Project Lifecycle Criteria

OW2 project classification

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.

Does the project code base compile?

Compilation is compulsory for Mature projects.

Are there users outside the project leader organization?
  • If yes, please list project users (other OW2 projects, external entities, ...)

Users are compulsory for Mature projects.

Are there professional services around the project code base? A commercial support offer?
  • If yes, please indicate services and/or support providers

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.

Is there a web site?
  • If yes, please indicate the project website URL

A project website is compulsory for Mature projects.

Is there a project flyer?
  • If yes, please indicate the URL at which the project flyer can be found

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.

Is the project written in English, or, better, internationalised?

Internationalization is recommended for all projects.

Is there a project roadmap?
  • If yes, please indicate the project roadmap URL

A roadmap is recommended for all projects.

Is the project competing with another OW2 mature project (this is for information, and OW2 accepts internal competition)?
  • If yes, please indicate other OW2 competing projects, and precise the functional area of competition

Competition is accepted as long as it respects the rules described on the project page.

Does this project reinforces the OW2 consortium as a whole?
  • If yes, please motivate how your project reinforces OW2

This indication is recommended for all projects. A project which could not express how it reinforces OW2 could not be considered Mature.

Is there a lead (one or several contact persons) who is a corporate OW2 member?
  • If yes, to which OW2 corporate member does the project lead belong?

It is compulsory for a mature project to be lead by a corporate OW2 member.

Do you consider that the project has no more development activity (about 1 year since last commits)?

A project which has no more activity is a strong candidate to become Archive.

Has the project officially been moved to another place than OW2?
  • If yes, please provide the new project URL

A project which has moved elsewhere is a strong candidate to become Archive.

Are there binary, source, documentation available on OW2 infrastructure?

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.

Is there an identified project lead (one, or maybe several person(s))?

It is compulsory for Mature projects to have an identified lead.

Has the project ever released code or binaries ? If not, does it intend to do so in the future? ("ghost" or "fake" projects) will be deleted when moving to archive

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.

Tags:
Created by olivier lizounat on 2011/08/25 15:47
Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice