Approved by ODPi TSC on 2018-09-04
ODPi Top Level Project Proposal Process
Based on the CNCF Project Proposal Process v1.1
This governance policy sets forth the proposal process for projects to be accepted into the ODPi. The process is the same for both existing projects which seek to move into the ODPi, and new projects to be formed within the ODPi.
Project Proposal Requirements
Projects must be proposed via pull request to https://github.com/odpi/tsc/tree/master/projects. Project proposals submitted to the ODPi must provide the following information to the best of your ability:
- Name of project (must be unique within ODPi)
- Project description (what it does, why it is valuable, origin and history)
- Statement on alignment with ODPi charter mission
- Sponsor from TSC (sponsor helps mentor projects)
- Preferred maturity level (see ODPi Graduation Criteria)
- License and contribution guidelines (charter dictates Apache 2 by default, having each committer agree to the DCO
- Source control (GitHub by default)
- External dependencies (including licenses)
- Initial committers (how long working on project)
- Infrastructure requests (CI / ODPi Cluster)
- Communication channels (slack, irc, mailing lists)
- Issue tracker
- Release methodology and mechanics
- Social media accounts
- Community size and any existing sponsorship
Project Acceptance Process
- Projects are required to present their proposal at a TSC meeting
- Projects get accepted via a 2/3 supermajority vote of the TSC
- All projects must adopt the ODPi Code of Conduct.
- All projects agree to transfer any relevant trademarks to ODPi and to assist in filing for any relevant unregistered ones. This assignment will be reversed if the project does not remain in the ODPi, as described below. Note that no patent or copyright assignment is necessary because the Apache 2 license provides sufficient protections for other developers and users.
- All projects start at the Incubation stage by default unless the TSC approves otherwise.