ProposalClass Sheet

Submitting a new project to OW2

You intend to submit a new project to OW2 and we thank you for your interest in our community. Please note that only registered members can submit projects on the Forge. Before proceeding with the project registration, you must concur with the following clarifications on the status and nature of the OW2 Consortium.

Your proposal supports the mission of OW2

The mission of the OW2 Consortium is to develop open source code middleware and to foster a vibrant community and business ecosystem. To be hosted by OW2, projects must be consistant with its mission: they are middleware project aiming at facilitating the development, deployment and management of distributed applications and their proponents commit to participate in developing the OW2 community and business ecosystem.

You consent to the governance of OW2

The strategy of the Consortium is decided by the Board of Directors. OW2 day-to-day operations are carried out by the Management Office and the technology strategy is driven by the Technology Council.

Projects submissions are evaluated by the Technology Council which decides by consensus whether or not to host the project on the OW2 infrastructure.

You subscribe to the participative nature of OW2

Once they are accepted, Projects are welcome to use all facilities provided by the Consortium's collaborative environment including the Forge, bug trackers, mailing lists, download sites, etc.

Projects participants must understand the community and participative nature of this infrastructure. While we do our utmost to provide a reliable service, the Consortium is still a non-profit organization, it does not sell a service, and project participants are not its customers. Project participants, and at least the project leader, are expected to be proactive in helping the Consortium improve its infrastructure.

The project leader is a de facto member of the Technology Council and is invited to take part in its discussions and deliberations held through conference calls, mailing lists and face-to-face meetings at Quarterly Meetings.

You adhere to the Projects Life Cycle

Like all IT project, OW2 projects evolve along what we call a Project Life Cycle. As defined by the Technology Council, the OW2 project life cycle is comprised of three stages: Incubation, Maturity and Archive.

New projects start in the Incubation stage then may move to the Maturity stage and, ultimately, might end up in Archive. The Technology Council carries out periodic evaluation of projects and update their status depending of several criteria. For more information, please refer to the OW2 Projects Life Cycle document.

To apply for project registration, you should fill in basic information about it. Please read descriptions below carefully and provide complete and comprehensive data. All fields below are mandatory.



Please provide detailed, accurate description of your project and of which OW2 Forge resources you plan to use and in which way. This description will be the basis for the approval or rejection of your project's hosting on OW2 Forge, and later, to ensure that you are using the services in the intended way. This description will not be used as a public description of your project. It must be written in English.
The approval of new projects is pronounced by the Technology Council. The typical time frame is to get an answer is two weeks. However, keep in mind that we are an open-source organization, where reaching a consensus may take some time.
















If you are applying for a website-only project, please select "website-only" from the choices below and proceed.

The OW2 Forge was created to advance the development of middleware according to the Open Source development model. Choosing a license is a serious decision in the life of a project. Unless you definitely know what you do, please take some time to read the text of several licenses before making a choice about your project. Our Board, Management Office and Technology Council may help you find your way amongst different licenses and make a choice that would fit both your needs and OW2 policy.

The Project License shall be any open source software license which is a) approved by the Board of the Association for each Project in accordance with reasonable and appropriate criteria and b) compliant with the non-assertion commitment described in Section 4 of the IPR Policy document, and/or imposing at least a royalty-free license of any Necessary Claims which cover the contribution of such patent holder, and which is revocable in the case of lack of reciprocity.
As an Open Source consortium and community, and as described in its IPR Policy document, OW2 will accept as an Open Source license any software license abiding by the following criteria: (i) Freedom to redistribute, (ii) Source code must be included in the program, (iii) Freedom to create derivative works, (iv) Integrity of the author's source code (modifications must be distinguished from the original version), (v) No discrimination against persons or groups, (vi) No discrimination against fields of endeavor, (vii) Distribution of license (i.e redistribution of the software shall include the license and must not need the execution of further license), (viii) The license must not be specific to a product, (ix) The license must not restrict other software, (x) The license must be technology neutral. The majority of projects at OW2 have selected the LGPL which can be considered as the default license for the Consortium. Feel free to select another license, but be so kind as to explain the reasons of your choice in the description of your project (field below).

In any event, the OW2 Consortium will not be held responsible for legal discrepancies regarding your license. The consortium neither has the purpose, ability nor resources to ensure that you hold the required rights, including copyrights, to submit your project and decide on its license. THIS IS YOUR RESPONSIBILITY AND YOUR LIABILITY. You may want to change the license for your project at a later date, so long as you have a legal capability to do so, and your file release clearly indicates this change, and your filemap categorization must be updated appropriately. It is your responsibility to include and update the license text in the sources of your project and to keep track of copyright owners. Changing the license may change the nature of the project, therefore such a move requires approval by the Board of Directors. Keep in mind that changing the license typically requires that all copyright holders agree to such change. Also be aware that choosing some licenses, including opting for public domain, may conflict with your domestic regulations depending of your country. Please note that license changes are not retroactive (i.e. do not apply to products already released under an Open Source license).

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 6.4.4 - Documentation
Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice