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 revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
rfc:adopt-code-of-conduct [2016/01/05 16:12]
ircmaxell Add appeals process
rfc:adopt-code-of-conduct [2016/01/20 18:44]
derick
Line 1: Line 1:
 ====== PHP RFC: Adopt Code Of Conduct ====== ====== PHP RFC: Adopt Code Of Conduct ======
-  * Version: 0.3 +  * Version: 0.5 
-  * Date: 2016-01-04 +  * Date: 2016-01-20 
-  * Author: Anthony Ferrara <​ircmaxell@php.net>​ +  * Author: Derick Rethans <​derick@php.net>​ 
-  * Status: ​Draft+  * Original ​Author: Anthony Ferrara <​ircmaxell@php.net>​ 
 +  * Status: ​Reopened
   * First Published at: http://​wiki.php.net/​rfc/​adopt-code-of-conduct   * First Published at: http://​wiki.php.net/​rfc/​adopt-code-of-conduct
  
Line 9: Line 10:
  
 This RFC proposes that the PHP project should adopt a formal code of conduct for its members. This RFC proposes that the PHP project should adopt a formal code of conduct for its members.
 +
 +The goal of this code of conduct is to give a clear signal what is expected of contributors and project maintainers,​ regarding their conduct in discussions on mailing lists, and other related communication channels. More specifically,​ the expected conduct in discussing language improvements and changes through the RFC process.
 +
 +This proposal consists of several parts:
 +
 +  * A general "Code of Conduct",​ which provides a general overview on what constitutes as unacceptable behaviour
 +  * A set of guidelines to foster collaboration on proposed language features through RFCs
 +  * A set of procedures to follow if individuals wish to make complaints if other project members do not follow either the Code of Conduct or the Constructive Collaboration Guidelines.
 +  * A Contributor Mediation Team to asses and act upon the complaints as received through the above procedures
 +  * Possibilities for strong action if things really go awry regarding a project member. For example, if project members continue to violate the Collaboration Guidelines or Code of Conduct after several rounds of mediation and/or complaints.
  
 ===== Proposal ===== ===== Proposal =====
 +
 +==== Code of Conduct ====
  
 This RFC proposes for the PHP project to adopt [[http://​contributor-covenant.org/​|version 1.3.0 of the Contributor Covenant]] as a Code of Conduct. This RFC proposes for the PHP project to adopt [[http://​contributor-covenant.org/​|version 1.3.0 of the Contributor Covenant]] as a Code of Conduct.
  
-==== Code of Conduct Text ====+=== Code of Conduct Text ===
  
 Contributor Code of Conduct Contributor Code of Conduct
Line 30: Line 43:
 religion, or nationality. religion, or nationality.
  
-Examples of unacceptable ​behavior ​by participants include:+Examples of unacceptable ​behaviour ​by participants include:
  
   * The use of sexualized language or imagery   * The use of sexualized language or imagery
Line 42: Line 55:
 or reject comments, commits, code, wiki edits, issues, and other or reject comments, commits, code, wiki edits, issues, and other
 contributions that are not aligned to this Code of Conduct, or to ban contributions that are not aligned to this Code of Conduct, or to ban
-temporarily or permanently any contributor for other behaviors ​that they+temporarily or permanently any contributor for other behaviours ​that they
 deem inappropriate,​ threatening,​ offensive, or harmful. deem inappropriate,​ threatening,​ offensive, or harmful.
  
Line 53: Line 66:
 spaces when an individual is representing the project or its community. spaces when an individual is representing the project or its community.
  
-Instances of abusive, harassing, or otherwise unacceptable ​behavior ​may+Instances of abusive, harassing, or otherwise unacceptable ​behaviour ​may
 be reported by contacting a project maintainer at codeofconduct@php.net. ​ be reported by contacting a project maintainer at codeofconduct@php.net. ​
 All complaints will be reviewed and investigated and will All complaints will be reviewed and investigated and will
Line 64: Line 77:
 http://​contributor-covenant.org/​version/​1/​3/​0/​ http://​contributor-covenant.org/​version/​1/​3/​0/​
  
-==== Website Page ====+=== Website Page ===
  
 A page will be created on php.net at //​php.net/​codeofconduct//​ that will display the actual language of the code of conduct used above: [[http://​contributor-covenant.org/​version/​1/​3/​0/​code_of_conduct.md|Code Of Conduct]] A page will be created on php.net at //​php.net/​codeofconduct//​ that will display the actual language of the code of conduct used above: [[http://​contributor-covenant.org/​version/​1/​3/​0/​code_of_conduct.md|Code Of Conduct]]
  
-==== Mailing List ====+==== Constructive Collaboration Guidelines ​====
  
-new mailing list will be created at //​codeofconduct@php.net// for use in reporting incidents ​and discussing them internallyThis mailing list will be private ​and unarchived.+This section presents a loose collection of guidelines that focus on encouraging constructive feedback on language proposals (RFCs). RFCs are  used to introduce ​new features into the languageCurrently, too little time is focussed on improving RFCs; instead a lot of effort exists to torpedo RFCs, attack suggestions ​and opinionsThe point of the RFC process to to **improve** PHP — and the RFCs themselves.
  
-==== Response Team ====+Below are several suggestions:​
  
-A team of 5 volunteers shall be assembled who will make up the code of conduct team.+  * Post infrequently. Take the time to read the existing thread. In general, don't send more than one post per hour about a single topic.  
 +  * Write clear and unambiguous prose. It is better to be descriptive than to be concise. 
 +  * Write as much as is necessary, but as little as you can get away with.  
 +  * Suggest improvements to the RFC, don't just shoot it down. 
 +  * Don't use hyperboles to defend your arguments. 
 +  * Don't send a "quick email",​ especially during a heated debate. 
 +  * Think before you send "​reply"​. Consider how the other party is likely to feel with the content. And, how you would feel if the same text was directed at you. Emotions are important and difficult, especially when you have never met in person. 
 +  * Debate the technical issues, and never attack a person'​s opinion. People will disagree, so be it.
  
-The team shall consist of:+=== Website Page ===
  
-  * At least one person with commit karma to php-src +A page will be created on php.net at //php.net/​collaboration-guidelines//​ that will display the collaboration guidelines as described above.
-  * At least one person with commit karma to php-documentation+
  
-As long as the preceding two seats are filled, there is no karma requirement (wiki or otherwise) for the remaining three seats. 
  
-All team members will be elected by RFC vote (requiring 2/3 majority). ​+==== Complaints procedure ==== 
 + 
 +=== Mailing List ===
  
-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).+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.
  
-==== 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 +  * The Community Mediation Team is notified of an incident ​through //​codeofconduct@php.net//​ 
-  * The team member documents the issue as best as possible, researching any supporting materials necessary +  * The Community Mediation Team should pick a case handler to deal with each specific incident 
-  * The team member makes a recommended course-of-action to the CoC team +  * A team member documents the issue as best as possible, researching any supporting materials necessary 
-  * The CoC team will vote internally on the recommended course-of-action +  * A team member shall make contact with the accused offending party and document their side as much as possible 
-  * The CoC shall report a redacted summary of the incident and the course-of-action to //​internals@php.net//​+  * A 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 other action is deemed absolutely necessary as a last resort: 
 + 
 +  * The team member makes a recommended course-of-action to the Community Mediation Team 
 +  * The Community Mediation Team will vote internally on the recommended course-of-action ​(4/5 majority required to affect any action) 
 +  * The Community Mediation Team 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.+=== Confidentiality === 
 + 
 +All incidents are to be kept in the strictest form of confidentiality. The Community Mediation 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 Community Mediation Team determines it wasn't significant enough to warrant punitive action). 
  
-==== 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 115: Line 146:
  
 Note: reporting an incident does not absolve a person of the requirement to abide by the CoC. This means that the victim of harassment is not entitled to "​harass back"​. ​ Note: reporting an incident does not absolve a person of the requirement to abide by the CoC. This means that the victim of harassment is not entitled to "​harass back"​. ​
 +
 +
 +==== Community Mediation Team ====
 +
 +A team of 5 volunteers shall be assembled who will make up the Community Mediation Team.
 +
 +The team shall consist of:
 +
 +  * At least one person with commit karma to php-src
 +  * At least one person **without** any karma to php-src
 +  * At least one person with commit karma to php-documentation
 +
 +As long as the preceding three seats are filled, there is no karma requirement (wiki or otherwise) for the remaining three seats.
 +
 +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 Community Mediation 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).
 +
 +=== Transparency ===
 +
 +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. ​
 +
 +Additionally,​ once per quarter (every 3 months), the Community Mediation 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.
  
 ==== 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 intention that nothing in this section is ever going to be needed. In extreme cases, when the Community Mediation Team finds that a certain project member continues to violate either the Code of Conduct or Constructive Contributing Guidelines, more punitive action **might** be required. 
 + 
 +The Community Mediation Team should make every reasonable attempt to defuse the situation without having to resort to punitive action. 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 185:
   * 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 necessarythey 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 Community Mediation Team (with 4/5th majority as described above) ​determines that punitive action ​is required, an RFC to the general project ​is created. 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 corrective action ​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.+Punitive action ​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 new address/​account which is believed to be used by an already banned individual does not require a RFC to effect provided there is reasonable evidence to support the correlation. A new address/​account which is believed to be used by an already banned individual does not require a RFC to effect provided there is reasonable evidence to support the correlation.
