A list of Committers for When a new ONAP Project project is provided by proposed the initial Project owner list of Committers is provided as part of the Project Proposal Template which is presented to the TSC for approval. 
The  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.From that point on a Committer can voluntarily step down from a Project her/himself with a simple email to the the PTL cc'd to the onap-tsc mailing list. All that is required in this situation is for the PTL to ask the LF to change permissions on the repository. 

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 Charter ONAP Technical Community Document has the official language and specific details that must be adhered to, but in a nutshell it works like this. What is listed here is simply a process overview and not authoritative:

Adding a Committer

...

• Community Driven

  • The
  sitting
  • existing Committers vote for a member of the community to be promoted based upon a significant contribution to the project
  (documentation in the form of an email thread or meeting minutes required).
• TSC is notifiied by the infrastructure coordinator
• The PTL edits the INFO.yaml file associated with the repo(s) and includes the link to the gerrit merge request in the request for change.
• The PTL submits a request to the ONAP Infratructure Coordinator (infrastructure-coordinator@onap.org) indicating the person, their email, Linux Foundation ID (LFID), and what repositories they should become committers on.
• The ONAP Infratructure Coordinator reviews the completeness and accuracy of the evidences and follows up with Linux Foundation for execution.

Removing a Committer:

• • over an extended period of time 

  • The PTL fills in Committer Promotion Request for [your-project-tag] 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 such as company wide layoffs have greatly diminished the Committer pool for the project and has also impacted the PTL as well. 

Removing a Committer:

• Voluntarily: 

  • Any Committer can step down

  A Committer may voluntarily resign

  • by informing the PTL and sending email to the onap-tsc list.

  A Committer can be removed by a PTL under the following conditions. The PTL is responsible for informing the Technical Steering Committee (TSC) of any committers who are removed via the ONAP-TSC email
  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
  • Demonstrated failure of the Committer to effectively perform her/his
    • duties for an extended period of time
    (
    • of 6 months or more
    )
    • .
  • A 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).
  • •   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
  vote to remove the Committer (
  • • . 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
  is required).
  
• After notifying the TSC, the PTL requests by email to the ONAP Infratructure Coordinator ( infrastructure-coordinator@onap.org  ) to remove the committer rights for the individual. Please include the committer name, email, LFID and list of repo(s) that the individual should be removed from.
• The PTL edits the INFO.yaml file associated with the repo(s) to delete the committer.
  • • 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. 
  • •