rfc:adopt-code-of-conduct

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:adopt-code-of-conduct [2016/01/05 16:12] – Add appeals process ircmaxellrfc:adopt-code-of-conduct [2016/01/07 18:00] – A buncch of major changes, wip ircmaxell
Line 1: Line 1:
 ====== PHP RFC: Adopt Code Of Conduct ====== ====== PHP RFC: Adopt Code Of Conduct ======
-  * Version: 0.3+  * Version: 0.4
   * Date: 2016-01-04   * Date: 2016-01-04
   * Author: Anthony Ferrara <ircmaxell@php.net>   * Author: Anthony Ferrara <ircmaxell@php.net>
Line 70: Line 70:
 ==== Mailing List ==== ==== Mailing List ====
  
-A new mailing list will be created at //codeofconduct@php.net// for use in reporting incidents and discussing them internally. This mailing list will be private and unarchived.+A new mailing list will be created at //codeofconduct@php.net// for use in reporting incidents and discussing them internally. This mailing list will be private.
  
-==== Response Team ====+==== Conflict Resolution Team ====
  
-A team of 5 volunteers shall be assembled who will make up the code of conduct team.+A team of 5 volunteers shall be assembled who will make up the Conflict Resolution Team.
  
 The team shall consist of: The team shall consist of:
Line 85: Line 85:
 All team members will be elected by RFC vote (requiring 2/3 majority).  All team members will be elected by RFC vote (requiring 2/3 majority). 
  
-There is no specified term limit, but if either the PHP project or the other members of the CoC team feel that a specific member is not doing their job, they can be removed by an RFC vote (requiring 50% + 1 to support removal).+There is no specified term limit, but if either the PHP project or the other members of the Conflict Resolution Team feel that a specific member is not doing their job, they can be removed by an RFC vote (requiring 50% + 1 to support removal).
  
-==== Process For Incidents ====+==== Process For Reported Incidents ====
  
 In the event that an incident is reported the following process should be followed: In the event that an incident is reported the following process should be followed:
  
-  * A CoC team member is notified of an incident+  * A Conflict Resolution Team member is notified of an incident
   * The team member documents the issue as best as possible, researching any supporting materials necessary   * The team member documents the issue as best as possible, researching any supporting materials necessary
-  * The team member makes a recommended course-of-action to the CoC team +  * The team member shall make contact with the accused offending party and document their side as much as possible 
-  * The CoC team will vote internally on the recommended course-of-action+  * The team member shall make every reasonable attempt to mediate and defuse the situation without needing to resort to punishment 
 + 
 +If all reasonable efforts to reach a mediated agreement fail and punitive action is deemed necessary (it should always be a last resort): 
 + 
 +  * The team member makes a recommended course-of-action to the Conflict Resolution Team 
 +  * The CoC team will vote internally on the recommended course-of-action (4/5 majority required to affect any action)
   * The CoC shall report a redacted summary of the incident and the course-of-action to //internals@php.net//   * The CoC shall report a redacted summary of the incident and the course-of-action to //internals@php.net//
  
 At all steps the reporter(s) should be kept up to date on the process and recommendations that are made. At all steps the reporter(s) should be kept up to date on the process and recommendations that are made.
- 
-All votes on recommended course-of-action shall require 4 team members to agree. 
  
 ==== Reasonable Person Test ==== ==== Reasonable Person Test ====
  