Line 135: Line 193:
 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 ​====+=== Appeals ​to Punitive 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). 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 (Community Mediation Team and PHP project members) should keep this in mind. 
  
-==== Confidentiality ​====+==== Additional Sections ​====
  
-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.+=== Conflict ​of Interest ===
  
-Additionallyreasonable attempts ​shall be made as to the confidentiality ​to the accused personThis 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).+In the event that a CoC violation is reported against a Conflict Resolution Team memberthe remaining members ​shall investigate and raise the concern ​to internals@php.net, even if they determine ​no action is to be taken
  
-==== Transparency ====+=== Accountability ​===
  
-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.+The PHP project voting body has the right to overturn any action taken the Conflict Resolution Team by vote (50% + 1 required to overturn).
  
-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+=== Updating Code Of Conduct === 
 + 
 +Any changes ​to the text of the Code of Conduct, or updating the version of it shall require an RFC with 2/3 majority votingAny changes to the text of the Contributor Guidelines shall require an RFC with 2/3 majority voting. 
 + 
 + 
 +===== 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 Community Mediation Team. This includes any php.net mailing list.  
 + 
 +=== 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.
  
-==== Conflict of Interest ====+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"​.
  
-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. ​+=== Other ===
  
-==== Accountability ====+In all cases, if an issue seems reasonably connected to a project matter, the CoC may apply depending on how strongly the connection is.
  
-The PHP project voting body has the right to overturn any action taken the CoC team by vote (50% + 1 required to overturn).+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.
  
-==== Updating Code Of Conduct ====+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).
  
-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 =====+===== Initial ​Community Mediation ​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 ​Community Mediation Team. A separate thread will be opened asking for volunteers. ​
  
 ===== Vote ===== ===== Vote =====
Line 177: Line 257:
   * 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
 +  * 0.5 - Focus more on mediation than punishment. Rename the Conflict Resolution Team to Contributor Mediation Team. Reshuffle content. Added Constructive Collaboration Guidelines.
rfc/adopt-code-of-conduct.txt · Last modified: 2017/09/22 13:28 (external edit)