User Tools

Site Tools


project_lifecycle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
project_lifecycle [2015/09/08 14:06]
Ildiko Vancsa [Project lifecycle overview]
project_lifecycle [2016/01/15 08:03]
Ildiko Vancsa
Line 1: Line 1:
 +
 +
 +----
 +
 +**DRAFT-DRAFT-DRAFT - Proposal for a revision of the OPNFV project lifecycle document - DRAFT-DRAFT-DRAFT**
 +
 +For the latest up to date version of the document see the [[https://​www.opnfv.org/​developers/​technical-project-governance/​project-lifecycle | OPNFV project lifecycle web page]].
 +
 +----
 +
 ===== OPNFV Projects ===== ===== OPNFV Projects =====
  
-The activities of the Community are organized into projects, which are targeting different areas within the scope of OPNFV including ​all the support functions to create and maintain the infrastructure and toolchains we use.+The activities of the Community are organized into projects targeting different areas within the scope of OPNFV including ​but not limited to; development of upstream code, integration of platform components, ​support functions to create and maintain the infrastructure and the development and maintenance of the toolchains we use.
  
 ==== Project lifecycle overview ==== ==== Project lifecycle overview ====
Line 15: Line 25:
 === Project states === === Project states ===
  
-^ Project state  ^ Description ​                                                                                                                                                                                                                                                                                                                                                                                     +^ Project state  ^ Description ​                                                                                                                                                                                               
-| Proposal ​      ​| ​The first step for a project is the project Proposal state. This phase has to include a clear project scope and plan. At this stage the project does not need to have a full list of resources, but the indication ​to work on having resource coverage and diversity for the work they are planning                                                                                            ​+| Proposal ​      ​| ​Project doesn’t really exist yet, may not have real resources, but is proposed and is expected ​to be created due to needs                                                                                ​
-| Incubation ​    ​| ​When a project moves to Incubation levelit has to have the proper resource coverage and a minimum diversity. At this stage the project ​is still considered ​to be nascent, the work following the Agile flow described in the development process can be started                                                                                                                              ​+| Incubation ​    ​| ​Project has resourcesbut is recognized ​to be nascent. ​                                                                                                                                                   
-| Mature ​        ​| ​In order to move to Mature level the project has to be considered as stable. It also has to successfully participate in multiple OPNFV releases ​before this stage                                                                                                                                                                                                                              ​+| Mature ​        ​| ​Project is fully functioning and stablehas achieved successful ​releases. ​                                                                                                                                ​
-| Integration ​   | The highest state a project can reach is Integration, at this level it is considered to be an integral part of the OPNFV reference platform ​and/or ecosystem                                                                                                                                                                                                                                   +| Integration ​   | The highest state a project can reach is Integration. Project ​is a component ​of the OPNFV reference platform. ​                                                                                             
-| Archived ​      ​| ​Regardless of the level of the project it can happen during its lifecycle that the activities within it are stopped. The project can be archived because ​of failure or the lack of resource coverageetcor it can successfully ​accomplish ​its goals and considered to be finishedIn either case the project should be removed from active state and has to be moved to the Archived stage.  | +| Archived ​      ​| ​Project has been recognized as dead (could ​be for a variety ​of reasonse.g. project ​successfully ​accomplished ​its goals, project failed, etc.), and has been archived as it's no longer a going concern.  |
  
  
-==== Reviews ==== 
  
-Moving between levels can only be done by official review procedures. 
  
-=== Metrics ===+==== Reviews & Metrics ​====
  
-During the reviews the candidate projects are evaluated based on predefined metrics and KPIs. The target numbers may vary for the different levels.+Project promotion, and demotion, across states can only be done by TSC review and voting.  ​During the reviews the candidate projects are evaluated based on predefined metrics and KPIs. The target numbers may vary for the different levels.
  
    * Longevity of the project    * Longevity of the project
-   * Active, diverse community 
    * Project follows OPNFV release cadence    * Project follows OPNFV release cadence
    * Requirements have resulted in corresponding implementations    * Requirements have resulted in corresponding implementations
Line 62: Line 68:
    * Graduation proposal posted for two weeks    * Graduation proposal posted for two weeks
      * Can demonstrate stable output (code base, documents) within its history of releases in accordance with release policy      * Can demonstrate stable output (code base, documents) within its history of releases in accordance with release policy
 +     * History of releases in accordance with release policy
      * Fulfils the applicable metrics defined above      * Fulfils the applicable metrics defined above
    * TSC review and simple majority approval by voting TSC members for graduation    * TSC review and simple majority approval by voting TSC members for graduation
Line 70: Line 77:
    * Integration proposal posted for two weeks    * Integration proposal posted for two weeks
    * The project fulfils the applicable metrics from the set defined above and additionally the ones below:    * The project fulfils the applicable metrics from the set defined above and additionally the ones below:
-     * Project is active 
      * Project is shown to be viable component of OPNFV Reference Platform      * Project is shown to be viable component of OPNFV Reference Platform
      * Project build and test scripts have been created to work with the rest of Platform build      * Project build and test scripts have been created to work with the rest of Platform build
      * Project shown to not break continuous development and integration environment      * Project shown to not break continuous development and integration environment
-   * History of releases in accordance with release policy 
    * TSC review and simple majority approval by voting TSC members    * TSC review and simple majority approval by voting TSC members
    * Integration review assesses projects based on the metrics of the graduation review. In addition the project is required to have confirmed longevity (project is active for at least one year, participates in release activities, and has release plans outlined to stay active for at least another year)    * Integration review assesses projects based on the metrics of the graduation review. In addition the project is required to have confirmed longevity (project is active for at least one year, participates in release activities, and has release plans outlined to stay active for at least another year)
project_lifecycle.txt · Last modified: 2016/01/15 09:29 by Frank Brockners