rfc:adopt-code-of-conduct
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:adopt-code-of-conduct [2016/01/04 20:55] – Spelling ircmaxell | rfc:adopt-code-of-conduct [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Adopt Code Of Conduct ====== | ====== PHP RFC: Adopt Code Of Conduct ====== | ||
- | * Version: 0.1 | + | * Version: 0.5 |
- | * Date: 2016-01-04 | + | * Date: 2016-01-20 |
- | * Author: Anthony Ferrara < | + | * Author: Derick Rethans < |
- | * Status: | + | * Original |
+ | * Status: | ||
* First Published at: http:// | * First Published at: http:// | ||
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, | ||
+ | |||
+ | This proposal consists of several parts: | ||
+ | |||
+ | * A general "Code of Conduct", | ||
+ | * A set of guidelines to foster collaboration on proposed language features through RFCs [[guidelines]]. | ||
+ | * 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 ===== | ||
- | This RFC proposes for the PHP project to adopt the [[http:// | + | ==== Code of Conduct |
- | ==== Website Page ==== | + | This RFC proposes for the PHP project to adopt [[http:// |
- | A page will be created on php.net at // | + | === Code of Conduct |
- | ==== Mailing List ==== | + | Contributor Code of Conduct |
- | A new mailing list will be created at // | + | As contributors and maintainers of this project, and in the interest of |
+ | fostering an open and welcoming community, we pledge to respect all | ||
+ | people who contribute through reporting issues, posting feature | ||
+ | requests, updating documentation, | ||
+ | and other activities. | ||
- | ==== Response Team ==== | + | We are committed to making participation in this project a |
+ | harassment-free experience for everyone, regardless of level of | ||
+ | experience, gender, gender identity and expression, sexual orientation, | ||
+ | disability, personal appearance, body size, race, ethnicity, age, | ||
+ | religion, or nationality. | ||
- | A team of 5 volunteers shall be assembled who will make up the code of conduct team. | + | Examples |
- | The team shall consist | + | * The use of sexualized language or imagery |
+ | * Personal attacks | ||
+ | * Trolling or insulting/ | ||
+ | * Public or private harassment | ||
+ | * Publishing other' | ||
+ | * Other unethical or unprofessional conduct | ||
- | * At least one person with commit karma to php-src | + | Project maintainers have the right and responsibility |
- | * At least one person with commit karma to php-documentation | + | or reject comments, commits, code, wiki edits, issues, and other |
+ | contributions that are not aligned | ||
+ | temporarily or permanently any contributor for other behaviours that they | ||
+ | deem inappropriate, | ||
- | As long as the preceding two seats are filled, there is no karma requirement (wiki or otherwise) for the remaining three seats. | + | By adopting this Code of Conduct, project maintainers commit themselves |
+ | to fairly and consistently applying these principles to every aspect of | ||
+ | managing this project. Project maintainers who do not follow | ||
+ | the Code of Conduct may be permanently removed from the project team. | ||
- | All team members will be elected by RFC vote. | + | This Code of Conduct applies both within project spaces and in public |
+ | spaces when an individual is representing the project or its community. | ||
- | There is no specified term limit, but if either the PHP project or the other members | + | Instances |
+ | be reported | ||
+ | All complaints will be reviewed and investigated and will | ||
+ | result in a response that is deemed necessary and appropriate to the | ||
+ | circumstances. Maintainers are obligated to maintain confidentiality | ||
+ | with regard to the reporter of an incident. | ||
- | ==== Process For Incidents | + | This Code of Conduct is adapted from the Contributor Covenant |
+ | (http:// | ||
+ | http:// | ||
+ | |||
+ | === Website Page === | ||
+ | |||
+ | A page will be created on php.net at // | ||
+ | |||
+ | ==== Constructive Collaboration Guidelines ==== | ||
+ | |||
+ | 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 language. Currently, too little time is focussed on improving RFCs; instead a lot of effort exists to torpedo RFCs, attack suggestions and opinions. The point of the RFC process to to **improve** PHP — and the RFCs themselves. | ||
+ | |||
+ | Below are several suggestions: | ||
+ | |||
+ | * 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", | ||
+ | * Think before you send " | ||
+ | * Debate the technical issues, and never attack a person' | ||
+ | |||
+ | === Website Page === | ||
+ | |||
+ | A page will be created on php.net at // | ||
+ | |||
+ | |||
+ | ==== Complaints procedure ==== | ||
+ | |||
+ | === Mailing List === | ||
+ | |||
+ | A new mailing list will be created at // | ||
+ | |||
+ | === Process For Reported | ||
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 | + | |
- | * 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 |
- | | + | * A team member documents the issue as best as possible, researching any supporting materials necessary |
- | | + | * A team member |
- | * The CoC shall report a redacted summary of the incident | + | * A team member |
- | The CoC team shall have the power to directly: | + | If all reasonable efforts |
- | * Revert or edit existing commits | + | |
- | | + | * The Community Mediation Team will vote internally on the recommended course-of-action (4/5 majority required to affect any action) |
- | * Revert/reject wiki edits, issues and other contributions | + | * The Community Mediation Team shall report a redacted summary of the incident and the course-of-action to // |
- | | + | |
- | * 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). | + | At all steps the reporter(s) should |
- | ==== Bans ==== | + | === Confidentiality |
- | A ban shall include removal of commit karma, mailing list write access as well as disabling of the associated PHP.net account. | + | 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, |
+ | |||
+ | Additionally, | ||
+ | |||
+ | |||
+ | === Reasonable Person Test === | ||
+ | |||
+ | To determine if the incident is a violation or not, the Conflict Resolution Team shall use the [[https:// | ||
+ | |||
+ | 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 extent of the risk so created | ||
+ | * the likelihood such risk will actually cause harm to others | ||
+ | * any alternatives of lesser risk, and the costs of those alternatives | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | 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 " | ||
+ | |||
+ | |||
+ | ==== 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, | ||
+ | |||
+ | 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, | ||
+ | |||
+ | ==== Potential Actions ==== | ||
+ | |||
+ | 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: | ||
+ | |||
+ | * Revert or edit existing commits | ||
+ | * Reject pull requests | ||
+ | * Revert/ | ||
+ | * Issue temporary ban (no more than 7 days) | ||
+ | |||
+ | 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 | ||
+ | |||
+ | 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/ | A new address/ | ||
- | ==== Confidentiality | + | Bans (temporary or permanent) should only be used in egregious cases where a pattern of disregard for the CoC is demonstrated. |
+ | |||
+ | === 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). | ||
+ | |||
+ | 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. | ||
+ | |||
+ | ==== Additional Sections ==== | ||
+ | |||
+ | === Conflict of Interest === | ||
+ | |||
+ | 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, | ||
+ | |||
+ | === Accountability === | ||
+ | |||
+ | 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 === | ||
+ | |||
+ | 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 Contributor Guidelines shall require an RFC with 2/3 majority voting. | ||
+ | |||
+ | |||
+ | ===== Examples ===== | ||
+ | |||
+ | ==== " | ||
+ | |||
+ | === Activities on a php.net property === | ||
+ | |||
+ | Activities on a php.net property shall always be considered " | ||
+ | |||
+ | === 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 " | ||
+ | |||
+ | 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" | ||
+ | |||
+ | === 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). | ||
- | 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, | ||
- | ===== Initial Team ===== | + | ===== Initial |
- | This RFC will include a vote for the initial | + | This RFC will include a vote for the initial |
===== Vote ===== | ===== Vote ===== | ||
- | This RFC requires | + | This RFC requires |
===== Changelog ===== | ===== Changelog ===== | ||
* 0.1 - Initial Draft | * 0.1 - Initial Draft | ||
+ | * 0.2 - Move to 2/3 majority | ||
+ | * 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.1451940941.txt.gz · Last modified: 2017/09/22 13:28 (external edit)