The project life cycle is composed of three stages: Incubation, Mature and Archive.
The following criteria are used to decide the status of each project.
Compilation is compulsory for Mature projects.
Users are compulsory for Mature projects.
Professional services are not compulsory to become a Mature project. Academic supported projects may not offer professional services, but may provide a strong community support.
A project website is compulsory for Mature projects.
A project Dashboard is compulsory for Mature projects (and recommended for all OW2 projects). Dashboards can be created by going to the Dashboard page.
It is recommended for all Mature project to have a project flyer, and possibly success stories. Templates can be found in the marketing resources page.
Internationalization is recommended for all projects.
A roadmap is recommended for all projects.
Competition is accepted as long as it respects the rules described on the project page.
This indication is recommended for all projects. A project which could not express how it reinforces OW2 could not be considered Mature.
It is compulsory for a mature project to be lead by a corporate OW2 member.
A project which has no more activity is a strong candidate to become Archive.
A project which has moved elsewhere is a strong candidate to become Archive.
It is compulsory for all OW2 projects to provide their source code on the OW2 Forge. Mature projects should also provide binary downloads and documentation.
It is compulsory for Mature projects to have an identified lead.
It is compulsory for a Mature project to release code. Moreover, projects which have never released any code for a long time are strong candidates to become Archive.
This wiki is licensed under a Creative Commons 2.0 licenseXWiki Enterprise 6.4.4 - Documentation