Access the OW2 code base directly:
The 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 Technology Council
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
Submiting a new project
You can directly submit a project from the OW2 Forge project submission page
. Please note that a project will be open on the Forge only if the submitter is an OW2 member. 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 it relevance for OW2 in terms of complementarities, synergies, licence, support, etc. Each project must also be presented and discussed at a Technology Council meeting. The Technology Council must reach a consensus to adopt the project. It is then provisionned in the OW2 Forge and you can start working on it.
Project selection criteria
Projects 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 five principal 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?
- Is the Project overlapping (or redundant) with other projects?
Projects Life Cycle
The project life cycle is composed of three stages: Incubation
. New projects start in the Incubation stage then may move to the Maturity stage and, ultimately, might end up in Archive stage depending on periodic evaluation by the Technology Council. A fully executed Corporate or Strategic membership is required for a project to be moved to Mature status. Community projects based on individual members only will be handled on a case-by-case basis.
If you intend to submit a project or to contribute to a project, we recommend you read the OW2 Project Life Cycle
Interoperability Clusters: the Himalaya program
Throughout 2008, the OW2 community is working towards developing seamless interoperability between the different software components which comprise its code base. This is a bottom-up, peer-to-peer effort aiming at enhancing technical relationship between projects. Some projects with natural complementarities will group to create what we call interoperability clusters
. These clusters will then connect to form a comprehensive range hence the name of the program.
Many OW2 projects already come as ready-to-use packages. They are
provided as complete archives which you only needs to download and
install to start using them.
You can access the OW2 code base organized in several functional categories here?
Other OW2 projects are not listed here because no
stable version is packaged so far. To download them, you need to use
the Forge. As developments go on, more projects are made available for
download, so this list is going to expand. Stay tuned and come back to
check for new packages.