User Tools

Site Tools


project_lifecycle_v2

Differences

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

Link to this comparison view

Next revision
Previous revision
project_lifecycle_v2 [2015/12/20 15:46]
Frank Brockners created
project_lifecycle_v2 [2016/01/15 09:28] (current)
Frank Brockners
Line 3: Line 3:
 ---- ----
  
-**DRAFT-DRAFT-DRAFT - Proposal ​for a revision ​of the OPNFV project lifecycle ​document - DRAFT-DRAFT-DRAFT**+====== !!OUTDATED!! ====== 
 + 
 +**This wiki was just for discussion: 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]].**
  
 ---- ----
Line 15: Line 17:
 ==== Project lifecycle overview ==== ==== Project lifecycle overview ====
  
-OPNFV defines four maturity levels that each project goes through during its lifecycle. The procedure of moving from one level to the next one is independent from the release process of OPNFV and the pace depends on each individual project.+OPNFV defines four maturity levels that each project goes through during its lifecycle. The procedure of moving from one level to the next one is independent from the release process of OPNFV and the pace depends on each individual project. Projects in states "​Incubation",​ "​Mature"​ and "​Integration"​ can participate in releases.
  
 The lifecycle of the projects is depicted on the following diagrams: The lifecycle of the projects is depicted on the following diagrams:
Line 30: Line 32:
 | Incubation ​    | Project has resources, but is recognized to be nascent. ​                                                                                                                                                   | | Incubation ​    | Project has resources, but is recognized to be nascent. ​                                                                                                                                                   |
 | Mature ​        | Project is fully functioning and stable, has achieved successful releases. ​                                                                                                                                | | Mature ​        | Project is fully functioning and stable, has achieved successful releases. ​                                                                                                                                |
-| Integration ​   | Project provides value to a broad audience. ​                                                                                             |+| Integration ​   | Project provides value to and receives interest from a broad audience. ​                                                                                             |
 | Archived ​      | Project has been recognized as dead (could be for a variety of reasons, e.g. project successfully accomplished its goals, project failed, etc.), and has been archived as it's no longer a going concern. ​ | | Archived ​      | Project has been recognized as dead (could be for a variety of reasons, e.g. project successfully accomplished its goals, project failed, etc.), and has been archived as it's no longer a going concern. ​ |
  
Line 49: Line 51:
  
   * Proposal posted for two weeks:   * Proposal posted for two weeks:
-    * Name (trademark) is okay+    * Name of the project is appropriate ​(no trademark ​issues etc.); Proposed repository name is all lower-case without any special characters
     * Project contact name and email     * Project contact name and email
     * Description is complete     * Description is complete
     * Scope and project plan is well defined     * Scope and project plan is well defined
-    * NFV requirement ​identified ​or new proposal prepared+    * Reference of an existing ​NFV requirement or clear identification of a new requirement
     * Resources committed     * Resources committed
     * Contributors identified     * Contributors identified
-    * Committers to be elected by contributors+    * Initial list of committers identified (elected/​proposed ​by initial ​contributors)
     * Meets BoD policy (IPR)     * Meets BoD policy (IPR)
-    * Proposal has been socialized with potentially interested or affected projects+    * Proposal has been socialized with potentially interested or affected projects ​and/or parties 
 +    * In the case where a project will require changes in other projects, those projects are listed in the proposal, and a sponsoring developer in the project has been identified
     * Proposal email to TSC mailing list     * Proposal email to TSC mailing list
   * Review by TSC: Confirm that the proposal is complete and the above listed requirements are met   * Review by TSC: Confirm that the proposal is complete and the above listed requirements are met
Line 68: Line 71:
   * Review metrics for graduation review:   * Review metrics for graduation review:
     * //​Successful participation in releases:// The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.     * //​Successful participation in releases:// The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.
-    * //Project is active and contributes to OPNFV:// The project demonstrates a stable or increasing number of contributions across recent release cycles. ​We consider ​commits ​as contributions ​merged to any related ​OPNFV or upstream project’s repository. Commits can be for example patches to update the requirements document of a project, code addition to an OPNFV or upstream project repository,​new test cases and so forth.+    * //Project is active and contributes to OPNFV:// The project demonstrates a stable or increasing number of contributions across recent release cycles. ​Contributions are commits ​which got merged to a repository of an OPNFV project ​or a related ​upstream project. Commits can for example ​be patches to update the requirements document of a project, code addition to an OPNFV or upstream project repository, new test cases and so forth.
     * //Mature artifacts produced:// The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed and used by users.     * //Mature artifacts produced:// The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed and used by users.
   * 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 76: Line 79:
   * Integration proposal posted for two weeks   * Integration proposal posted for two weeks
   * Review metrics for integration review include the metrics for graduation review plus the following:   * Review metrics for integration review include the metrics for graduation review plus the following:
-    * //​Contributor diversity://​ The project demonstrates that it has a stable core team of contributors/​committers which are affiliated to a set of at least three different companies. Core team members are those who have been active on the project for more than 2 releases, which means they were reviewing contributions to the project in OPNFV Gerrit and/or in the tool of the target upstream project(s). and are expected to have reviewed an average of at least 25% of all code contributions for the last year.+    * //​Contributor diversity://​ The project demonstrates that it has a stable core team of contributors/​committers which are affiliated to a set of at least three different companies. Core team members are those who have been active on the project for more than 2 releases, which means they were reviewing contributions to the project in OPNFV Gerrit and/or in the review-tool of the target upstream project(s).
     * //​Recognized value through other projects:// The project demonstrates that its results are leveraged by other OPNFV projects in an ongoing way, i.e. for at least the last 2 releases.     * //​Recognized value through other projects:// The project demonstrates that its results are leveraged by other OPNFV projects in an ongoing way, i.e. for at least the last 2 releases.
-    * //​Successful integration tests// (only applicable to projects which provide features/​functionality):​ The project demonstrates that component and system level tests have been implemented,​ that tests are used within the OPNFV CI/CD test pipeline, and that tests bear successful results.+    * //​Successful integration tests// (only applicable to projects which provide features/​functionality):​ The project demonstrates that component ​tests and system-level tests have been implemented,​ that tests are used within the OPNFV CI/CD test pipeline, and that tests bear successful results.
   * TSC review and simple majority approval by voting TSC members   * TSC review and simple majority approval by voting TSC members
  
Line 86: Line 89:
     * States reason for project termination being sought     * States reason for project termination being sought
       * Termination proposal to include acceptable triggers for termination (e.g. protracted idleness, or request by the project)       * Termination proposal to include acceptable triggers for termination (e.g. protracted idleness, or request by the project)
-    * Estimates impact on other projects and how to mitigate +    * Estimates impact on other projects and how to mitigate ​potential negative impacts 
-    * Removal will not break Reference Platform ​builds+    * Removal will not break OPNFV platform ​builds
     * Location identified and links created for the archived project     * Location identified and links created for the archived project
   * Simple majority approval by voting TSC members   * Simple majority approval by voting TSC members
-  * If no approval, ​remains in pre-reviewed ​state+  * If no approval, state of the project does not change
project_lifecycle_v2.1450626395.txt.gz · Last modified: 2015/12/20 15:46 by Frank Brockners