Skip to content

Commit

Permalink
Encourage projects to set annual goals
Browse files Browse the repository at this point in the history
Signed-off-by: S m, Aruna <arun.s.m.cse@gmail.com>
  • Loading branch information
arsulegai committed Jun 8, 2023
1 parent 56a8a7d commit 7e319f3
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions guidelines/project-incubation-entry-considerations.md
Expand Up @@ -11,6 +11,11 @@ This document provides information to help people who are considering bringing t
## Considerations
When considering projects that are proposed for incubation to Hyperledger, the TOC will consider the following items: codebase, maintainers, community, sponsors, legal, and overlap with existing projects. The below items are not hard and fast rules for projects being accepted. The considerations are a guide to project proposers. If you meet most of the considerations, you are most likely to be accepted. If you do not meet any of the considerations, you are most likely to not be accepted.

### Goal Setting
* Every project team have vision for why they exist.
* The project is more likely to succeed if it sets annual goals with expected outcomes.
* Hyperledger governance model allows for projects to go through an annual review process against the set goals. The evaluation helps everybody in the project to anticipate what's coming next in the project. It will open up opportunities for parties with similar interests join forces.

### Codebase
* Code should exist as open source software in some form. Previous accepted projects have come up through labs (e.g., Cactus, Ursa); while others previously had stand alone governance prior to joining (e.g., Besu).
* DCO sign off should exists in the code repository. If not 100% ready, the code must be capable of becoming compliant upon entry (i.e., squash commit).
Expand Down

0 comments on commit 7e319f3

Please sign in to comment.