User Tools

Site Tools


developer:committer_removal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
developer:committer_removal [2015/10/06 10:32]
Christopher Price created
developer:committer_removal [2015/10/20 14:31] (current)
Ulrich Kleber [Removal of inactive committers]
Line 1: Line 1:
-====== Committer ​Removal ​======+====== ​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. 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.
Line 5: Line 9:
 The removal of a committer from a project must take place according to Section 8 of the [[https://​www.opnfv.org/​developers/​technical-project-governance/​tsc-charter|TSC Charter]]. ​ This page intends to describe how the charter shall be interpreted in a practical step by step manner. The removal of a committer from a project must take place according to Section 8 of the [[https://​www.opnfv.org/​developers/​technical-project-governance/​tsc-charter|TSC Charter]]. ​ This page intends to describe how the charter shall be interpreted in a practical step by step manner.
  
-==== Reasons for committer removal ​====+==== Scenarios ​====
  
-Committers may choose to stand down 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 general there are three scenarios where a project ​will need to remove a name on the committer list:
  
-==== Committer removal procedures ====+  * 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.
  
-In general it is preferable that committers themselves stand down 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.+We need to describe ​the process for all three cases.
  
-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 opnfv-helpdesk@rt.linuxfoundation.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.+==== Committer retirement ====
  
-==== Alternative methods ​of committer ​removal ====+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.
  
-At times it may be that a standing ​committer is not able to be contacted by the project leader, ​or has been perceived by the project ​as disruptive.  ​As described in the TSC charter "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 TSC."+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 (opnfv-tsc@lists.opnfv.org) and the helpdesk (opnfv-helpdesk@rt.linuxfoundation.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 not able to continue his work for a project and the project leader ​is not able to get in contact with the committer any moree.g. to get his consent to retire from the committer role. 
 + 
 +In this case the PTL may request the TSC to agree to remove the committer 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 the instance a committer is not able to be contacted the PTL may request the TSC to agree to remove the committer from the project. ​ In this instance the PTL must demonstrate:​ 
-  * Sufficient evidence that the PTL has attempted to contact the committer in question. 
-  * A clear majority vote of standing committers to remove the committer in question from the project. 
 The PTL may address the TSC with the above information whereby the TSC will vote on the matter. ​ If the TSC votes to remove the committer the PTL will then update the INFO file in the repository and forward as e-mail referring to the TSC vote to opnfv-helpdesk@rt.linuxfoundation.org for administrative handling. The PTL may address the TSC with the above information whereby the TSC will vote on the matter. ​ If the TSC votes to remove the committer the PTL will then update the INFO file in the repository and forward as e-mail referring to the TSC vote to opnfv-helpdesk@rt.linuxfoundation.org for administrative handling.
 +
 +==== Removal of disruptive committers ====
  
 In the instance a committer is perceived to be disruptive the PTL may request the TSC to agree to remove the committer from the project. ​ In this instance the PTL must demonstrate:​ In the instance a committer is perceived to be disruptive the PTL may request the TSC to agree to remove the committer from the project. ​ In this instance the PTL must demonstrate:​
   * Sufficient evidence that the committer in question has in fact been disruptive.   * Sufficient evidence that the committer in question has in fact been disruptive.
-  ​* Sufficient evidence that mediation has occured on the issues highlighted including ​outside ​parties ​form the project committer pool.  +    * Note that fighting of a position, solution or opinion cannot be considered disruptive 
-  * A clear majority ​vote of standing committers to remove the committer in question from the project.+    * Only damage to the project'​s results or severe compromising behaviour over a considerable time should be considered disruptive 
 +  ​* Sufficient evidence that mediation has occured on the issues highlighted including parties ​outside from the project'​s ​committer pool, and no other consent could be found
 +  * A vote of standing committers to remove the committer in question from the project.
 The PTL may address the TSC with the above information whereby the TSC will vote on the matter. ​ If the TSC votes to remove the committer the PTL will then update the INFO file in the repository and forward as e-mail referring to the TSC vote to opnfv-helpdesk@rt.linuxfoundation.org for administrative handling. The PTL may address the TSC with the above information whereby the TSC will vote on the matter. ​ If the TSC votes to remove the committer the PTL will then update the INFO file in the repository and forward as e-mail referring to the TSC vote to opnfv-helpdesk@rt.linuxfoundation.org for administrative handling.
 +
 +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 TSC."
  
 ==== Contesting a committer removal ==== ==== Contesting a committer removal ====
    
-The TSC is responsible for overseeing the committer removal ​processes. ​ 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 opnfv-tsc@lists.opnfv.org,​ or if preferred the TSC Chair Person directly to identify if further action or intervention by the TSC is needed. ​+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 processthey should reach out to the TSC via the TSC mailing list opnfv-tsc@lists.opnfv.org,​ or if preferred the TSC Chair Person directly to identify if further action or intervention by the TSC is needed. ​
  
developer/committer_removal.1444127535.txt.gz · Last modified: 2015/10/06 10:32 by Christopher Price