...
- (Danno) Code should exist as open source software in some form
- Some projects come up from labs (e.g., Cactus, Ursa)
- Some projects have stand alone governance prior to joining (Besu ... others?)
- DCO sign off exists in the code repository
- If not 100% ready, the code is capable of becoming compliant upon entry (i.e. squash commit)
(Arun) Answer the checklist (TODO: come up with a checklist) for a new project's proposal in terms of license/copyright, DCO requirements, file structure/repo requirement (should comply to this requirement within 6 months of incubation), CI/CD requirement, release process (will be incubation exit criteria).
Maintainers
- (Danno) The project should have multiple maintainers
- These maintainers need not be from different companies
- However, having maintainers from different companies is seen as a positive sign (Hart)
- Proposals with only one maintainer have been rejected by prior TSCs.
- These maintainers need not be from different companies
- (Arun) Come up with a plan to promote contributors into maintainers. Get this plan published as part of project proposal.
- (Arun) The project either has demonstrable examples of POC/production uses publicly available or has backing of more than one organization/individuals (should be able to demonstrate significant contribution in codebase, should also be able to demonstrate that this engagement is long term ~ex: 3 months long or at least 35% of the codebase contributions).
...