forked from PyDataAmsterdam/amsterdam.pydata.org
-
Notifications
You must be signed in to change notification settings - Fork 9
/
coc.html
438 lines (310 loc) · 28.2 KB
/
coc.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
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
<!DOCTYPE HTML>
<!--
Spectral by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
--><html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PyData Global 2020</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!--[if lte IE 8]><script src="/assets/js/ie/html5shiv.js"></script><![endif]-->
<link rel="stylesheet" href="/assets/css/schedule-style.css">
<link rel="stylesheet" href="/assets/css/main.css">
<link rel="stylesheet" href="/assets/css/responsive.css">
<!--[if lte IE 8]><link rel="stylesheet" href="/assets/css/ie8.css" /><![endif]-->
<!--[if lte IE 9]><link rel="stylesheet" href="/assets/css/ie9.css" /><![endif]-->
<link rel="shortcut icon" href="/assets/favicon.ico">
<script>
(function (w,d,s,o,f,js,fjs) {
w[o] = w[o] || function () { (w[o].q = w[o].q || []).push(arguments) };
js = d.createElement(s), fjs = d.getElementsByTagName(s)[0];
js.id = o; js.src = f; js.async = 1; fjs.parentNode.insertBefore(js, fjs);
}(window, document, 'script', 'plausible', 'https://plausible.io/js/p.js'));
plausible('page')
</script>
</head>
<body>
<!-- Page Wrapper --> <style>
.meetup-link {
font-size: 11px !important;
margin-left: 15px
}
.meetup-list {
margin-bottom: 0px;
}
</style>
<div id="page-wrapper">
<!-- Header -->
<header id="header">
<script src="https://global.pydata.org/assets/js/jquery.min.js"></script>
<div id="header-title">
<img id="header-logo" src="https://global.pydata.org/assets/images/pydata.png"><h1><a href="https://global.pydata.org//">PyData Global 2020</a></h1>
</div>
<nav id="nav">
<ul>
<li class="special">
<a href="#menu" class="menuToggle"><span>Menu</span></a>
<div id="menu">
<ul>
<li><a href="https://global.pydata.org/">Home</a></li>
<li><a href="https://global.pydata.org/coc">Code of Conduct</a></li>
<li><a href="https://global.pydata.org/pages/community_sponsors">Community sponsors</a></li>
<li><a href="https://global.pydata.org/pages/format">Our Format</a></li>
<li><a href="https://global.pydata.org/pages/job_board">Job Board</a></li>
<li><a href="https://global.pydata.org/pages/newsletter">Newsletter</a></li>
<li><a href="https://global.pydata.org/pages/numfocus">About NumFocus</a></li>
<li><a href="https://global.pydata.org/pages/organizers">Organizing Committee</a></li>
<li><a href="https://global.pydata.org/pages/posters">Posters</a></li>
<li><a href="https://global.pydata.org/pages/program">Program</a></li>
<li><a href="https://global.pydata.org/pages/qa_panels">Q&A Panels</a></li>
<li><a href="https://global.pydata.org/pages/quick_start">Quick Start</a></li>
<li><a href="https://global.pydata.org/pages/schedule">Live Event Schedule</a></li>
<li><a href="https://global.pydata.org/pages/short_talks">Short Talks</a></li>
<li><a href="https://global.pydata.org/pages/sponsors">Sponsor PyData Global</a></li>
<li><a href="https://global.pydata.org/pages/sprints">Sprints</a></li>
<li><a href="https://global.pydata.org/pages/talk_release_schedule">Talk Release Schedule</a></li>
<li><a href="https://global.pydata.org/pages/tickets">Tickets & Scholarships</a></li>
</ul>
</div>
</li>
</ul>
</nav>
</header><script>
function getCompareDate() {
var d = new Date(),
month = '' + (d.getMonth() + 1),
day = '' + d.getDate(),
year = d.getFullYear();
if (month.length < 2) month = '0' + month;
if (day.length < 2) day = '0' + day;
return [year, month, day].join('');
}
var future_elements = document.querySelectorAll('[future-date]');
Array.prototype.forEach.call(future_elements, function(el, i){
if(el.getAttribute('future-date').split('-').join('') < getCompareDate()) el.remove();
});
var past_elements = document.querySelectorAll('[past-date]');
Array.prototype.forEach.call(past_elements, function(el, i){
if(el.getAttribute('past-date').split('-').join('') > getCompareDate()) el.remove();
});
</script>
<!-- Main -->
<article id="main">
<header>
<h2>Code of Conduct</h2>
<p></p>
</header>
<section class="wrapper style5">
<div class="inner">
<h1 id="pydata-global-code-of-conduct"><strong>PyData Global Code of Conduct</strong></h1>
<h2 id="the-short-version">The short version</h2>
<p>Do not insult or put down others. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for PyData Global.</p>
<p>All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate.</p>
<p>PyData Global is dedicated to providing a harassment-free community for everyone, regardless of gender, sexual orientation, gender identity and expression, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of community members in any form.</p>
<p><strong>To submit a report, you may use this form: <a href="https://forms.gle/UydhxLYdtBw2XJir9">PyData Global Code of Conduct Reporting Form</a></strong>. For other ways to submit a report, please check the <a href="#how-to-submit-a-report">how to submit a report</a> section.</p>
<p>Thank you for helping make this a welcoming, friendly community for all.</p>
<h2 id="code-of-conduct-table-of-contents"><strong>Code of Conduct Table of Contents</strong></h2>
<ul>
<li><a href="#diversity-statement">Diversity Statement</a></li>
<li><a href="#introduction--scope">Introduction & Scope</a></li>
<li><a href="#standards-for-behavior">Standards for Behavior</a></li>
<li><a href="#unacceptable-behavior">Unacceptable Behavior</a></li>
<li><a href="#reporting-guidelines">Reporting Guidelines</a></li>
<li><a href="#how-to-submit-a-report">How to Submit a Report</a></li>
<li><a href="https://forms.gle/UydhxLYdtBw2XJir9"><strong>Reporting Form</strong></a></li>
<li><a href="#persons-responsible-for-resolving-complaints">Person(s) Responsible for Resolving Complaints</a></li>
<li><a href="#conflicts-of-interest">Conflicts of Interest</a></li>
<li><a href="#what-to-include-in-a-report">What to Include in a Report</a></li>
<li><a href="#enforcement-what-happens-after-a-report-is-filed">Enforcement: What Happens After a Report is Filed?</a></li>
<li><a href="#appealing-a-decision">Appealing a Decision</a></li>
<li><a href="#timeline-summary">Timeline Summary</a></li>
<li><a href="#license">License</a></li>
</ul>
<h2 id="the-longer-version">The longer version</h2>
<h3 id="diversity-statement">Diversity Statement</h3>
<p>PyData Global welcomes and encourages participation in our community by people of all backgrounds and identities. We are committed to promoting and sustaining a culture that values mutual respect, tolerance, and learning, and we work together as a community to help each other live out these values.</p>
<p>We have created this diversity statement because we believe that a diverse community is stronger, more vibrant, and produces better software and better science. A diverse community where people treat each other with respect has more potential contributors, more sources for ideas, and fewer shared assumptions that might hinder development or research.</p>
<p>Although we have phrased the formal diversity statement generically to make it all-inclusive, we recognize that there are specific identities that are impacted by systemic discrimination and marginalization. We welcome all people to participate in the NumFOCUS community regardless of their identity or background.</p>
<h3 id="introduction--scope">Introduction & Scope</h3>
<p>This code of conduct should be honored by everyone who participates in the PyData Global conference and other PyData Global events. It should be honored in any conference-related activities, by anyone claiming affiliation with PyData Global, and especially when someone is representing PyData Global in any role (including as an event volunteer or speaker).</p>
<p>This code of conduct applies to all spaces managed by PyData Global, including all public and private mailing lists, issue trackers, wikis, forums, and any other communication channel used by our community. The code of conduct equally applies at PyData Global events and governs standards of behavior for attendees, speakers, volunteers, booth staff, and event sponsors.</p>
<p>This code is not exhaustive or complete. It serves to distill our understanding of a collaborative, inclusive community culture. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the PyData Global community.</p>
<p>The PyData Global Code of Conduct follows below.</p>
<h3 id="standards-for-behavior">Standards for Behavior</h3>
<p>PyData Global is a worldwide community. All communication should be appropriate for a professional audience including people of many different backgrounds.</p>
<p><strong>Please always be kind and courteous. There’s never a need to be mean or rude or disrespectful.</strong> Thank you for helping make this a welcoming, friendly community for all.</p>
<h4 id="we-strive-to">We strive to:</h4>
<p><strong>Be empathetic, welcoming, friendly, and patient.</strong> We work together to resolve conflict. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.</p>
<p><strong>Be inquisitive.</strong> Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.</p>
<p><strong>Be careful in the words that we choose.</strong> We are careful and respectful in our communication and we take responsibility for our own speech. Be kind to others. Do not insult or put down other members of the community.</p>
<h4 id="unacceptable-behavior"><strong>Unacceptable Behavior</strong></h4>
<p>We are committed to making participation in this community a harassment-free experience.</p>
<p><strong>We will not accept harassment or other exclusionary behaviors, such as:</strong></p>
<ul>
<li>The use of sexualized language or imagery</li>
<li>Excessive profanity (please avoid curse words; people differ greatly in their sensitivity to swearing)</li>
<li>Posting sexually explicit or violent material</li>
<li>Violent or intimidating threats or language directed against another person</li>
<li>Inappropriate physical contact and/or unwelcome sexual attention or sexual comments</li>
<li>Sexist, racist, or otherwise discriminatory jokes and language</li>
<li>Trolling or insulting and derogatory comments</li>
<li>Written or verbal comments which have the effect of excluding people on the basis of membership in a specific group, including level of experience, gender, gender identity and expression, sexual orientation, disability, neurotype, personal appearance, body size, race, ethnicity, age, religion, or nationality</li>
<li>Public or private harassment</li>
<li>Sharing private content, such as emails sent privately or non-publicly, or direct message history, without the sender’s consent</li>
<li>Continuing to initiate interaction (such as photography, recording, messaging, or conversation) with someone after being asked to stop</li>
<li>Sustained disruption of talks, events, or communications, such as heckling of a speaker</li>
<li>Publishing (or threatening to post) other people’s personally identifying information (“doxing”), such as physical or electronic addresses, without explicit permission</li>
<li>Other unethical or unprofessional conduct</li>
<li>Advocating for, or encouraging, any of the above behaviors</li>
</ul>
<h3 id="reporting-guidelines"><strong>Reporting Guidelines</strong></h3>
<p>If you believe someone is violating the code of conduct, please report this in a timely manner. Code of conduct violations reduce the value of the community for everyone. The team at PyData Global takes reports of misconduct very seriously and is committed to preserving and maintaining the welcoming nature of our community.</p>
<h4 id="all-reports-will-be-kept-confidential"><strong>All reports will be kept confidential.</strong></h4>
<p>In some cases we may determine that a public statement will need to be made. If that’s the case, the identities of all involved parties and reporters will remain confidential unless those individuals instruct us otherwise.</p>
<p>All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The PyData Global team commits to maintaining confidentiality with regard to the reporter of an incident.</p>
<p>For possibly unintentional breaches of the code of conduct, you may want to respond to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please report the issue to the PyData Global CoC response team directly, or fill out this form (https://forms.gle/UydhxLYdtBw2XJir9) with your report if you prefer to do this on your own.</p>
<p>Take care of each other. Alert the PyData Global CoC response team if you notice a dangerous situation, someone in distress, or violations of this code of conduct, even if they seem inconsequential.</p>
<h4 id="how-to-submit-a-report"><strong>How to Submit a Report</strong></h4>
<p><strong>If you feel your physical safety is in jeopardy or the situation is an emergency, we urge you to contact law enforcement before making a report to PyData Global.</strong></p>
<p>PyData Global is committed to promptly addressing any reported issues. If you have experienced or witnessed behavior that violates the PyData Global Code of Conduct during our event, please submit a report. You can do so in three different ways:</p>
<ol>
<li>
<strong>Submit a report through <a href="https://forms.gle/UydhxLYdtBw2XJir9">this form</a></strong>. Your form submission will be received by the PyData Global Code of Conduct Enforcement team. You will be notified by a member of the team when the form has been received.</li>
<li>
<strong>Submit an email to <a href="mailto:[email protected]">[email protected]</a></strong>. Your email will be received by the PyData Global Code of Conduct Enforcement team. You will be notified by a member of the team when the email has been received.</li>
<li>
<p><strong>During the conference, contact the on-duty member of the PyData Global Code of Conduct response team privately in Mattermost</strong>. You can find out who is on-duty by seeing the message pinned in the Mattermost channel here (<a href="https://forum.numfocus.org/pydata-global/channels/code-of-conduct-on-call-announcements">https://forum.numfocus.org/pydata-global/channels/code-of-conduct-on-call-announcements</a>) (you do not need to talk in the channel, you can make your report privately by sending a private direct message to the person on duty). Members of the response team will be able to take your report via either a private video chat or through written chat, as you prefer. Members of the response team include:</p>
<ol>
<li>Diego Torres Quintanilla, Executive Chair</li>
<li>Matthijs Brouns, Executive Vice-Chair</li>
<li>Sanket Verma, Executive Vice-Chair</li>
<li>Lisa Martin, Financial Administrator at NumFOCUS</li>
<li>Nicole Carlson, Diversity, Equity and Inclusion Chair</li>
</ol>
</li>
</ol>
<h4 id="persons-responsible-for-resolving-complaints">Person(s) Responsible for Resolving Complaints</h4>
<p>All reports of breaches of the code of conduct will be investigated and handled by the <strong>PyData Global Code of Conduct Enforcement Team or the NumFOCUS Board of Directors</strong>.</p>
<p>Members of the NumFOCUS Board of Directors can be found in the <a href="https://numfocus.org/community/people">NumFOCUS website</a>. The members of the PyData Global Code of Conduct enforcement team include:</p>
<ul>
<li>
<strong>Jane Adams</strong>, Executive Chair</li>
<li>
<strong>Diego Torres Quintanilla</strong>, Executive Chair</li>
<li>
<strong>Matthijs Brouns</strong>, Executive Vice-Chair</li>
<li>
<strong>Sanket Verma</strong>, Executive Vice-Chair</li>
<li>
<strong>Nicole Carlson</strong>, Diversity, Equity and Inclusion Chair</li>
</ul>
<h4 id="conflicts-of-interest"><strong>Conflicts of Interest</strong></h4>
<p>In the event of any conflict of interest, the team member will immediately notify the Board and recuse themselves if necessary.</p>
<p>If you are concerned about making a report that will be read by any of the above individuals, you can submit your report directly to the NumFOCUS board through <a href="mailto:[email protected]">[email protected]</a>.</p>
<h4 id="what-to-include-in-a-report"><strong>What to Include in a Report</strong></h4>
<p>Our ability to address any code of conduct breaches in a timely and effective manner is impacted by the amount of information you can provide, so, <strong>our reporting form asks you to include as much of the following information as you can:</strong></p>
<ul>
<li>Your contact info (so we can get in touch with you if we need to follow up). This will be kept confidential. If you wish to remain anonymous, your information will not be shared beyond the person receiving the initial report.</li>
<li>The approximate time and location of the incident (please be as specific as possible)</li>
<li>Identifying information (e.g. name, nickname, screen name, physical description) of the individual whose behavior is being reported</li>
<li>Description of the behavior (if reporting harassing language, please be specific about the words used), your account of what happened, and any available supporting records (e.g. email, GitHub issue, screenshots, etc.)</li>
<li>Description of the circumstances/context surrounding the incident</li>
<li>Let us know if the incident is ongoing, and/or if this is part of an ongoing pattern of behavior</li>
<li>Names and contact info, if possible, of anyone else who witnessed or was involved in this incident. (Did anyone else observe the incident?)</li>
<li>Any other relevant information you believe we should have</li>
</ul>
<p>The PyData Global CoC response team will attempt to gather and write down the above information from anyone making a verbal report in-person at an event. Recording the details in writing is exceedingly important in order for us to effectively respond to reports. If event staff/meetup organizers write down a report taken verbally, then the person making the report will be asked to review the written report for accuracy.</p>
<h3 id="enforcement-what-happens-after-a-report-is-filed"><strong>Enforcement: What Happens After a Report is Filed?</strong></h3>
<h4 id="acknowledgment-and-responding-to-immediate-needs"><strong>Acknowledgment and Responding to Immediate Needs</strong></h4>
<p>PyData Global staff and/or our event staff will attempt to ensure your safety and help with any immediate needs. PyData Global will make every effort to <strong>acknowledge receipt within 1 hour</strong> between 8:00 and 22:30 UTC, and in 5 hours outside those times (and we’ll aim for much more quickly than that).</p>
<h4 id="reviewing-the-report"><strong>Reviewing the Report</strong></h4>
<p>PyData Global will make all efforts to <strong>review the incident within 24 hours during conference days</strong> and determine:</p>
<ul>
<li>Whether this is an ongoing situation, or if there is a threat to anyone’s physical safety</li>
<li>What happened</li>
<li>Whether this event constitutes a code of conduct violation</li>
<li>Who the bad actor was, if any</li>
</ul>
<h4 id="contacting-the-person-reported"><strong>Contacting the Person Reported</strong></h4>
<p>After PyData Global has had time to review and discuss the report, someone will attempt to contact the person who is the subject of the report to inform them of what has been reported about them. We will then ask that person for their account of what happened.</p>
<h4 id="response-and-potential-consequences"><strong>Response and Potential Consequences</strong></h4>
<p>Once PyData Global has completed our investigation of the report, we will make a decision as to how to respond. The person making a report will not normally be consulted as to the proposed resolution of the issue, except insofar as we need to understand how to help them feel safe.</p>
<p>Potential consequences for violating the PyData Global code of conduct include:</p>
<ul>
<li>Nothing (if we determine that no violation occurred)</li>
<li>Private feedback or reprimand from PyData Global to the individual(s) involved</li>
<li>Warning the person to cease their behavior and that any further reports will result in sanctions</li>
<li>A public announcement that an incident occurred</li>
<li>Mediation (only if both reporter and reportee agree)</li>
<li>A permanent or temporary ban from some or all PyData Global spaces (mailing lists, GitHub repos, in-person events, etc.)</li>
<li>Assistance to the complainant with a report to other bodies, for example, institutional offices or appropriate law enforcement agencies</li>
<li>Removing a person from future PyData Global events and any formal affiliation to the PyData Global community</li>
<li>Publishing an account of the harassment and calling for the resignation of the alleged harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the person is the event leader, or refuses to stand aside from the conflict of interest, or similar)</li>
<li>Any other response that PyData Global deems necessary and appropriate to the situation</li>
</ul>
<p><strong>At PyData Global events</strong>, if a participant engages in behavior that violates this code of conduct, the conference organizers and staff may take any action they deem appropriate.</p>
<p>Potential consequences for violating the PyData Global Code of Conduct during the conference include:</p>
<ul>
<li>Warning the person to cease their behavior and that any further reports will result in sanctions</li>
<li>Requiring that the person avoid any interaction with the person they are harassing for the remainder of the event</li>
<li>Ending a session that violates the policy early</li>
<li>Not publishing or removing a recording of a talk or session that violated the policy</li>
<li>Not publishing or removing slides of a talk or session 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 reported person holds</li>
<li>Requiring that the person not volunteer for future PyData Global runs (either indefinitely or for a certain time period)</li>
<li>Requiring a person to immediately leave the event and not return without receiving a refund</li>
<li>Banning the person from future events (either indefinitely or for a certain time period)</li>
<li>Any other response that PyData Global deems necessary and appropriate to the situation</li>
</ul>
<p>No one espousing views or values contrary to the standards of our code of conduct will be permitted to hold any position representing PyData Global, including volunteer positions. PyData Global has the right and responsibility to remove, edit, or reject comments, Mattermost messages, commits, code, wiki edits, issues, and other contributions that are not aligned with this code of conduct.</p>
<p>We aim to <strong>respond within one week</strong> to the original reporter with either a resolution or an explanation of why the situation is not yet resolved.</p>
<p>We will contact the person who is the subject of the report to let them know what actions will be taken as a result of the report, if any.</p>
<p>Our policy is to make sure that everyone aware of the initial incident is also made aware that official action has been taken, while still respecting the privacy of individuals. PyData Global may choose to make a public report of the incident, while maintaining the anonymity of those involved.</p>
<h3 id="appealing-a-decision">Appealing a Decision</h3>
<p>To appeal a decision of PyData Global, you can contact the NumFOCUS board via <a href="mailto:[email protected]">[email protected]</a>.</p>
<h4 id="timeline-summary"><strong>Timeline Summary:</strong></h4>
<h4 id="confirming-receipt"><strong>Confirming Receipt</strong></h4>
<ul>
<li>PyData Global will make every effort to acknowledge receipt of a report <strong>within 1 hour</strong> between 8:00 and 22:30 UTC, and in 5 hours outside those times (and we’ll aim for much more quickly than that).</li>
</ul>
<h4 id="reviewing-the-report-1"><strong>Reviewing the Report</strong></h4>
<ul>
<li>PyData Global will make all efforts to review the incident <strong>within 24 hours during conference days</strong>.</li>
</ul>
<h4 id="consequences--resolution"><strong>Consequences & Resolution</strong></h4>
<ul>
<li>We aim to respond <strong>within one week</strong> to the original reporter with either a resolution or an explanation of why the situation is not yet resolved.</li>
</ul>
<h2 id="license">License</h2>
<p>This code of conduct has been adapted from numerous sources, including the <a href="https://numfocus.org/code-of-conduct">NumFOCUS Code of Conduct</a>, <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">Geek Feminism wiki, created by the Ada Initiative and other volunteers, which is under a Creative Commons Zero license</a>, the <a href="http://contributor-covenant.org/version/1/2/0/">Contributor Covenant version 1.2.0</a>, the <a href="https://github.com/bokeh/bokeh/blob/master/CODE_OF_CONDUCT.md">Bokeh Code of Conduct</a>, the <a href="https://github.com/jupyter/governance/blob/master/conduct/enforcement.md">SciPy Code of Conduct</a>, the <a href="https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#enforcement-manual">Carpentries Code of Conduct</a>, and the <a href="https://neurips.cc/public/CodeOfConduct">NeurIPS Code of Conduct</a>.</p>
<p><strong>PyData Global Code of Conduct is licensed under a <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 Unported License.</a></strong></p>
</div>
</section>
</article>
<!-- Footer -->
<footer id="footer">
<ul class="icons">
<li><a href="https://twitter.com/PyData" class="icon fa-twitter" target="_blank"><span class="label">Twitter</span></a></li>
<li><a href="https://github.com/PyDataGlobal" class="icon fa-github" target="_blank"><span class="label">GitHub</span></a></li>
</ul>
<ul class="copyright">
<li>© PyData Global 2020</li>
<li>Design: <a href="http://html5up.net" target="_blank">HTML5 UP</a>.</li>
<li>Stock Images: <a href="https://unsplash.com/" target="_blank">Unsplash</a>.</li>
<li>Jekyll integration: <a href="http://andrewbanchi.ch" target="_blank">Andrew Banchich</a>.</li>
</ul>
</footer>
</div>
<script src="https://global.pydata.org/assets/js/jquery.scrollex.min.js"></script>
<script src="https://global.pydata.org/assets/js/jquery.scrolly.min.js"></script>
<script src="https://global.pydata.org/assets/js/skel.min.js"></script>
<script src="https://global.pydata.org/assets/js/util.js"></script>
<!--[if lte IE 8]><script src="https://global.pydata.org/assets/js/ie/respond.min.js"></script><![endif]-->
<script src="https://global.pydata.org/assets/js/main.js"></script>
<script src="https://global.pydata.org/assets/js/schedule-main.js"></script>
<script src="https://global.pydata.org/assets/js/schedule-util.js"></script>
</body>
</html>