This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
community:project-incubation-exit-criteria [2016/12/05 05:46] Brian Behlendorf [Project Incubation Exit Criteria] |
community:project-incubation-exit-criteria [2017/05/30 23:09] (current) Tracy Kuhrt [Minimum requirements] |
||
---|---|---|---|
Line 37: | Line 37: | ||
* 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 considerations ===== | ===== Additional considerations ===== |