Become A Committer

Revision as of 16:43, 24 May 2023 by Dwallacelf (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

How To Become A Project Committer

This page is provides an overview of how a contributor to a project can become a committer.

What Is A Committer?

The committer role is defined in Technical Community Document section 3.1.2:

  • For each project there is a set of Contributors approved for the right to commit code to the source code management system (the “Committers”) for that project.
  • Committer rights are per project; being a Committer on one project does not give an individual committer rights on any other project.
  • The Committers will be the decision makers on all matters for a project including design, code, patches, and releases for a project.
  • Committers are the best available individuals, but usually work full-time on components in active development.

How Is A Committer Added To A Project?

The process of adding a committer to a project is specified in Technical Community Document section 3.2.2:

  • Initial Committers for a project will be specified at project creation.
  • Committer rights for a project are earned via code contribution and community trust.
  • Committers for a project select and vote for new Committers for that project, subject to TSC approval.
  • New Committers for a project should have a demonstrable established history of meritocratic code contribution.

Where Is The List Of Committers Maintained?

Each project maintains the official list of committers in the project git repository in the INFO.yaml file. Committers are also listed on the project wiki page on, however, this list may become stale and should not be taken as the official list.

What Are The Attributes Of Excellence For Committers?

  1. Active participation in project meetings, events, webinars, etc.
  2. Project contributions (code, documentation, tests, white papers, presentations, etc)
  3. Diligent & timely review of gerrit changes
  4. Personal commitment to supporting the project (above and beyond employer expectations)
  5. Personal accountability for content merged by committer (e.g. if a patch that you merged causes a problem, you take action to rectify the issue)
  6. Considerate and thoughtful interactions with all project contributors (i.e. in reviews, email discussions, meetings)
  7. Adherence to LFN's Antitrust Policy

How Do I Get Started On Becoming A Committer?

  1. Participate, participate, participate
    1. push gerrit changes
    2. make constructive review comments
    3. speak up at community meetings
    4. answer questions on email lists, slack channels, etc.
  2. Communicate your desire to become a committer directly with the project PTL or Committer and the TSC Chairperson
  3. Participate, participate, participate

What Happens Next?

After having convinced the PTL or another Committer to nominate you, a vote by the projects committers will be held on a publicly accessible email list with a list of your contributions to the project (typically from Once the vote concludes, if a majority of the project committers have voted for you, then the results of vote will be added to the TSC Meeting Agenda and the TSC will discuss and vote on your nomination.

How Do I Activate Git Merge Rights?

If the TSC approves, then you must follow the LFN Project Self-Service Committer Management instructions to activate merge rights to the project git repository.