@@ -12,20 +12,20 @@ that's the case, the identities of all victims, reporters, and the accused will
12
12
remain confidential unless those individuals instruct us otherwise. The details
13
13
of the incident may also be generalized.
14
14
15
- If you believe anyone is in physical danger, please notify appropriate emergency
16
- services first by calling the relevant local authorities. If you are unsure what
17
- service or agency is appropriate to contact, include this in your report and we
18
- will attempt to notify them.
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
19
20
20
In your report please include:
21
21
22
22
* Your contact info for follow-up contact.
23
23
* Names (legal, nicknames, or pseudonyms) of any individuals involved.
24
24
* If there were other witnesses besides you, please try to include them as well.
25
25
* When and where the incident occurred. Please be as specific as possible.
26
- * Your account of what occurred.
26
+ * Your description of what occurred.
27
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.
28
+ public IRC or Slack log), please include a link and a screenshot .
29
29
* Any extra context you believe existed for the incident.
30
30
* If you believe this incident is ongoing.
31
31
* Any other information you believe we should have.
@@ -36,7 +36,8 @@ What happens after you file a report?
36
36
You will receive a reply from the :doc: `enforcement team </contributing/code_of_conduct/enforcement_team >`
37
37
acknowledging receipt as soon as possible, but within 24 hours.
38
38
39
- The team will immediately meet to review the incident and determine:
39
+ The team member receiving the report will immediately contact all or some other
40
+ enforcement team members to review the incident and determine:
40
41
41
42
* What happened.
42
43
* Whether this event constitutes a Code of Conduct violation.
@@ -59,12 +60,12 @@ to how to respond. Responses may include:
59
60
spaces (events, meetings, mailing lists, IRC, Slack, etc.)
60
61
* A request to engage in mediation and/or an accountability plan.
61
62
* On a case by case basis, other actions may be possible but will usually be
62
- coordinated with the core- team.
63
+ coordinated with the core team and Symfony .
63
64
64
65
We'll respond within one week to the person who filed the report with either a
65
66
resolution or an explanation of why the situation is not yet resolved.
66
67
67
- Once we've determined our final action , we'll contact the original reporter to
68
+ Once we've determined our final actions , we'll contact the original reporter to
68
69
let them know what action (if any) we'll be taking. We'll take into account feedback
69
70
from the reporter on the appropriateness of our response, but our response will be
70
71
determined by what will be best for community safety.
@@ -93,7 +94,6 @@ Reporting Guidelines derived from those of the `Stumptown Syndicate`_ and the
93
94
94
95
Adopted by `Symfony `_ organizers on 21 February 2018.
95
96
96
-
97
97
.. _`Stumptown Syndicate` : http://stumptownsyndicate.org/code-of-conduct/reporting-guidelines/
98
98
.. _`Django Software Foundation` : https://www.djangoproject.com/conduct/reporting/
99
99
.. _`Symfony` : https://symfony.com
0 commit comments