This document provides information to help people who are considering bringing their projects to Hyperledger for incubation. Specifically, it will outline items that the TSC will take into consideration when evaluating the project, as well as, some best practices that have been followed by other projects prior to the project proposal being submitted to the TSC. Our hope is that this document will smooth the entry process for new projects being proposed. The project proposal process and the template for project proposals are outlined outside of this document. The goal of incubation within Hyperledger is to provide a space for projects that have high potential to grow in the community. Ideas should start in Hyperledger Labs.

...

• (Arun) Follow the guidelines listed at https://hyperledger.github.io/hyperledger-hip/
• (Arun) Update checklist items for tools/website/writing blogs/marketing etc. (TODO: come up with a checklist). This becomes important as the community and number of projects grow. The requirement here is that project team follows up on completing the checklist after it is approved. Checklist can be found at New Project Checklist - Community Architects - Hyperledger Confluence.

Recommendations

• (Arun) Make relevant documentations, design discussions available in public. Keep them in review before bringing for discussion in TSC meeting.
  • (Hart) I think this is a big one.  We shouldn't even consider proposals where these things are not yet public, and should tell submitters to come back when they are.
• (Arun) Publish the project's scope in advance. Call for public review comments on project's scope.
  • Optionally, make use of Hyperledger channels to invite more participation. Make use of Hyperledger mailing lists to invite and call for participation.
  • There can be special consideration, for example projects that are incubated from labs have been in the public domain, Hyperledger community is familiar with them.