Changes for document Projects

into Projects. A Project regroups either development actions corresponding to

one or more technical software components,components or the integration of

are the //raison d’être// of OW2, and without projects, OW2 just would not exist. Projects represent

guidelines, for providing technology validation, for making Project

lifecycle decisions, forand monitoring production and overall Projects

You can directly submit a project directly on the [[project submission page>>Proposal.WebHome]]. 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. ItOnce it is then provisioned in the OW2 Forge andForge, you can start working on it.

Project 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:

OW2 recognizes that a dynamic code base must accept some level of competition between its projects. Moreover the OW2 project portfolio is already quite extensive and could not grow without some projects friction or overlap.overlap between projects. Projects with overlapping or ’competitive’ features will be allowed on the OW2 Forge and in OW2 initiatives so long as:as they are:

1) They are providedProvided by an OW2 Member.

2) They are distributedDistributed under an OSI-approved license.

3) They are differentiatedDifferentiated from existing projects.

4) They are acceptedAccepted by the Technology Council.

New projects start in the Incubation stagestage. They then maymight move to the Mature stage and, ultimately, might end up in Archive stage depending on periodic evaluation by the Technology Council ( see the [[project lifecycle criteria page>>Community.Project_Lifecycle_Criteria]] ).

##A fully executed Corporate or Strategic membership is required for a project to be moved from Incubation to Mature status. Community projects based on individual members only will only be handled on a case-by-case basis. Competition will be re-assessed for moving to the Mature status.

Starting inIn 2008, the OW2 community launched a long-term effort to develop seamless interoperability between the different software components which comprise its code base. This is a long-termlong-term, bottom-up, peer-to-peer (and on-and-off!) endeavour aiming at enhancingstrives to enhance technical relationship between projects. Some projects with natural complementarities will group together to create what we call **interoperability clusters**. These clusters will then connect to form a comprehensive rangerange; 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 downloadrequire downloading and installinstallation in order to start using them.be used.

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,move forward, more projects arewill be made available for download,downloading, so this list is going to expand. Stay tuned and come back to check for new packages.