When a new ONAP project is proposed the initial list of Committers is provided as part of the 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. 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.

  • 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 impacted the Committer pool and 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.  

• Involuntary

  • Inactivity

    • A PTL can remove a Committer for a demonstrated failure to perform their duties for an extended period of time of 6 months or more.  Committer lists are often scrubbed at the start of a release cycle just because that is a convenient time to take stock of where a particular project community stands.  All that is required is for the PTL to send an email to the onap-tsc list stating that the person is being removed due to inactivity and then update any associated INFO.yamls

  • Vote of the sitting Committers

    • A Committer can be removed by a 2/3rds vote of the sitting Committers. The PTL must send an email to the onap-tsc list stating that the person is being removed, along with documentation in the form of an email thread or meeting minutes and then update any associated INFO.yamls.

  • Action by the PTL

    • The PTL can ask the TSC for a Committer to be removed if the Committer has proven to be disruptive to the project in the performance of his/her duties. Documentation in the form of an email thread or meeting minutes is required.  If the request is granted the PTL needs update any associated INFO.yamls

  • Action by the TSC

    • Under exceptional circumstances the TSC can take action to remove a Committer. Typically this is done only when the existing PTL has been let go by their company and/or they have become non-responsive to the needs of the community.