global-conference-2023/coc-enforcement.html at main · pyladies/global-conference-2023 · GitHub

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
<!DOCTYPE html>
<html lang="en">
    <head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <meta property="og:title" content="PyLadiesCon 2023 - Code of Conduct Enforcement Procedure">
    <meta property="og:description" content="Code of Conduct Enforcement Procedure.">
    <meta property="og:type" content="article">
    <meta property="og:url" content="https://conference.pyladies.com/coc-enforcement.html">
    <meta property="og:image" content="https://conference.pyladies.com/img/icon.png">
    <meta property="og:image:alt" content="PyLadiesCon logo">
    <link rel="shortcut icon" href="/img/favicon.ico" />
    <title>PyLadiesCon 2023 - Code of Conduct Enforcement Procedure</title>

    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Inter&family=Orbitron:wght@500&family=Press+Start+2P&display=swap" rel="stylesheet">

    <link rel="stylesheet" href="css/vars.css">
    <link rel="stylesheet" href="css/bootstrap.min.css">
    <link rel="stylesheet" href="css/style.css">
    <script crossorigin="anonymous" src="https://kit.fontawesome.com/6cf87c29c5.js"></script>

  </head>
  <body>

  <header class="site-header sticky-top py-1">
  <nav class="navbar navbar-expand-lg navbar-light d-flex flex-row justify-content-around align-items-center">
    <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
      <img class="hamburger-logo" src="img/bar-chart-2.png"/>
    </button>

    <div class="collapse navbar-collapse" id="navbarSupportedContent">
      <ul class="navbar-nav mx-auto">
        <a href="index.html" aria-label="PyLadiesCon">
          <img class="menu-logo" src="img/icon.png"/>
        </a>
        <li class="nav-item dropdown px-4">
          <a class="nav-link dropdown-toggle menu-font" data-toggle="dropdown" href="index.html" role="button" aria-haspopup="true" aria-expanded="false">About</a>
          <div class="dropdown-menu">
            <a class="dropdown-item" href="about.html#the-event">The Event</a>
            <a class="dropdown-item" href="about.html#the-organizers">The Organizers</a>
            <a class="dropdown-item" href="about.html#the-psf">The PSF</a>
            <a class="dropdown-item" href="about.html#coc">Code of Conduct</a>
          </div>
        </li>
        <li class="nav-item px-4">
          <a class="nav-link dropdown-toggle menu-font" data-toggle="dropdown" href="index.html" role="button" aria-haspopup="true" aria-expanded="false">Speakers</a>
          <div class="dropdown-menu">
            <a class="dropdown-item" href="speakers.html#keynotes">The Keynotes</a>
            <a class="dropdown-item" href="speakers.html#speakers">The Speakers</a>
          </div>
        </li>
        <li class="nav-item px-4">
          <a class="py-2 d-flex d-md-inline-block menu-font" href="schedule.html">Schedule</a>
        </li>
        <li class="nav-item px-4">
          <a class="py-2 d-flex d-md-inline-block menu-font" href="sponsors.html">Sponsor</a>
        </li>
        <li class="nav-item px-4">
          <a class="py-2 d-flex d-inline-block menu-font" href="index.html#contact">Contact</a>
        </li>
        <div class="text-end px-4">
            <a class="btn btn-outline-secondary btn-pink text-white" href="https://events.hubilo.com/pyladiescon2023/register">Register</a>
        </div>
      </ul>
    </div>
  </nav>
</header>

