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.
Complete name of the project
You have to start by providing the name of your project. This name is descriptive and not constrained (but limited to 40 characters).
Say who you are. Typical value of this field must contains at least Name, Affiliation (your company's name for example) and your email address that the TC can use to reach you.
Project purpose and summarization
The approval of new projects is recommended by the Technology Council and pronounced and executed by the Management Office. 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.
The following information helps the technology council in determining the purpose, intentions and scope of the project.
Description of the project and its goals
Do not be too descriptive, focus on the main features and contributions of your project.
Help us understand if your software is targeted to middleware designers, end-users, or a specific community. Similar or competitor projects: Identify the competing projects in the state of the art that partially or completely overlap with your project. Please provide name, URLs and a description of how your project brings new contributions. Note that it is fine for your project to overlap with other projects, even if they are hosted by OW2.
The Technology Council is not only concerned with the technical and architectural aspects of the project, but also about its viability. This section must contains the list of initial committers for this project (name + affiliation + email). Please also give details about your financial support if applicable.
If you are a "for profit" organization, what is your business model or strategy for this product? What do you expect to gain from open sourcing your product? What about your competitors?
If your project already has a user community, provide detailed information about it or indicate user communities that could be interested by the project.
OW2 is an international consortium, explain how globalization is handled in your project or how do you plan to support it.
Provide a development plan (workplan) with possibly a short-term and a long-term vision.
Is the source code currently publicly accessible? Where is it downloadable from at the moment? If the project is accepted in the OW2 code base, will source code, documentation, etc. be hosted on the OW2 infrastructure or your own infrastructure?
Your project and OW2
The following information identifies interaction with the OW2 Community so that we can understand where and how your project fits in the overall picture.
Provide a list of OW2 components that are used (or that you plan to use) in your project and which components could benefit from your project.
Identify possible synergies with OW2 projects or working groups.
This section contains the name of people (external to your project) that express their interest in this software and would be willing to become users or contributors of the project once it is created. Notice that this section may be updated during the discussions with the TC by the interested peoples themselves.
Technologies and standards
Detail the technologies or standards that are used or implemented by your project. Identify which standards are already covered by the OW2 code base.
Contribution to the OW2 Community
Describe the benefits for OW2 to host your project.
Motivations to join the consortium and its community
Finally, we would like you to briefly expose your motivations to join the consortium. You have certainly considered other open source communities to host your project (at least we hope so), but why did you to choose OW2? Explain why, if your project is already hosted somewhere else (sourceforge.net, own website, ?) you would like to move to OW2 and how do you envision the transition.Why OW2: Explain why do you think that OW2 is the right host for your project.
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: 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, 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).