@@ -2,7 +2,7 @@ Reporting Guidelines
2
2
====================
3
3
4
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 >`
5
+ it to the :doc: `CARE team </contributing/code_of_conduct/care_team >`
6
6
by emailing, Twitter, in person or any way you see fit.
7
7
8
8
**All reports will be kept confidential. ** The privacy of everyone included in
@@ -19,28 +19,28 @@ 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
- * 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.
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
31
32
32
What happens after you file a report?
33
33
-------------------------------------
34
34
35
- You will receive a reply from the :doc: `enforcement team </contributing/code_of_conduct/enforcement_team >`
35
+ You will receive a reply from the :doc: `CARE team </contributing/code_of_conduct/care_team >`
36
36
acknowledging receipt as soon as possible, but within 24 hours.
37
37
38
38
The team member receiving the report will immediately contact all or some other
39
- enforcement team members to review the incident and determine:
39
+ CARE team members to review the incident and determine:
40
40
41
- * What happened.
42
- * Whether this event constitutes a Code of Conduct violation.
43
- * What kind of response is appropriate.
41
+ * What happened.
42
+ * Whether this event constitutes a Code of Conduct violation.
43
+ * What kind of response is appropriate.
44
44
45
45
If this is determined to be an ongoing incident or a threat to physical safety,
46
46
the team's immediate priority will be to protect everyone involved. This means
@@ -50,16 +50,16 @@ and that everyone is physically safe.
50
50
Once the team has a complete account of the events, they will make a decision as
51
51
to how to respond. Responses may include:
52
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.
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
63
64
64
We'll respond within one week to the person who filed the report with either a
65
65
resolution or an explanation of why the situation is not yet resolved.
@@ -69,20 +69,20 @@ let them know what action (if any) we'll be taking. We'll take into account feed
69
69
from the reporter on the appropriateness of our response, but our response will be
70
70
determined by what will be best for community safety.
71
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
72
+ The CARE team keeps a private record of all incidents. By default all reports
73
+ are shared with the entire CARE team unless the reporter specifically asks
74
+ to exclude specific CARE team members, in which case these CARE team
75
75
members will not be included in any communication on the incidents as well as records
76
76
created related to the incidents.
77
77
78
- Enforcement team members are expected to inform the enforcement team and the reporters
78
+ CARE team members are expected to inform the CARE team and the reporters
79
79
in case of conflicts on interest and recuse themselves if this is deemed a problem.
80
80
81
81
Appealing the response
82
82
----------------------
83
83
84
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 >`
85
+ of the working group, contact the :doc: `CARE team </contributing/code_of_conduct/care_team >`
86
86
with your appeal and they will review the case.
87
87
88
88
Document origin
0 commit comments