/
code_of_conduct.html
353 lines (339 loc) · 18.7 KB
/
code_of_conduct.html
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
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
<!doctype html>
<html lang="en">
<head>
<title>Coding Grace - Code of Conduct</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="/static/css/bootstrap.min.css">
<link rel="stylesheet" href="/static/css/style.css">
</head>
<body>
<header>
<nav class="navbar navbar-inverse navbar-fixed-top" role="navigation">
<div class="container-fluid">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/">Coding Grace</a>
</div>
<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav">
<li ><a href="/">Home</a></li>
<li><a href="http://blog.codinggrace.com">Blog</a></li>
<!--<li ><a href="about.html">About</a></li>-->
<li ><a href="/#about">About</a></li>
<li class="active"><a href="/#conduct">Code of Conduct</a></li>
</ul>
</div>
</div> <!-- container-fluid -->
</nav>
</header>
<div class="container-fluid">
<div class="page-header">
<div class="row">
<div class="col-md-2">
<img src="/static/images/codinggrace-logo.png" alt="Coding Grace Logo">
</div>
<div class="col-md-6">
<h1></h1>
</div>
<div class="col-md-3">
<div class="well">
Irish-based not-for-profit organisation who organise female friendly coding workshops and events.
</div>
</div>
</div>
</div>
<div class="container-fluid">
<section>
<h1>The Long Version</h1>
<p>
Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical
appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking,
following, harassing photography or recording, sustained disruption of talks or other events, inappropriate
physical contact, and unwelcome sexual attention.
</p>
<p>
Participants asked to stop any harassing behavior are expected to comply immediately.
</p>
<p>
Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the
anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other
material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or
otherwise create a sexualized environment.
</p>
<p>
Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be
offensive to those around you. Excessive swearing and offensive jokes are not appropriate for Coding Grace.
</p>
<p>
If a participant engages in behavior that violates this code of conduct, the event organisers may take any
action they deem appropriate, including warning the offender or expulsion from the event with no refund
(if any).
</p>
</section>
<section>
<div class="row">
<div class="col-md-6">
<h2>Contact information</h2>
<p>
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please
contact a member of Coding Grace. You may also contact venue staff and ask to be put in touch with the
organiser of the event.
</p>
<p>
If the matter is especially urgent, please call/contact any of these individuals:
<ul>
<li>
<span class="glyphicon glyphicon-user"></span> Vicky Twomey-Lee || <span class="glyphicon glyphicon-envelope"></span> <a href="mailto:codinggrace@gmail.com">codinggrace@gmail.com</a> || <span class="glyphicon glyphicon-earphone"></span> +353 86 150 2003
</li>
</ul>
</p>
<p>
Coding Grace staff will be happy to help participants contact venue security or local law enforcement,
provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event.
We value your attendance.
</p>
</div>
<div class="col-md-6">
<h2>License</h2>
<p>
This Code of Conduct was forked from the example policy from the <a href="https://github.com/python/pycon-code-of-conduct">
PyCon Code of Conduct on Github</a> which is under a Creative Commons Zero license.
</p>
<p>
(Events Code of Conduct by Coding Grace is licensed under a Creative Commons Attribution 3.0 Unported License.)
</p>
</div>
</div>
</section>
<div class="divide"></div>
<section>
<h1>Handling Harassment</h1>
<h2>Attendee Procedure for incident handling</h2>
<p>
This procedure has been adopted from the Ada Initiative’s guide titled
<a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports">
“Conference anti-harassment / Responding to Reports”</a>.
</p>
<ol>
<li>
<p>
Staff will also be prepared to handle the incident. All of our staff are informed of the
code of conduct policy and guide for handling harassment at the events.
</p>
</li>
<li>
<p>
Report the harassment incident (preferably in writing) to a events staff member. All
reports are confidential. Please do not disclose public information about the incident
until the staff have had sufficient time in which to address the situation. This is as
much for your safety and protection as it is the other attendees.
</p>
<p>
When reporting the event to staff, try to gather as much information as available but do
not interview people about the incident. Staff will assist you in writing the
report/collecting information.
</p>
<p>
The important information consists of:
<ol>
<li>Identifying information (name/badge number) of the participant doing the harassing</li>
<li>The approximate time of the behavior (if different than the time the report was made)</li>
<li>The circumstances surrounding the incident</li>
<li>Other people involved in the incident</li>
</ol>
</p>
<p>
The staff is well informed on how to deal with the incident and how to further proceed
with the situation.
</p>
</li>
<li>
If everyone is presently physically safe, involve law enforcement or security only at a victim’s
request. If you do feel your safety in jeopardy please do not hesitate to contact the Gardaí by
dialing 112. If you do not have a cell phone, you can use any hotel phone or
simply ask a staff member.
</li>
</ol>
<h2>Staff Procedure for incident handling</h2>
<p>
This procedure has been adopted from the Ada Initiative’s guide titled
<a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports">
“Conference anti-harassment/Responding to Reports”.
</a>
</p>
<div class="row">
<div class="col-md-6">
<h4>
Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it
yourself as it was told to you. The important information to gather include the following:
</h4>
<ul>
<li>Identifying information (name/badge number) of the participant doing the harassing</li>
<li>The behavior that was in violation</li>
<li>The approximate time of the behavior (if different than the time the report was made)</li>
<li>The circumstances surrounding the incident</li>
<li>Other people involved in the incident</li>
</ul>
<h4>
Prepare an initial response to the incident. This initial response is very important and will set
the tone for PyCon. Depending on the severity/details of the incident, please follow these
guidelines.
</h4>
<ul>
<li>
If there is any general threat to attendees or the safety of anyone including conference staff
is in doubt, summon security or Gardaí
</li>
<li>Offer the victim a private place to sit</li>
<li>
Ask “is there a friend or trusted person who you would like to be with you?” (if so, arrange
for someone to fetch this person)
</li>
<li>Ask them “how can I help?”</li>
<li>Provide them with your list of emergency contacts if they need help later</li>
<li>
If everyone is presently physically safe, involve law enforcement or security only at a
victim’s request
</li>
</ul>
<h4>There are also some guidelines as to what not to do as an initial response:</h4>
<ul>
<li>
Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This
suggests that you want them to do so, and is therefore coercive. “If you’re OK with it
[pursuing the complaint]” suggests that you are by default pursuing it and is not coercive.
</li>
<li>
Do not ask for their advice on how to deal with the complaint. This is a staff responsibility.
</li>
<li>
Do not offer them input into penalties. This is the staff’s responsibility.
</li>
</ul>
<h4>
Once something is reported to a staff member, immediately meet with the conference chair and/or
event coordinator. The main objectives of this meeting is to find out the following:
</h4>
<ul>
<li>What happened?</li>
<li>Are we doing anything about it?</li>
<li>Who is doing those things?</li>
<li>When are they doing them?</li>
</ul>
<p>
After the staff meeting and discussion, have a staff member (preferably the conference chair or
event coordinator if available) communicate with the alleged harasser. Make sure to inform them of
what has been reported about them.
</p>
<p>
Allow the alleged harasser to give their side of the story to the staff. After this point, if the
report stands, let the alleged harasser know what actions will be taken against them.
</p>
</div>
<div class="col-md-6">
<h4>Some things for the staff to consider when dealing with Code of Conduct offenders:</h4>
<ul>
<li>
Warning the harasser to cease their behavior and that any further reports will result in sanctions
</li>
<li>
Requiring that the harasser avoid any interaction with, and physical proximity to, their
victim for the remainder of the event
</li>
<li>Ending a talk that violates the policy early</li>
<li>Not publishing the video or slides of a talk that violated the policy</li>
<li>
Not allowing a speaker who violated the policy to give (further) talks at the event now or in
the future
</li>
<li>Immediately ending any event volunteer responsibilities and privileges the harasser holds</li>
<li>
Requiring that the harasser not volunteer for future events your organization runs (either
indefinitely or for a certain time period)
</li>
<li>
Requiring that the harasser refund any travel grants and similar they received (this would
need to be a condition of the grant at the time of being awarded)
</li>
<li>Requiring that the harasser immediately leave the event and not return</li>
<li>Banning the harasser from future events (either indefinitely or for a certain time period)</li>
<li>Removing a harasser from membership of relevant organisations</li>
<li>
Publishing an account of the harassment and calling for the resignation of the harasser from
their responsibilities (usually pursued by people without formal authority: may be called for
if the harasser is the event leader, or refuses to stand aside from the conflict of interest,
or similar, typically event staff have sufficient governing rights over their space that this
isn’t as useful)
</li>
</ul>
<p>
Give accused attendees a place to appeal to if there is one, but in the meantime the report stands.
Keep in mind that it is not a good idea to encourage an apology from the harasser.
</p>
<p>
It is very important how we deal with the incident publicly. Our policy is to make sure that
everyone aware of the initial incident is also made aware that it is not according to policy and
that official action has been taken - while still respecting the privacy of individual attendees.
When speaking to individuals (those who are aware of the incident, but were not involved with the
incident) about the incident it is a good idea to keep the details out.
</p>
<p>
Depending on the incident, the conference chair, or designate, may decide to make one or more public
announcements. If necessary, this will be done with a short announcement either during the plenary
and/or through other channels. No one other than the conference chair or someone delegated authority
from the conference chair should make any announcements. No personal information about either party
will be disclosed as part of this process.
</p>
<p>If some attendees were angered by the incident, it is best to apologize to them that the incident
occurred to begin with. If there are residual hard feelings, suggest to them to write an email to
the conference chair or to the event coordinator. It will be dealt with accordingly.
</p>
</div>
</div>
</section>
<section>
<div class="row">
<div class="col-md-6">
<h2>Staff Contact</h2>
<ul>
<li>
<span class="glyphicon glyphicon-user"></span> Vicky Twomey-Lee || <span class="glyphicon glyphicon-envelope"></span> <a href="mailto:codinggrace@gmail.com">codinggrace@gmail.com</a> || <span class="glyphicon glyphicon-earphone"></span> +353 86 150 2003
</li>
</ul>
</div>
<div class="col-md-6">
<h2>Other Information</h2>
<ul>
<li>
<a href="https://www.python.org/psf/codeofconduct/">Python Software Foundation (PSF)'s Code of Conduct</a>
</li>
<li><a href="http://python.org/community/diversity/">Python Community’s Diversity Page</a></li>
<li>
<a href="http://www.letsgetlouder.com/">http://www.letsgetlouder.com/</a> - Pledging here means “As a member of the Python community,
we pledge only to attend, speak at, assist, sponsor, or otherwise participate in conferences
that publicly promote an anti-harassment and anti-discrimination code of conduct policy.”
</li>
<li><a href="http://geekfeminism.wikia.com/wiki/Code_of_conduct">Geek Feminism - Code of Conduct</a></li>
</ul>
</div>
</div>
</section>
</div>
</div>
<footer>
<section>
Coding Grace 2013 - 2014 || <a href="http://twitter.com/codinggrace">@codinggrace</a> || <a href="https://www.facebook.com/pages/Coding-Grace/501098363273457">Facebook Page</a>
</section>
</footer>
<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
<script src="/static/js/bootstrap.min.js"></script>
</body>
</html>