<main>

    <!-- page cover -->
    <div class="position-relative overflow-hidden p-1 p-md-3 m-md-1 text-center bg-white">
      <div class="d-flex w-75 my-md-3 mx-auto align-items-center">
        <div class="col-10 col-md-10 p-lg-1 mx-auto mt-auto">
          <h4 class="special-font gradient title-size-2 text-start">Code of Conduct Enforcement Procedures</h4>
        </div>
        <div class="col-2 col-md-2 d-none d-lg-block">
          <img class="img-fluid" src="img/sponsors-icon-2.png" />
        </div>
      </div>
    </div>

    <!-- about -->

  <div class="d-md-flex flex-md-equal w-100 mt-md-3 ps-md-3">
    <div class="bg-white pt-3 pt-md-5 overflow-hidden">
      <img class="w-100" src="img/about-photo-1.png" alt="Video call with 6 female participants with
      a diversity of hair styles and colours, skin tones and are all smiling."/>
    </div>
    <div class="bg-white pt-3 pt-md-5 overflow-hidden">
      <img class="w-100" src="img/about-photo-2.png" alt="Three recially diverse women sitting on a sofa each with a
      laptop on their lap and smiling." />
    </div>
  </div>

  <div class="d-md-flex flex-md-equal w-100 ps-md-3">
    <div class="bg-white mr-md-3 pt-3 px-3 pt-md-5 px-md-5 text-left text-white overflow-hidden">
      <div class="my-3 py-3 text-black" id="the-event">


        <p class="lead">
          This document summarizes the procedures the PyLadies Con CoC team uses to enforce the Code of Conduct.
        </p>

        <h2 class="display-8">Summary of processes</h2>
        <p>
          When the work group receives a report of a possible Code of Conduct violation, it will:
          <ol>
            <li>Acknowledge the receipt of the report.</li>
            <li>Evaluate conflicts of interest.</li>
            <li>Call a meeting of Code of Conduct responders who do not have a conflict of interest.</li>
            <li>Evaluate the reported incident.</li>
            <li>Propose a behavioral modification plan.</li>
            <li>Propose consequences for the reported behavior.</li>
            <li>Vote on behavioral modification plan and consequences for the reported person.</li>
            <li>Contact online community administrators/moderators to approve the behavioral modification plan and consequences.</li>
            <li>Follow up with the reported person.</li>
            <li>Decide further responses.</li>
            <li>Follow up with the reporter.</li>
          </ol>
        </p>

        <h2 class="display-8">Acknowledge the report</h2>
        <p>
        We will have members of the Code of Conduct team online at all times during the conference.
        Reporters should receive an emailed acknowledgment of the receipt of their report within 2 hours.
        </p>

        <h2 class="display-8">Conflict of interest policy</h2>

        <p>
          Examples of conflicts of interest include:
          <ul>
            <li>The reporter or reported person is your manager</li>
            <li>You have a romantic or platonic relationship with either the reporter or the reported person. It’s fine to participate if they are an acquaintance.</li>
            <li>The reporter or reported person is your metamour. (This is a term used in the poly community;
              <a href="https://www.urbandictionary.com/define.php?term=Metamour">see the short definition for metamour</a>,
              <a href="https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/">and a longer description</a>).</li>
            <li>The reporter or reported person is your family member</li>
            <li>The reporter or reported person is your direct client</li>
            <li>The reporter or reported person is someone you work closely with. This could be someone on your team or someone who works on the same project as you.</li>
            <li>The reporter or reported person is a maintainer who regularly reviews your contributions</li>
          </ul>
        </p>
        <p>
          Committee members do not need to state why they have a conflict of interest, only that one exists.
          Other work group members should not ask why the person has a conflict of interest.
        </p>
        <p>
          Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recuse themselves from voting on a response to the report.
        </p>

        <h2 class="display-8">Evaluating a report</h2>

        <h3 class="display-8">Jurisdiction</h3>
        <ul>
          <li>Is this a Code of Conduct violation? Is this behavior on our list of inappropriate behavior? Is it borderline inappropriate behavior? Does it violate our community norms?</li>
          <li>Did this occur in a space that is within our Code of Conduct’s scope? If the incident occurred outside the community, but a community member’s mental health or physical safety may be
            negatively impacted if no action is taken, the incident may be in scope. Private conversations in community spaces are also in scope.</li>
        </ul>

        <h3 class="display-8">Impact</h3>
        <ul>
          <li>Did this incident occur in a private conversation or in a public space? Incidents that all community members can see will have more negative impact.</li>
          <li>Does this behavior negatively impact a marginalized group in our community? Is the reporter a person from a marginalized group in our community? How is the reporter being negatively impacted by the reported person’s behavior? Are members of the marginalized group likely to disengage with the community if no action was taken on this report?</li>
          <li>Does this incident involve a community leader? Community members often look up to community leaders to set the standard of acceptable behavior.</li>
        </ul>

        <h3 class="display-8">Risk</h3>
        <ul>
          <li>Does this incident include sexual harrasment?</li>
          <li>Does this pose a safety risk? Does the behavior put a person’s physical safety at risk? Will this incident severely negatively impact someone’s mental health?</li>
          <li>Is there a risk of this behavior being repeated? Does the reported person understand why their behavior was inappropriate? Is there an established pattern of behavior from past reports?</li>
        </ul>

        <p>Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact.</p>

        <h2 class="display-8">Propose a behavioral modification plan</h2>

        <p>
          The CoC team will determine a concrete behavioral modification plan that ensures the inappropriate behavior is not repeated.
          The CoC team will also discuss what actions may need to be taken if the reported person does not agree to the behavioral modification plan.
        </p>

        <p>
          What follows are examples of possible behavioral modification plans for incidents that occur in online spaces under the scope of this Code of Conduct.
          This behavioral modification list is not inclusive, and the event staff reserves the right to take any action it deems necessary.
          <ul>
            <li>Requiring that the reported person not use specific language</li>
            <li>Requiring that the reported person not join in on specific types of discussions</li>
            <li>Requiring that the reported person not send private messages to a community member</li>
            <li>Requiring that the reported person not join specific communication channels</li>
            <li>Removing the reported person from administrator or moderator rights to community infrastructure</li>
            <li>Removing a volunteer from their duties and responsibilities</li>
            <li>Removing a person from leadership of relevant organizations</li>
            <li>Removing a person from membership of relevant organizations</li>
          </ul>
        </p>

        <h2 class="display-8">Propose consequences</h2>
        <p>
          What follows are examples of possible consequences of an incident report.
          This consequences list is not inclusive, and the event staff reserves the right to take any action it deems necessary.
        </p>

        <p>
          Possible private responses to an incident include:
          <ul>
            <li>Nothing, if the behavior was determined to not be a Code of Conduct violation</li>
            <li>A verbal or emailed warning</li>
            <li>A final warning</li>
            <li>Temporarily removing the reported person from the online community</li>
            <li>Permanently removing the reported person from the online community</li>
            <li>Publishing an account of the incident</li>
            <li>Escalating the incident to the PSF Code of Conduct Working Group</li>
          </ul>
        </p>

        <h2 class="display-8">Follow up with the reported person</h2>
        <p>
          The CoC team will draft a response to the reported person.
          The email should contain:

          <ul>
            <li>A description of the person’s behavior in neutral language</li>
            <li>The negative impact of that behavior</li>
            <li>A concrete behavioral modification plan</li>
            <li>Any consequences of their behavior</li>
          </ul>
        </p>

        <p>
          The CoC team should not state who reported this incident.
          They should attempt to anonymize any identifying information from the report.
          The reported person should be discouraged from contacting the reporter to discuss the report.
          If they wish to apologize to the reporter, the CoC team can accept the apology on behalf of the reporter.
        </p>

        <h3 class="display-8">Decide further responses</h3>
        <p>
          If the reported person provides additional context, the CoC team may need to re-evaluate the behavioral modification plan and consequences.
        </p>

        <h2 class="display-8">Follow up with the reporter</h2>

        <p>
          A person who makes a report should receive a follow-up email stating what action was taken in response to the report.
          If the CoC team decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation.
          Reports that are not made in good faith (such as “reverse sexism” or “reverse racism”) may receive no response.
        </p>

        <p>
          The follow-up email should be sent no later than one week after the receipt of the report.
          If deliberation or follow up with the reported person takes longer than one week, the CoC group should send a status email to the reporter.
        </p>

        <!-- License and attribution -->
        <h2>License</h2>

        <p>
          This Code of Conduct is licensed under the <a href="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License.</a>
        </p>

        <h2>Attribution</h2>

        <p>
          <ul>
            <li>This Code of Conduct is based on the <a href="https://us.pycon.org/2023/about/code-of-conduct/">PyCon US Code of Conduct</a>
            which was forked from the example policy from the <a href="https://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">Geek Feminism wiki,
            created by the Ada Initiative and other volunteers</a>, which is under a <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons Zero license.</a></li>
            <li>Audrey Eschright of <a href="http://safetyfirstpdx.org/">Safety First PDX</a> provided the impact vs risk assessment framework,
              which is licensed under a <a href="http://creativecommons.org/licenses/by-sa/3.0/"> Creative Commons Attribution Share-Alike 3.0 Unported License</a>
              by Audrey Eschright of <a href="http://safetyfirstpdx.org/">Safety First PDX</a></li>
            <li>
              <a href="https://github.com/sagesharp/code-of-conduct-template/">Code of Conduct template</a> was created by
              <a href="https://otter.technology/code-of-conduct-training">Otter Tech</a> and is licensed under a
              <a href="http://creativecommons.org/licenses/by/3.0/"> Commons Attribution 3.0 Unported License</a>.
            </li>
          </ul>
        </p>

      </div>
    </div>

    </div>
  </div>

