Project Submission

The following questions are asked when submitting a new project on the project submission page.

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.

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).

Submitter information

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

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.

Project information

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.

Targeted audience

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.

Supporting team

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.

Business model

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?

User community

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.


If your project is an application, are you willing for it to be hosted as a sub-project of an existing project (i.e., a JOnAS application)? If yes, please detail in which project you would like to be hosted.

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.

OW2 components

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.

Interested parties

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 (, 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.

Other Information?


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: information 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, cancel 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).