Last modified byon 2010/07/06 09:59
Access the OW2 code base directly:
OverviewThe Consortium's activities for software development are organized into Projects. A Project regroups development actions corresponding to one or more technical software components, or the integration of different technical components in order to build a platform. Projects are the raison d'�tre of OW2, without projects, OW2 just does not exist. Projects represent the fundamental activity. At OW2, everything starts with a Project. Building on the legacy of ObjectWeb and OrientWare, OW2 is fully committed to managing open source projects. They currently cover a broad scope of functionality including application platforms, persistency/database solutions, workflow engines, software engineering, etc. OW2 provides a ?home? as well as a showcase to open source software projects. Each project evolves through a well documented project life cycle. OW2 already hosts more than 100 projects. The is responsible for building the overall technical architecture, including defining technical guidelines, for providing technology validation, for making Project lifecycle decisions, for monitoring production and overall Projects consistency.
Submitting a new projectYou can directly submit a project from the OW2 Forge . The fully executed Individual membership of the project leader is the minimum membership requirement for a project to be accepted in incubation. The proposal is then debated on the Technology Council mailing list which evaluates its relevance for OW2 in terms of complementarities, synergies, licence, support, etc. The Technology Council must reach a consensus to adopt the project. Each project must also be presented and discussed at a Technology Council meeting. It is then provisioned in the OW2 Forge and you can start working on it.
Project selection criteriaProject submissions are evaluated by the Technology Council which decides by consensus whether or not to host the project on the OW2 infrastructure. The Technology Council will decide after evaluating and reaching consensus on the four principal following criteria:
- Is it middleware (at large)?
- Does the team show goodwill to synergize with other OW2 projects?
- Is the license compatible with the IPR policy?
- Is the Project able to release code and/or foster a community?
Competition between projectsOW2 recognizes that a dynamic code base must accept some level of competition between its projects. Moreover OW2 project portfolio is already quite extensive and could not grow without some projects friction or overlap. Projects with overlapping or 'competitive' features will be allowed on the OW2 Forge and in OW2 initiatives so long as: 1) They are provided by an OW2 Member.
2) They are distributed under an OSI-approved license.
3) They are differentiated from existing projects.
4) They are accepted by the Technology Council.