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 revision		Previous revision
Next revisionBoth sides next revision
rfc:adopt-code-of-conduct [2016/01/05 15:44] – Significant expansion ircmaxellrfc:adopt-code-of-conduct [2016/01/05 16:12] – Add appeals process ircmaxell
Line 107: Line 107:
 The following four points shall be taken into account for any incident: The following four points shall be taken into account for any incident:
  
- * the foreseeable risk of harm their actions create versus the utility of their actions +  * the foreseeable risk of harm their actions create versus the utility of their actions 
- * the extent of the risk so created +  * the extent of the risk so created 
- * the likelihood such risk will actually cause harm to others +  * the likelihood such risk will actually cause harm to others 
- * any alternatives of lesser risk, and the costs of those alternatives+  * any alternatives of lesser risk, and the costs of those alternatives
  
 Additionally, it shall be assumed that both parties (the accuser and the accused) are acting as reasonable people until proven otherwise. This means that best intentions shall be assumed unless significant evidence to the contrary is found. Additionally, it shall be assumed that both parties (the accuser and the accused) are acting as reasonable people until proven otherwise. This means that best intentions shall be assumed unless significant evidence to the contrary is found.
Line 127: Line 127:
   * 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).+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.
  
 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 134: Line 134:
  
 Bans (temporary or permanent) should only be used in egregious cases where a pattern of disregard for the CoC is demonstrated. Bans (temporary or permanent) should only be used in egregious cases where a pattern of disregard for the CoC is demonstrated.
 +
 +==== Appeals ====
 +
 +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. 
  
 ==== 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 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.
 +
 +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).
  
 ==== Transparency ==== ==== Transparency ====
Line 143: Line 151:
 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 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.
  
-Reasonable efforts should be taken to ensure the privacy of the reporting party. The only two exceptions would be if the incident was public and 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. 
  
 ==== Conflict of Interest ==== ==== Conflict of Interest ====
rfc/adopt-code-of-conduct.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools