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

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


The Hyperledger Project has defined a lifecycle for its projects but this definition does not specify in any detail what it takes for a project to be able to transition from the Incubation phase to the Active phase.

This document is meant to fill this gap by defining a set of criteria to be considered before moving a project from Incubation to Active.

It is important to note that Active in this case refers to the project itself rather than its product and it is therefore more about the maturity of process than the maturity of the product or General Availability (GA).

For this reason this document defines two sets of exit criteria. The first one is made of requirements expected to be met by all projects before moving to Active. The second set lists examples of additional requirements typically defined at the onset of the project as goals to be met to exit incubation. There are expected to be documented in the Proposal for a Hyperledger Improvement Project (HIP). Because not all projects have the same goals, the importance of each criteria and the exact definition of this second set of criteria may vary from one project to another. Ultimately the TSC is responsible for determining whether a project deserves to move to Active or not and this decision does not need to be solely based on these exit criteria. The purpose of these exit criteria is to help the TSC in its decision process by informing its members of key aspects of the project.

Minimum 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:


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