Let us know how we are doing

Take the DCI Working Group's new survey!

Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Hyperledger Governing Process document - do not modify without first getting approval of the TSC

Accepted by the Technical Steering Committee on 2016/12/01.


  • Legal

    • All code has been made available under the Apache License and is free of incompatible dependencies

    • Project name has been checked for trademark issues

  • Community support

    • The project must have an active and diverse set of contributing members representing various constituencies

    • The project is not highly dependent on any single contributor (there are at least 3 legally independent committers and there is no single company or entity that is vital to the success of the project)

    • Release plans are developed and executed in public by the community.

  • Sufficient test coverage
    The project must include a comprehensive unit and integration test suite and document its coverage. Additional performance and scale test capability is desirable.

  • Sufficient user documentation
    The project must including enough documentation for anyone to test or deploy any of the modules.

  • Alignment

    • Requirements fulfillment
      The project must document what requirements and use cases it addresses.

    • Architecture
      The project must document how it fits within the Hyperledger Architecture

    • Compatibility with other Hyperledger projects
      Where applicable, the project should be compatible with other active projects.

    • Release numbering: the project should use the Hyperledger standard release taxonomy, once that is agreed upon.

    • Project must make a release, even a “developer preview”, before graduation.

  • Infrastructure

    • Gerrit or Github repo has been created

    • Mailing lists have been created and are archived

    • Other communication means used, such as slack channels, are set up

    • 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)

  • 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.


The above borrows from the ASF’s Minimum Graduation Requirements.