When a new ONAP project is proposed the initial list of Committers is provided as part of the Project Proposal Template which New Project Proposals template which is presented to the TSC for approval. The specific wiki version of the Proposal at the time the Project is approved by the TSC defines the actual list of Committers approved for that project when it launches.
However adding a new Committer or removing a Committer once the Project is approved is governed by Section 3.2.2 of the ONAP Technical Community Document
The ONAP Technical Community Document has the official language and specific details that must be adhered to. What is listed here is simply a process overview and not considered authoritative:
Adding a Committer
Community Driven
Most of the process to add a new Committer is automated, but the PTL need to fill in the template and update the INFO.yalm for the repo. See Committer Promotion automation via INFO.yaml for the HOW-TO
- The existing Committers vote for a member of the community to be promoted based upon a significant contribution to the project over an extended period of time
The PTL fills in the
and moves it under their project's wiki hierarchy after saving it.Create from Template templateName 85426205 templateId 85426205 title Committer Promotion for [your-project-name] : Committer Name buttonLabel Committer Promotion Template The PTL updates the INFO.yaml and includes a link to the completed promotion template in the INFO.yaml commit message
Committer access is auto-provisioned after the code is merged
A Jenkins job sends an FYI notification of the Committer promotion to the TSC list for visibility
TSC Driven
- Under exceptional circumstances the TSC may intervene to add new Committers to a project. Typically this is done only when something extreme occurs such as company wide layoffs which have greatly diminished impacted the Committer pool for the project and has also impacted the PTL as well. the PTL
Removing a Committer:
Voluntarily:
Any Committer can step down by informing the PTL and sending email to the onap-tsc list. All that is required in this situation is for the PTL to make the necessary updates to the INFO.yaml file(s) for any impacted repositories.
...