-To determine if the incident is a violation or not, the CoC team shall use the [[https://en.wikipedia.org/wiki/Reasonable_person|Reasonable Person Test]]. +To determine if the incident is a violation or not, the Conflict Resolution Team shall use the [[https://en.wikipedia.org/wiki/Reasonable_person|Reasonable Person Test]]. 
  
 The following four points shall be taken into account for any incident: The following four points shall be taken into account for any incident:
Line 118: Line 121:
 ==== Potential Actions ==== ==== Potential Actions ====
  
-The CoC team should make every reasonable attempt to defuse the situation without having to resort to "punishment". This includes establishing a meaningful discussion around the incident, giving the accused offender the chance to apologize (privately or publicly, depending on the incident) or determining that no action is necessary even if the CoC was violated.+The Conflict Resolution Team should make every reasonable attempt to defuse the situation without having to resort to "punishment". This includes establishing a meaningful discussion around the incident, giving the accused offender the chance to apologize (privately or publicly, depending on the incident) or determining that no action is necessary even if the CoC was violated.
  
 In the event that additional action is required, it may include: In the event that additional action is required, it may include:
Line 127: Line 130:
   * Issue temporary ban (no more than 7 days)   * Issue temporary ban (no more than 7 days)
  
-If the CoC team determines that a longer temporary ban or a permanent ban is necessary, they shall institute a temporary ban and raise an RFC to the general project to effect the desired ban. Once the RFC is issued, the temporary ban's lifetime will be tied to the RFC's lifetime (will expire when the vote is finished). All Ban RFCs will require 2/3 majority to affect the ban.+If the Conflict Resolution Team determines that a longer temporary ban or a permanent ban is necessary, they shall institute a temporary ban and raise an RFC to the general project to effect the desired ban. Once the RFC is issued, the temporary ban's lifetime will be tied to the RFC's lifetime (will expire when the vote is finished). All Ban RFCs will require 2/3 majority to affect the ban. However, this temporary ban shall not include the //internals@php.net// mailing list, provided that the accused party remains civil and reasonably within the CoC to ensure that they receive a fair representation during the ban discussion.
  
 A ban may include removal of commit karma, mailing list write access as well as disabling of the associated PHP.net account. Depending on the particular infraction, one, many or all access may be suspended. A ban may include removal of commit karma, mailing list write access as well as disabling of the associated PHP.net account. Depending on the particular infraction, one, many or all access may be suspended.
Line 139: Line 142:
 Either party may appeal an action by raising the concern to internals@php.net. PHP project members may then vote to overturn or strengthen the action as necessary (votes require 50%+1 to overturn, and 2/3 majority to strengthen the action). Either party may appeal an action by raising the concern to internals@php.net. PHP project members may then vote to overturn or strengthen the action as necessary (votes require 50%+1 to overturn, and 2/3 majority to strengthen the action).
  
-It is worth noting that this may be used as a technique to attempt to disclose the reporter to make them the subject of public scrutiny. Therefore reasonable attempts at confidentiality should be maintained, and the teams (CoC team and PHP project members) should keep this in mind. +It is worth noting that this may be used as a technique to attempt to disclose the reporter to make them the subject of public scrutiny. Therefore reasonable attempts at confidentiality should be maintained, and the teams (Conflict Resolution Team and PHP project members) should keep this in mind. 
  
 ==== Confidentiality ==== ==== Confidentiality ====
  
-All incidents are to be kept in the strictest form of confidentiality. The CoC team shall be the only group to know about the reporter and the precise details of any incident. Any communication outside of the team (including fact-finding, investigation, documentation, etc) shall not include identifying information as to the reporter unless agreed by the reporter or is otherwise public.+All incidents are to be kept in the strictest form of confidentiality. The Conflict Resolution Team shall be the only group to know about the reporter and the precise details of any incident. Any communication outside of the team (including fact-finding, investigation, documentation, etc) shall not include identifying information as to the reporter unless agreed by the reporter or is otherwise public.
  
-Additionally, reasonable attempts shall be made as to the confidentiality to the accused person. This includes transparency reports where no significant action is taken (due to lack of evidence or that the CoC team determines it wasn't significant enough to warrant punishment).+Additionally, reasonable attempts shall be made as to the confidentiality to the accused person. This includes transparency reports where no significant action is taken (due to lack of evidence or that the Conflict Resolution Team determines it wasn't significant enough to warrant punishment).
  
 ==== Transparency ==== ==== Transparency ====
  
-Any action taken by the CoC team shall be reported to internals@php.net, including a summary of the incident and the action taken. The summary of the incident should include supporting evidence and justification for the decision.+Any punitive action taken by the Conflict Resolution Team shall be reported to internals@php.net, including a summary of the incident and the action taken. The summary of the incident should include supporting evidence and justification for the decision.
  
 Reasonable efforts should be taken to ensure the privacy of the reporting party. The only two exceptions would be if the incident was public or if the reporting party agrees to be identified.  Reasonable efforts should be taken to ensure the privacy of the reporting party. The only two exceptions would be if the incident was public or if the reporting party agrees to be identified. 
 +
 +Additionally, once per quarter (every 3 months), the Conflict Resolution Team shall produce an aggregated report as to the number of times incidents were reported, and the outcomes of the incidents, even if no punitive measures were taken.
  
 ==== Conflict of Interest ==== ==== Conflict of Interest ====
  
-In the event that a CoC violation is reported against a CoC team member, the remaining members shall investigate and raise the concern to internals@php.net, even if they determine no action is to be taken. +In the event that a CoC violation is reported against a Conflict Resolution Team member, the remaining members shall investigate and raise the concern to internals@php.net, even if they determine no action is to be taken. 
  
 ==== Accountability ==== ==== Accountability ====
  
-The PHP project voting body has the right to overturn any action taken the CoC team by vote (50% + 1 required to overturn).+The PHP project voting body has the right to overturn any action taken the Conflict Resolution Team by vote (50% + 1 required to overturn).
  
 ==== Updating Code Of Conduct ==== ==== Updating Code Of Conduct ====
Line 165: Line 170:
 Any changes to the text of the code of conduct, or updating the version of it shall require an RFC with 2/3 majority voting. Any changes to the text of the code of conduct, or updating the version of it shall require an RFC with 2/3 majority voting.
  
-===== Initial Team =====+===== Examples ===== 
 + 
 +==== "Representing The Project" ==== 
 + 
 +=== Activities on a php.net property === 
 + 
 +Activities on a php.net property shall always be considered "representing the project" and hence fall under the jurisdiction of the CoC and Conflict Resolution Team. 
 + 
 +=== Activities at a technology conference === 
 + 
 +While at a technology conference, the CoC is only considered to apply if and only if the person is demonstrably representing the project. 
 + 
 +For example, merely speaking at a conference about PHP is not enough to be "representing the project". However, when speaking about the project itself (meaning internals functions, etc), while the talk is occurring the CoC shall apply. 
 + 
 +This does not intend to limit the CoC applicability to only during a talk, however any violation that happens at a conference shall be assumed to **not** be representing the project unless there is significant and obvious evidence to the contrary. 
 + 
 +=== Activities on a social network === 
 + 
 +On social networks, the CoC is only considered to apply if the context of the conversation makes it clear that the person represents the PHP project. 
 + 
 +For example, merely having "PHP contributor" in an about or bio is not enough to be "representing the project". However, a conversation about the PHP project itself (including RFCs, etc) is enough to justify "representation". 
 + 
 +=== Other === 
 + 
 +In all cases, if an issue seems reasonably connected to a project matter, the CoC may apply depending on how strongly the connection is. 
 + 
 +For example, if one person is involved in a heated discussion on internals@, and then immediately after starts harassing another participant on another channel with similar tone, the harassment may be considered a violation. 
 + 
 +In no case should a casual connection be considered a violation (just because two people are both members of the project is not enough to form a connection). 
 + 
 + 
 +===== Initial Conflict Resolution Team =====
  
-This RFC will include a vote for the initial CoC team. A separate thread will be opened asking for volunteers. +This RFC will include a vote for the initial Conflict Resolution Team. A separate thread will be opened asking for volunteers. 
  
 ===== Vote ===== ===== Vote =====
Line 177: Line 213:
   * 0.2 - Move to 2/3 majority   * 0.2 - Move to 2/3 majority
   * 0.3 - Significant expansion of the RFC   * 0.3 - Significant expansion of the RFC
 +  * 0.4 - More significant expansion, adding examples
rfc/adopt-code-of-conduct.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools