1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
|
{% extends "conduct/base.html" %}
{% load i18n %}
{% block title %}{% translate "Django Code of Conduct - Enforcement Manual" %}{% endblock %}
{% block og_title %}{% translate "Django Code of Conduct - Enforcement Manual" %}{% endblock %}
{% block og_description %}{% translate "This is the enforcement manual followed by Django's Code of Conduct working group" %}{% endblock %}
{% block content %}
<h1>{% translate "Django Code of Conduct - Enforcement Manual" %}</h1>
<h2 class="deck">
{% blocktranslate trimmed %}
This is the enforcement manual followed by Django's Code of
Conduct working group. It's used when we respond to an issue to make sure we're
consistent and fair. It should be considered an internal document, but we're
publishing it publicly in the interests of transparency.
{% endblocktranslate %}</h2>
<h3>{% translate "The Code of Conduct Working Group" %}</h3>
<p>
{% url 'members:teams' as teams_url %}
{% blocktranslate trimmed %}
All responses to reports of conduct violations will be managed by the
<a href="{{ teams_url }}#code-of-conduct-team">Code of Conduct working group</a>.
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
The Django Software Foundation's Board of Directors ("the board") will establish
this working group, comprised of at least three members. One member will be
designated chair of the working group and will be responsible for all reports back to
the board. The board will review membership on a regular basis.
{% endblocktranslate %}</p>
<h3>{% translate "How the working group will respond to reports" %}</h3>
<p>
{% blocktranslate trimmed %}
When a report is sent to the working group they will immediately reply to the
report to confirm receipt. This reply must be sent within 24 hours, and the
working group should strive to respond much quicker than that.
{% endblocktranslate %}</p>
{% url 'conduct_reporting' as conduct_reporting %}
<p>
{% blocktranslate trimmed %}
See the <a href="{{ conduct_reporting }}">reporting guidelines</a> for details of
what reports should contain. If a report doesn't contain enough information, the
working group will obtain all relevant data before acting. The working group is
empowered to act on the DSF's behalf in contacting any individuals involved to
get a more complete account of events.
{% endblocktranslate %}</p>
<p>{% translate "The working group will then review the incident and determine, to the best of their ability:" %}
<ul>
<li>{% translate "what happened" %}</li>
<li>{% translate "whether this event constitutes a code of conduct violation" %}</li>
<li>{% translate "who, if anyone, was the bad actor" %}</li>
<li>{% translate "whether this is an ongoing situation, and there is a threat to anyone's physical safety" %}</li>
</ul>
</p>
<p>
{% blocktranslate trimmed %}
This information will be collected in writing, and whenever possible the
working group's deliberations will be recorded and retained (i.e. chat transcripts, email
discussions, recorded voice conversations, etc).
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
The working group should aim to have a resolution agreed upon within one week.
In the event that a resolution can't be determined in that time, the working group will
respond to the reporter(s) with an update and projected timeline for resolution.
{% endblocktranslate %}</p>
<h3>{% translate "Acting Unilaterally" %}</h3>
<p>
{% blocktranslate trimmed %}
If the act is ongoing (such as someone engaging in harassment on the forum), or involves
a threat to anyone's safety (e.g. threats of violence), any working group member
may act immediately (before reaching consensus) to end the situation. In ongoing
situations, any member may at their discretion employ any of the tools available
to the working group, including bans and blocks.
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
If the incident involves physical danger, any member of the working group may --
and should -- act unilaterally to protect safety. This can include contacting
law enforcement (or other local personnel) and speaking on behalf of the DSF.
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
In situations where an individual working group member acts unilaterally, they must
report their actions to the working group for review within 24 hours.{% endblocktranslate %}</p>
<h3>{% translate "Resolutions" %}</h3>
<p>
{% blocktranslate trimmed %}
The working group must agree on a resolution by consensus. If the working group cannot
reach consensus and deadlocks for over a week, the working group will turn the matter
over to the board for resolution.{% endblocktranslate %}</p>
<p>{% translate "Possible responses may include:" %}
<ul>
<li>{% translate "Taking no further action (if we determine no violation occurred)." %}</li>
<li>
{% blocktranslate trimmed %}
A private reprimand from the working group to the individual(s) involved.
In this case, a working group member will deliver that reprimand to the individual(s)
over email, cc'ing the working group.{% endblocktranslate %}</li>
<li>
{% blocktranslate trimmed %}
A public reprimand. In this case, a working group member will deliver that reprimand
in the same venue that the violation occurred (i.e. in the forum for a forum violation;
email for an email violation, etc.). The working group may choose to publish this message
elsewhere for posterity.{% endblocktranslate %}</li>
<li>
{% blocktranslate trimmed %}
An imposed vacation (i.e. asking someone to "take a week off" from the forum).
A working group member will communicate this "vacation" to the individual(s).
They'll be asked to take this vacation voluntarily, but if they don't agree then
a temporary ban may be imposed to enforce this vacation.{% endblocktranslate %}</li>
<li>
{% blocktranslate trimmed %}
A permanent or temporary ban from some or all Django spaces (the forum,
etc.). The working group will maintain records of all such bans so that they may be
reviewed in the future, extended to new Django fora, or otherwise maintained.
{% endblocktranslate %}</li>
<li>
{% blocktranslate trimmed %}
A request for a public or private apology. a working group member will deliver this request.
The working group may, if it chooses, attach "strings" to this request: for example,
the working group may ask a violator to apologize in order to retain his or her membership
on the forum.{% endblocktranslate %}</li>
</ul>
</p>
<p>
{% blocktranslate trimmed %}
Once a resolution is agreed upon, but before it is enacted, the working group
will contact the original reporter and any other affected parties and explain
the proposed resolution. The working group will ask if this resolution is
acceptable, and must note feedback for the record. However, the working group is
not required to act on this feedback.
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
Finally the working group will make a report for the DSF board. In case the
incident or report involves a current member of the board, the working group will
provide the report only to the other board members.
{% endblocktranslate %}</p>
<p>
{% blocktranslate trimmed %}
The working group will never publicly discuss the issue; all public statements
will be made by the DSF board.
{% endblocktranslate %}</p>
<h3>{% translate "Conflicts of Interest" %}</h3>
{% url 'conduct_reporting' as url%}
<p>
{% blocktranslate trimmed %}
In the event of any conflict of interest a working group member must immediately
notify the other members, and recuse themselves if necessary. If a report concerns
a possible violation by a current working group member, this member should be
excluded from the response process. For these cases, anyone can make a report
directly to any of the working group chairs, as documented in the
<a href="{{ url }}">reporting guidelines</a>.
{% endblocktranslate %}</p>
<hr>
<p><i>
{% blocktranslate trimmed %}
Editor's note: Writing this document posed a unique challenge. Most
similar guides are written on the assumption of an in-person event. However, the
Django community doesn't exist in one place, and most of the time we're spread
out across the world and interact online. This makes trying to define and
enforce community standards a different type of challenge. This document is
adapted from the <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports">Ada Initiative template</a> and the <a href="https://us.pycon.org/2013/about/code-of-conduct/harassment-incidents/">PyCon 2013 Procedure for
Handling Harassment Incidents</a>, but changed to reflect the nature of our
community. It is our expectation that this will be a living document and change
as we grow to understand how to meet this challenge and best serve our community
and ideals.{% endblocktranslate %}</i>
</p>
{% endblock %}
|
