Maintenance of Committer Lists
It is important for OPNFV projects to maintain their list of committers, so project work can execute properly e.g. by doing necessary votes or patch approvals. The actual list of committers of a project can always be seen in the INFO file in the project repository.
Besides adding new committers to a project (for details of the process see https://wiki.opnfv.org/developer/committer_promotions), there are also cases where names need to be removed from the list of committers.
While we like to maintain and support our committers remaining engaged and active in the community it is not always possible for these individuals to remain active as committers in OPNFV. At times committers will step down from their roles and on occasion may be removed without themselves being in a position to stand down.
The removal of a committer from a project must take place according to Section 8 of the TSC Charter. This page intends to describe how the charter shall be interpreted in a practical step by step manner.
In general there are three scenarios where a project will need to remove a name on the committer list:
- Committers may choose to stand down / retire from a project when they no longer have the time or ability to engage effectively in the project.
- It may also be that at times committers simply drift away from a project without communicating their intent to stand down.
- In hopefully rare cases, it might happen that a committer is perceived to be disruptive to the project and the peaceful work in the project is compromised or even damaged.
We need to describe the process for all three cases.
In general it is preferable that committers themselves stand down / retire from a project when they determine they no longer intend to perform the role as expected of them. They may still remain active and contribute to the project although not in the capacity of a committer.
This is done in the form of an e-mail to the project stating their intention to stand down from the role of committer. In this situation the PTL will then update the INFO file in the repository and forward the e-mail to the TSC (email@example.com) and the helpdesk (firstname.lastname@example.org) for administrative handling. It is important this e-mail contain the original e-mail from the committer indicating their desire to stand down from the position.
Removal of inactive committers
At times it may be that a committer is unable to continue their work on a project and that the project leader is not able to get in contact with the committer to request that they retire from the committer role.
In this case the PTL may notify the TSC that the inactive committer is being removed from the project. The PTL then must demonstrate:
- Sufficient evidence that the PTL has attempted to contact the committer in question. Typically this can be done by declaring that the committer in question:
- was not present in the project meetings for more than 6 months (see participant lists in the minutes or IRC); AND
- did not contribute any patch for the project for more than 6 months; AND
- did not participate in the email discussion of the project for more than 6 month
- An approval by the project's committers to remove the committer in question from the project, i.e. no objections within a week.
In addition, a committer may be removed if they have not accessed the project gerrit for 12 months or more. This process may be initiated by the project lead, another project committer, or by LF staff. In this case, the current or most recent PTL must be contacted and given an opportunity to decline the removal. The removal may proceed if the PTL agrees to the removal, or if the PTL does not respond within two weeks of notification. In addition, the current or most recent PTL must be added as a reviewer to the Gerrit change.
The PTL (or other removal process initiator) must notify the TSC mailing list (email@example.com) on the inactive committer removal. The PTL will then update the INFO file (or file a ticket to firstname.lastname@example.org for administrative handling). Please note the section on "Contesting a committer removal" below.
Removal of disruptive committers
In the instance a committer is perceived to be disruptive, the PTL may agree with other committers to remove the disruptive committer from the project. In this instance the PTL must demonstrate:
- Sufficient evidence that the committer in question has in fact been disruptive.
- Note that fighting of a position, solution or opinion cannot be considered disruptive
- Only damage to the project's results or severe compromising behaviour over a considerable period should be considered disruptive
- Sufficient evidence that mediation has occured on the issues highlighted including parties outside of the project's committer pool, and no other consensus could be found.
- A vote of standing committers to remove the committer in question from the project.
The PTL must notify the TSC mailing list (email@example.com) on the committer removal. The PTL will then update the INFO file (or file a ticket to firstname.lastname@example.org for administrative handling). Please note the section on "Contesting a committer removal" below.
This is in accordance to the TSC charter which states: " A Committer who is disruptive, or has been inactive for an extended period (e.g., six or more months) may have his or her Committer status revoked by the Project Lead. The Project Lead is responsible for informing the TSC of any committers that are removed."
Contesting a committer removal
The TSC is responsible for overseeing the processes for maintaining the committer lists. In the case that any member of the OPNFV community would like to raise discussion or has concerns over a committer removal, or the committer removal process, they should reach out to the TSC via the TSC mailing list email@example.com, or if preferred the TSC Chair Person directly to identify if further action or intervention by the TSC is needed.