Skip to content

Commit 2dbe26a

Browse files
NyholmNyholm
committed
Adding guidelines for reporting violations of code of conduct
1 parent a586997 commit 2dbe26a

File tree

3 files changed

+123
-5
lines changed

3 files changed

+123
-5
lines changed

‎contributing/code_of_conduct/enforcement_team.rst

Lines changed: 27 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,30 @@
11
Enforcement Team
22
================
33

4-
We're preparing the "Enforcement Team" for the new Symfony Code of Conduct.
5-
Come back to this article in a few days to see the members of that team.
4+
Our Pledge
5+
----------
6+
7+
In the interest of fostering an open and welcoming environment, the enforcement team
8+
pledge to ensure that the spirit of the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
9+
is respected. Our main priority is to ensure the safety of our community members.
10+
The second goal is to help educate the community as a whole to be aware of the CoC
11+
and how to help implement its spirit throughout the community. In case these goals
12+
conflict, we will prioritize safety of community members over all other goals.
13+
14+
If you think there is or has been a violation to the code of conduct please contact
15+
enforcement team or if you prefer contact only individual members of the enforcement team.
16+
17+
Members
18+
-------
19+
20+
Here are all the members of the Code of Conduct enforcement team. You can contact
21+
any of them directly using the contact details below or you can also contact all of
22+
them at once by emailing **[email protected]**.
23+
24+
About the Enforcement Team
25+
--------------------------
26+
27+
The :doc:`Symfony project leader </contributing/code/core_team>` appoints enforcement
28+
team with candidates they see fit. The enforcement team will consist of at least
29+
3 people. The team should be representing as many demographics as possible,
30+
ideally from different employers.

‎contributing/code_of_conduct/reporting_guidelines.rst

Lines changed: 95 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,98 @@
11
Reporting Guidelines
22
====================
33

4-
We're preparing the "Reporting Guidelines" to explain how can you report a
5-
violation of the new Symfony Code of Conduct. Come back to this article in a
6-
few days to see the process in detail.
4+
If you believe someone is violating the Code of Conduct we ask that you report
5+
it to the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
6+
by emailing, Twitter, in person or any way you see fit.
7+
8+
**All reports will be kept confidential.** The privacy of everyone included in
9+
the report is of our highest concern. Second to privacy there is transparency.
10+
After every report we will determine if a public statement should be made. If
11+
that's the case, the identities of all victims, reporters, and the accused will
12+
remain confidential unless those individuals instruct us otherwise. The details
13+
of the incident may also be generalized.
14+
15+
If you believe anyone is in physical danger or doing something that is against
16+
the law, please notify appropriate emergency services first by calling the relevant
17+
local authorities. If you are unsure what service or agency is appropriate to
18+
contact, include this in your report and we will attempt to notify them.
19+
20+
In your report please include:
21+
22+
* Your contact info for follow-up contact.
23+
* Names (legal, nicknames, or pseudonyms) of any individuals involved.
24+
* If there were other witnesses besides you, please try to include them as well.
25+
* When and where the incident occurred. Please be as specific as possible.
26+
* Your description of what occurred.
27+
* If there is a publicly available record (e.g. a mailing list archive or a
28+
public IRC or Slack log), please include a link and a screenshot.
29+
* If you believe this incident is ongoing.
30+
* Any other information you believe we should have.
31+
32+
What happens after you file a report?
33+
-------------------------------------
34+
35+
You will receive a reply from the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
36+
acknowledging receipt as soon as possible, but within 24 hours.
37+
38+
The team member receiving the report will immediately contact all or some other
39+
enforcement team members to review the incident and determine:
40+
41+
* What happened.
42+
* Whether this event constitutes a Code of Conduct violation.
43+
* What kind of response is appropriate.
44+
45+
If this is determined to be an ongoing incident or a threat to physical safety,
46+
the team's immediate priority will be to protect everyone involved. This means
47+
we may delay an "official" response until we believe that the situation has ended
48+
and that everyone is physically safe.
49+
50+
Once the team has a complete account of the events, they will make a decision as
51+
to how to respond. Responses may include:
52+
53+
* Nothing (if we determine no Code of Conduct violation occurred).
54+
* A private reprimand from the Code of Conduct response team to the individual(s)
55+
involved.
56+
* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
57+
list or Slack).
58+
* A permanent or temporary ban from some or all Symfony conference/community
59+
spaces (events, meetings, mailing lists, IRC, Slack, etc.)
60+
* A request to engage in mediation and/or an accountability plan.
61+
* On a case by case basis, other actions may be possible but will usually be
62+
coordinated with the core team and the Symfony company.
63+
64+
We'll respond within one week to the person who filed the report with either a
65+
resolution or an explanation of why the situation is not yet resolved.
66+
67+
Once we've determined our final actions, we'll contact the original reporter to
68+
let them know what action (if any) we'll be taking. We'll take into account feedback
69+
from the reporter on the appropriateness of our response, but our response will be
70+
determined by what will be best for community safety.
71+
72+
The enforcement team keeps a private record of all incidents. By default all reports
73+
are shared with the entire enforcement team unless the reporter specifically asks
74+
to exclude specific enforcement team members, in which case these enforcement team
75+
members will not be included in any communication on the incidents as well as records
76+
created related to the incidents.
77+
78+
Enforcement team members are expected to inform the enforcement team and the reporters
79+
in case of conflicts on interest and recuse themselves if this is deemed a problem.
80+
81+
Appealing the response
82+
----------------------
83+
84+
Only permanent resolutions (such as bans) may be appealed. To appeal a decision
85+
of the working group, contact the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
86+
with your appeal and they will review the case.
87+
88+
Document origin
89+
---------------
90+
91+
Reporting Guidelines derived from those of the `Stumptown Syndicate`_ and the
92+
`Django Software Foundation`_.
93+
94+
Adopted by `Symfony`_ organizers on 21 February 2018.
95+
96+
.. _`Stumptown Syndicate`: http://stumptownsyndicate.org/code-of-conduct/reporting-guidelines/
97+
.. _`Django Software Foundation`: https://www.djangoproject.com/conduct/reporting/
98+
.. _`Symfony`: https://symfony.com

‎contributing/index.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,6 @@ Contributing
88
code/index
99
documentation/index
1010
community/index
11+
code_of_conduct/index
1112

1213
.. include:: /contributing/map.rst.inc

0 commit comments

Comments
 (0)