forked from foss4g2018/foss4g2018
-
Notifications
You must be signed in to change notification settings - Fork 0
/
code-of-conduct.html
380 lines (346 loc) · 24.5 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
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Programme</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon" type="image/png" sizes="32x32"
href="/img/favicons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16"
href="/img/favicons/favicon-16x16.png">
<link rel="manifest" href="/img/favicons/manifest.json">
<link rel="mask-icon" href="/img/favicons/safari-pinned-tab.svg"
color="#5bbad5">
<link rel="shortcut icon" href="./img/favicon.ico">
<meta name="theme-color" content="#ffffff">
<link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css"
integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u"
crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="css/slick.css"/>
<link href="css/plugins.css" rel="stylesheet" type="text/css"/>
<link href="css/style.css" rel="stylesheet" type="text/css"/>
<link href="https://fonts.googleapis.com/css?family=Sintony:400,700"
rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Miriam+Libre:400,700"
rel="stylesheet">
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/slick.min.js"></script>
</head>
<body class="animated" data-animated="fadeIn">
<div class="wrapper">
<section class="js-include" title="includes/page-nav.html"
id="top"></section>
<section class="js-include" title="includes/branding-bar.html"
id="branding" style="margin-top: 80px;"></section>
<!-- page content -->
<section class="page_section header">
<div class="dark_blue_wrap" id="coc-header">
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2">
<h1>Code of Conduct</h1>
<div class="entry-content">
<div class="btns">
<a href="pdf/FOSS4GCodeOfConduct.pdf" class="shortcode_button" target="_blank">Download as PDF</a></div>
</div>
</div>
</div>
</div>
</div>
</section>
<section class="page_section header">
<div class="" id="code-of-conduct">
<div class="container">
<div class="row">
<div class="col-md-8 col-md-offset-2">
<p class="entry-content">
<p>
FOSS4G 2018 is a community conference intended
for networking and collaboration in the open
source geospatial community.
</p>
<p>
We value the participation of each member of
the FOSS4G community and want all attendees to
have an enjoyable and fulfilling experience.
Accordingly, all attendees are expected to show
respect and courtesy to other attendees
throughout the conference and at all conference
events, whether officially sponsored by FOSS4G
2018 or not.
</p>
<p>
To make clear what is expected, all
delegates/attendees, speakers, exhibitors,
organizers and volunteers at any FOSS4G 2018
event are required to conform to the following
Code of Conduct. Organizers will enforce this
code throughout the event.
</p>
<p>
Above and beyond this code of conduct, as an
OSGeo event, participants are expected to act
respectfully toward others in accordance with
the OSGEO code of conduct.
</p>
<h2>The Short Version</h2>
<p>
FOSS4G is dedicated to providing a
harassment-free conference experience for
everyone, regardless of gender, sexual
orientation, disability, physical appearance,
body size, race, or religion. We do not
tolerate harassment of conference participants
in any form.
</p>
<p>
All communication should be appropriate for a
professional audience including people of many
different backgrounds. Sexual language and
imagery is not appropriate for any conference
venue, including talks.
</p>
<p>
Be kind to others. Do not insult or put down
other attendees. Behave professionally.
Remember that harassment and sexist, racist, or
exclusionary jokes are not appropriate for
FOSS4G.
</p>
<p>
Attendees violating these rules may be asked to
leave the conference without a refund at the
sole discretion of the conference organizers.
</p>
<p>
Thank you for helping make this a welcoming,
friendly event for all.
</p>
<h2>The Longer Version</h2>
<p>
Harassment includes offensive communication
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 at sponsor 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 FOSS4G.
</p>
<p>
If a participant engages in behavior that
violates this code of conduct, the conference
organizers may take any action they deem
appropriate, including warning the offender or
expulsion from the conference with no refund.
</p>
<h2>Contact Information</h2>
<p>
If you are being harassed, notice that someone
else is being harassed, or have any other
concerns, please contact either our conference
chair or the event coordinators:
</p>
<ul style="font-size: large; margin-top: 10px; margin-bottom: 10px; padding-bottom: 10px; padding-top: 10px; border-bottom: solid white 1px; border-top: solid white 1px;">
<li>Maria Antonia Brovelli : maria.brovelli [at] polimi.it</li>
<li>Mark Iliffe : markiliffe [at] gmail.com </li>
<li>Msilikale Msilanga : msilikalemsilanga [at] gmail.com</li>
<li>Ragnvald Larson : ragnvald [at] mindland.com</li>
<li>Serena Coetzee : serenacoetzee [at] gmail.com</li>
</ul>
<p>Conference 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 conference. We
value your attendance.</p>
<h2>Procedure for Handling Harassment -
Attendees</h2>
<p>
This procedure has been adopted from the Ada
Initiative’s guide titled “Conference
anti-harassment/Responding to Reports” and
PyCon 2017’s policy.
</p>
<p>
Contact any staff personnel as listed above.
The staff will also be prepared to handle the
incident. All of our staff members are informed
of the code of conduct policy and guide for
handling harassment at the conference. There
will be a mandatory staff meeting onsite at the
conference when this will be reiterated as
well.
</p>
<p>
Report the harassment incident (preferably in
writing) to one of the contact people above -
all reports are confidential.
</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:
</p>
<ol>
<li>Identifying information (name) 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>
<li>The staff is well informed on how to deal with
the incident and how to further proceed with
the situation.</li>
</ol>
<p>If everyone is presently physically safe, staff
will 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 local law enforcement by dialing 911.
If you do not have a cell phone, you can use
any hotel phone or simply ask a staff member.
All reports should be made directly to one of
the staff listed above.</p>
<h2>Staff Procedure for incident
handling</h2>
<p>This procedure has been adopted from the Ada Initiative's guide titled " Conference anti-harassment/Responding to Reports ” and PyCon 2017’s similar document.
</p>
<p>Be sure to have a good understanding of our Code of Conduct policy, described above.
</p>
<p>Also have a good understanding of what is expected from an attendee that wants to report a harassment incident. (See section above outlining how attendees can report issues).
</p>
<p>If there is an immediately dangerous situation, do not hesitate to call 999 (Tanzanian police emergency) first.
</p>
<p>All reports should be made directly to the contact personnel mentioned above in this article.
</p>
<p>If contact cannot be made via phone or email, please proceed to the registration desk.
</p>
<p><strong>Incident Report</strong>
</p>
<p>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:
</p>
<ol>
<li>Identifying information (name) 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>
</ol>
<p><strong>Initial Response</strong></p>
<p>Prepare an initial response to the incident. This initial response is very important and will set the tone for FOSS4G 2017. Depending on the severity/details of the incident, please follow these guidelines:
<ol>
<li>If there is any general threat to attendees or the safety of anyone including conference staff is in doubt, summon security or police.</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>
<li>There are also some guidelines as to what not to do as an initial response:</li>
<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>
</ol>
<p><strong>Staff meeting</strong></p>
<p>Once something is reported at least two of Caitlin, Guido, Ashley and Michael should meet. The main objectives of this meeting is to find out the following:</p>
<ol>
<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>
</ol>
<p><strong>Follow-up with alleged harasser</strong></p>
<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.
Allow the alleged harasser to give their side of the story to the staff. After this point, if report stands, let the alleged harasser know what actions will be taken against them.
Some things for the staff to consider when dealing with Code of Conduct offenders (note that the list below is not a requirement and only applies if the staff deems it necessary based on the report):
</p>
<ol>
<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 immediately leave the event and not return</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>
<li>Additional common responses that are outside the scope of FOSS4G 2017, but are maintained here for future consideration:</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, and was not in 2017).</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 organizations</li>
</ol>
<p>Please keep in mind that it is not a good idea to encourage an apology from the harasser.
</p>
<p><strong>Follow-up communication</strong></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.
Depending on the incident, the conference chair or their 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.
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>
<p><strong>Record of Incident</strong></p>
<p>Record of incidents and actions taken is to be preserved for future LOC and OSGeo use to be able to recognize patterns of behavior. The experience of many other Conferences has shown that patterns of harassment often occur over multiple years and these records allow future staff and volunteers to react appropriately. Collections of incident records should be kept confidential and communicated from conference chair to conference chair or from conference chair to OSGeo Board of Directors as appropriate.
</p>
<h2>License</h2>
This Code of Conduct was forked from the PyCon 2017
Code of Conduct which was forked from the Geek
Feminism wiki, created by the Ada Initiative and
other volunteers which is under a Creative Commons
Zero license.
</p>
<p>
Creative Commons License
Conference Code of Conduct is licensed under a
Creative Commons Attribution 3.0 Unported License.
</p>
</div>
</div>
</div>
</div>
</div>
</section>
<section class="js-include" title="includes/sponsors.html"
id="sponsors"></section>
<!-- content-info adds the triangly bits behind the div -->
<footer class="content-info js-include" title="includes/footer.html"
id="contact"></footer>
<footer class="js-include" title="includes/footer-map.html"
id="map"></footer>
</div>
<!-- //wrapper -->
<header class="fixed-menu"></header>
<script type="text/javascript" src="js/jquery-ui.min.js"></script>
<script type="text/javascript" src="js/modules.js"></script>
<script type="text/javascript" src="js/current.js"></script>
<script type="text/javascript" src="js/foss4g.js"></script>
</body>
</html>