</main>

<footer class="container py-5">
  <div class="row align-items-center justify-content-lg-between">
    <div class="col-md-7 col-lg-auto text-center text-md-start">
      <img src="img/logo_footer.png" />
      <small class="d-block mb-3 text-muted">
        2007 - 2023 PyLadies. All Rights Reserved.<br>
        Disclaimer - PyLadies and the PyLadies logo are trademarks of the Python Software Foundation
      </small>
    </div>
    <div class="col-md-5 col-lg-auto text-center text-md-start">
      <a class="arrow-link" href="https://pyladies.com/">PyLadies</a>
      <a class="arrow-link" href="https://www.python.org/psf-landing/">PSF</a>
      <a class="arrow-link" href="https://python.org">Python</a>
      <div class="social pt-3">
        <a href="mailto:pyladiescon@pyladies.com"><i class="fas fa-envelope fa-2x px-2"></i></a>
        <a href="https://fosstodon.org/@pyladiescon" rel="me"><i class="fab fa-mastodon fa-2x px-2"></i></a>
        <a href="https://twitter.com/pyladiescon"><i class="fab fa-twitter fa-2x px-2"></i></a>
        <a href="https://instagram.com/pyladiescon"><i class="fab fa-instagram fa-2x px-2"></i></a>
        <a href="https://www.linkedin.com/company/pyladiescon"><i class="fab fa-linkedin fa-2x px-2"></i></a>
      </div>
    </div>
    <div class="row justify-content-center">
      <div class="col-7 col-sm-6 col-lg-3">
        <a href="https://www.awesomic.com"><img class="img-fluid" src="img/awesomic-white.gif"/></a>
      </div>
    </div>
  </div>
</footer>

<script src="js/jquery-3.2.1.slim.min.js"></script>
<script src="js/popper.min.js"></script>
<script src="js/bootstrap.min.js"></script>

</body>
</html>