Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

Adding or removing a Committer is governed by the ONAP Technical Community Document. It 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.   

The technical process to add or remove a Committer is automated. Please see Committer Management Automation via INFO.yaml for the HOW-TO

The administrative processes to add or remove a Committer can take several forms

When a new ONAP project is proposed the initial list of Committers for the project must be provided as part of the New Project Proposals template.   The specific A list of Committers for a new ONAP Project is provided by the initial Project owner as part of the Project Proposal 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 .

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 TSC Charter.

The Charter has the official language and specific details that must be adhered to, but in a nutshell it works like this:

Adding a Committer:   Committer Request Template

when it launches. 

Adding a Committer

  • Community Driven

    • The existing
  • The sitting
    • 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)
  • The PTL submits a request to the ONAP Infratructure Coordinator (Gildas Lanilis) indicating the person, their email, Linux Foundation ID (LFID), and what repositories they should become committers on.
    • over an extended period of time 
    • The PTL fills in the 

      Create from template
      templateName85426205
      templateId85426205
      titleCommitter Promotion for [your-project-name] : Committer Name
      buttonLabelCommitter Promotion Template
       and moves it under their project's wiki hierarchy after saving it.

    • The PTL follows the technical process to add the Committer

  • 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. When this happens a helpdesk ticket is usually required for RelEng assistance in making the necessary technical changes. 
    The ONAP Infratructure Coordinator reviews the completeness and accuracy of the evidences and follows up with Linux Foundation for execution.

Removing a Committer:

  • Voluntarily

    • Any Committer can step down

    A Committer may voluntarily resign
    • by informing the PTL and

    sending email to
    • cc 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 follow the technical process 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.
      )
      •    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 follow the technical process for any impacted repos.  Committer lists are often scrubbed by PTLs at the start of a new release cycle just because that is a convenient time to take stock of where a particular project community stands with regards to engagement and participation.  
    • Vote of the sitting Committers

      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)

      • 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 (Gildas Lanilis) 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
    • 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 to then follow the technical process for any impacted repos.
    • Action by the TSC

      • Under exceptional circumstances the TSC intervene 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. When this happens a helpdesk ticket is usually required for RelEng assistance in making the necessary technical changes.