rfc:adopt-code-of-conduct
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:adopt-code-of-conduct [2016/01/05 15:52] – formatting ircmaxell | rfc:adopt-code-of-conduct [2016/01/05 16:12] – Add appeals process ircmaxell | ||
---|---|---|---|
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, | 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, | ||
+ | |||
+ | Additionally, | ||
==== Transparency ==== | ==== Transparency ==== |
rfc/adopt-code-of-conduct.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1