Mature Transition Criteria


Here is the output of the discussion between Jacques, Florent and myself (Guillaume) about the required criteria to successfully move a project from incubator to mature.

Acceptance Criteria

First of all, we decided to remove all business related criteria: we're the technology council, not the board, let these business aspects to other guys and focus on technical and community aspects.

Technical Criteria

Build

  • The project code-base must build.
  • A continuous integration mechanism must be used to ensure the build is a success.
Projects could use the in-house Continuous Integraton System (http://bamboo.ow2.org) or provides a link on their own CI system elsewhere.

Re-Usability

The projects must show that it is used within the OW2 universe or outside.

Possible Control Points:

  • Code sharing with maven repository
  • Gives references of client system (using the project)
  • Gives references of business users
  • ...

Quality

This one is much more subjective and should be discussed.
What is sure is that quality is an important factor of maturity acceptance.

Possible Control Points:

  • Checkstyle report
  • Code coverage
  • Tests/Code ratio ?
  • At least 1 development branch (the trunk)
  • At least 1 tags in the VCS for proper release management
  • ...

Community Criteria

Committers

The project must have more than 1 active committer.

Dashboard

The project's dashboard must be up to date.

Question: What is the minimal dashboard's content for a mature project ?
  • Compulsory
    • Project Name
    • Project description -> compulsory
    • Short project description
    • Status: Mature/Incubator/Archive
    • Function: (in the list of predefined functions)obvious
    • License
    • Forge Link
    • Mailing List link
    • Repository type (SVN, CVS, etc)
    • Repository Link
    • Project Home Page Link
  • Recommended
    • Logo Image
    • License Link
    • Project DataSheet link (the link must be to a PDF file)
    • Professional support link
    • Case study -> I think it should be compulsory (at least to show who is using it)
    • Standard implemented
  • Future
    • Fossology report -> will be compulsory in the future for mature projects when implemented
    • Code quality reports(Sonar? Code coverage? other?)
    • project roadmap (link)

Active

The project must show that it is in activity:

  • Exchanges (question + answer) on the mailing lists
    • Community support
  • Last commits
  • ...

Get Involved

Share technical know how with other users, and help to promote OW2

TC Live

 

 


This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 6.4.4 - Documentation
Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice