User Tools

Site Tools


community:project-incubation-exit-criteria

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
community:project-incubation-exit-criteria [2016/10/28 16:43]
Arnaud J Le Hors
community:project-incubation-exit-criteria [2017/05/30 23:09] (current)
Tracy Kuhrt [Minimum requirements]
Line 1: Line 1:
 ====== Project Incubation Exit Criteria ====== ====== Project Incubation Exit Criteria ======
 +
 +Accepted as of version "​2016/​12/​01 15:43" by the Technical Steering Committee on 2016/12/01.
  
 ===== Introduction ===== ===== Introduction =====
Line 24: Line 26:
   * Sufficient user documentation\\ The project must including enough documentation for anyone to test or deploy any of the modules.   * Sufficient user documentation\\ The project must including enough documentation for anyone to test or deploy any of the modules.
   * Alignment   * Alignment
-    * Requirements fulfillment\\ The project must document what [[https://​github.com/​hyperledger/​hyperledger/​wiki/​Requirements-WG | requirements and uses cases]] it addresses. +    * Requirements fulfillment\\ The project must document what [[groups:​requirements:​Requirements-WG | requirements and use cases]] it addresses. 
-    * Architecture\\ The project must document how it fits within the [[https://​github.com/​hyperledger/​hyperledger/​wiki/​Architecture-WG | HLP Architecture]] +    * Architecture\\ The project must document how it fits within the [[groups:​architecture:​Architecture-WG | Hyperledger ​Architecture]] 
-    * Compatibility with other HLP projects\\ Where applicable, the project should be compatible with other active projects. +    * Compatibility with other Hyperledger ​projects\\ Where applicable, the project should be compatible with other active projects. 
-    * Release numbering: the project should use the [[https://​docs.google.com/​document/​d/​1u9pt-bXeOXefYBB1uYE6M-D6CtmkC1lGCjmicSlZgVA | HLP standard release taxonomy]], once that is agreed upon.+    * Release numbering: the project should use the [[https://​docs.google.com/​document/​d/​1u9pt-bXeOXefYBB1uYE6M-D6CtmkC1lGCjmicSlZgVA | Hyperledger ​standard release taxonomy]], once that is agreed upon.
     * Project must make a release, even a “developer preview”, before graduation.     * Project must make a release, even a “developer preview”, before graduation.
   * Infrastructure   * Infrastructure
-    * Github repo has been created+    * Gerrit or Github repo has been created
     * Mailing lists have been created and are archived     * Mailing lists have been created and are archived
     * Other communication means used, such as slack channels, are set up     * Other communication means used, such as slack channels, are set up
     * Project is set up with Continuous Integration     * Project is set up with Continuous Integration
     * All information necessary for someone to join the community and be able to start contributing is duly documented (location of repo, list of maintainers,​ mailing lists addresses, slack channels if used, etc) following the Hyperledger Project standard practice (CONTRIBUTING.md MAINTAINERS.txt etc)     * All information necessary for someone to join the community and be able to start contributing is duly documented (location of repo, list of maintainers,​ mailing lists addresses, slack channels if used, etc) following the Hyperledger Project standard practice (CONTRIBUTING.md MAINTAINERS.txt etc)
 +  * CII Badge \\ A team seeking to graduate from incubation shall have started the CII Badge application and be nearly complete with incomplete badge requirements referenced in their graduation proposal. 100% of the applicable criteria for the CII Badge is a requirement for releasing a 1.0 of the project. That does not mean the project must have 100% of all criteria, just 100% of the applicable criteria. This is to allow for projects such as test harnesses, that have "​N/​A"​ answers for questions that don't offer that as an option.
  
-===== Additional ​requirements ​=====+===== Additional ​considerations ​=====
 In addition to the above, requirements such as the following may be defined at the onset of the project and considered as goals to be met to exit incubation: In addition to the above, requirements such as the following may be defined at the onset of the project and considered as goals to be met to exit incubation:
   * Sufficient real world use\\ The project should be used in real applications and not just in demos. Because not all real applications may be discussed publicly, in such cases statements providing as much details as possible should be made.   * Sufficient real world use\\ The project should be used in real applications and not just in demos. Because not all real applications may be discussed publicly, in such cases statements providing as much details as possible should be made.
community/project-incubation-exit-criteria.1477672980.txt.gz · Last modified: 2016/10/28 16:43 by Arnaud J Le Hors