project_lifecycle
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project_lifecycle [2015/09/10 12:15] Christopher Price |
project_lifecycle [2016/01/15 09:29] Frank Brockners |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | ====== !!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]].** | ||
| + | |||
| + | ---- | ||
| + | |||
| ===== OPNFV Projects ===== | ===== OPNFV Projects ===== | ||
| Line 30: | Line 40: | ||
| * 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 59: | 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 67: | 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) | ||
| Line 86: | Line 94: | ||
| * 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, remains in pre-reviewed state | ||
| - | |||
project_lifecycle.txt ยท Last modified: 2016/01/15 09:29 by Frank Brockners
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
