You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: community/code-of-conduct/enforcement/index.html
+116-41
Original file line number
Diff line number
Diff line change
@@ -323,6 +323,8 @@ <h4 class="b-header">On this page</h4>
323
323
324
324
<li><aclass="link" href="#the-code-of-conduct-committee"><iclass="icon circle-filled"></i>The Code of Conduct Committee</a></li>
325
325
326
+
<li><aclass="link" href="#current-code-of-conduct-committee"><iclass="icon circle-filled"></i>Current Code of Conduct Committee</a></li>
327
+
326
328
<li><aclass="link" href="#how-the-committee-will-respond-to-reports"><iclass="icon circle-filled"></i>How the committee will respond to reports</a></li>
@@ -360,59 +358,136 @@ <h4 class="b-header">On this page</h4>
360
358
</div>
361
359
</div>
362
360
<divclass="column content is-three-quarters">
363
-
<h2id="codes-of-conduct">Codes of Conduct</h2><p>This document provides incident reporting guidelines and an enforcement manual for the following codes of conduct used by Creative Commons:</p>
361
+
<h2id="codes-of-conduct">Codes of Conduct</h2><p>This document provides incident reporting guidelines and an enforcement manual
362
+
for the following codes of conduct used by Creative Commons:</p>
364
363
<ul>
365
364
<li><ahref="/community/code-of-conduct/">CC Open Source Code of Conduct</a></li>
366
365
<li><ahref="https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct">Slack/Code of Conduct</a></li>
367
366
</ul>
368
-
<h2id="reporting-guidelines">Reporting Guidelines</h2><p>If you believe someone is violating the code of conduct, we ask that you report it to Creative Commons by emailing
369
-
<strong><ahref="mailto:conduct@creativecommons.org">conduct@creativecommons.org</a></strong>. <strong>All reports will be kept confidential.</strong> In some cases we may determine that a public statement will need to be made, which the committee may make in its discretion. The identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.</p>
370
-
<p><strong>If you believe anyone is in physical danger, please notify appropriate emergency personnel first.</strong> If you are unsure what proper authorities are appropriate, please include this in your report and we will attempt to notify them.</p>
371
-
<p>If you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct, we still encourage you to report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. Knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.</p>
367
+
<h2id="reporting-guidelines">Reporting Guidelines</h2><p>If you believe someone is violating the code of conduct, we ask that you report
368
+
it to Creative Commons by emailing
369
+
<strong><ahref="mailto:conduct@creativecommons.org">conduct@creativecommons.org</a></strong>. <strong>All reports will be kept
370
+
confidential.</strong> In some cases we may determine that a public statement will
371
+
need to be made, which the committee may make in its discretion. The identities
372
+
of all victims and reporters will remain confidential unless those individuals
373
+
instruct us otherwise.</p>
374
+
<p><strong>If you believe anyone is in physical danger, please notify appropriate
375
+
emergency personnel first.</strong> If you are unsure what proper authorities are
376
+
appropriate, please include this in your report and we will attempt to notify
377
+
them.</p>
378
+
<p>If you are unsure whether the incident is a violation, or whether the space
379
+
where it happened is covered by this Code of Conduct, we still encourage you to
380
+
report it. We would much rather have a few extra reports where we decide to
381
+
take no action, rather than miss a report of an actual violation. We do not
382
+
look negatively on you if we find the incident is not a violation. Knowing
383
+
about incidents that are not violations, or happen outside our spaces, can also
384
+
help us to improve the Code of Conduct or the processes surrounding it.</p>
372
385
<p>In your report please include:</p>
373
386
<ul>
374
387
<li>Your contact info (so we can get in touch with you if we need to follow up)</li>
375
-
<li>Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.</li>
388
+
<li>Names (real, nicknames, or pseudonyms) of any individuals involved. If there
389
+
were other witnesses besides you, please try to include them as well.</li>
376
390
<li>When and where the incident occurred. Please be as specific as possible.</li>
377
-
<li>Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a Slack message) please include a link.</li>
391
+
<li>Your account of what occurred. If there is a publicly available record (e.g.
392
+
a mailing list archive or a Slack message) please include a link.</li>
378
393
<li>Any extra context for the incident.</li>
379
394
<li>If you believe this incident is ongoing.</li>
380
395
<li>Any other information the committee should have.</li>
381
396
</ul>
382
-
<h3id="conflicts-of-interest">Conflicts of Interest</h3><p>In the event of any conflict of interest a committee member must immediately notify the other members, and recuse themselves if the other committee members believe a conflict exists. If a report concerns a possible violation by a current committee member, this member must be excluded from the response process. For these cases, anyone can make a report directly to the <strong>CC Legal team at <ahref="mailto:legal@creativecommons.org">legal@creativecommons.org</a></strong> instead of through the regular process, above.</p>
383
-
<h2id="enforcement-manual">Enforcement Manual</h2><p>This manual mainly covers reports of code of conduct violations from community members. If an administrator of a forum notices ongoing or dangerous behavior that violates the code of conduct (such as spam), they may act unilaterally as described in the <strong>Acting Unilaterally</strong> section below.</p>
384
-
<h3id="the-code-of-conduct-committee">The Code of Conduct Committee</h3><p>All responses to reports of conduct violations will be managed by a Code of Conduct Committee ("the committee"), which will be comprised of three members of Creative Commons staff. The Code of Conduct Committee will serve in the role of “project maintainers” as described in the Contributor Covenant.</p>
385
-
<h3id="how-the-committee-will-respond-to-reports">How the committee will respond to reports</h3><p>When a report is sent to the committee they will reply promptly, and within no more than 2 Creative Commons business days.</p>
386
-
<p>See the reporting guidelines above for details of what reports should contain. If a report doesn't contain enough information, the committee will obtain all relevant data before acting.</p>
387
-
<p>The committee will then review the incident and determine, to the best of their ability:</p>
397
+
<h3id="conflicts-of-interest">Conflicts of Interest</h3><p>In the event of any conflict of interest a committee member must immediately
398
+
notify the other members, and recuse themselves if the other committee members
399
+
believe a conflict exists. If a report concerns a possible violation by a
400
+
current committee member, this member must be excluded from the response
401
+
process. For these cases, anyone can make a report directly to the <strong>CC Legal
402
+
team at <ahref="mailto:legal@creativecommons.org">legal@creativecommons.org</a></strong> instead
403
+
of through the regular process, above.</p>
404
+
<h2id="enforcement-manual">Enforcement Manual</h2><p>This manual mainly covers reports of code of conduct violations from community
405
+
members. If an administrator of a forum notices ongoing or dangerous behavior
406
+
that violates the code of conduct (such as spam), they may act unilaterally as
407
+
described in the <strong>Acting Unilaterally</strong> section below.</p>
408
+
<h3id="the-code-of-conduct-committee">The Code of Conduct Committee</h3><p>All responses to reports of conduct violations will be managed by a Code of
409
+
Conduct Committee ("the committee"), which will be comprised of three members
410
+
of Creative Commons staff. The Code of Conduct Committee will serve in the role
411
+
of "project maintainers" as described in the Contributor Covenant.</p>
412
+
<h3id="current-code-of-conduct-committee">Current Code of Conduct Committee</h3><ul>
<h3id="how-the-committee-will-respond-to-reports">How the committee will respond to reports</h3><p>When a report is sent to the committee they will reply promptly, and within no
418
+
more than 2 Creative Commons business days.</p>
419
+
<p>See the reporting guidelines above for details of what reports should contain.
420
+
If a report doesn't contain enough information, the committee will obtain all
421
+
relevant data before acting.</p>
422
+
<p>The committee will then review the incident and determine, to the best of their
423
+
ability:</p>
388
424
<ul>
389
425
<li>what happened</li>
390
426
<li>whether this event constitutes a code of conduct violation</li>
391
427
<li>who, if anyone, acted in contravention of the policy</li>
392
-
<li>whether this is an ongoing situation, and if there is a threat to anyone's physical safety</li>
428
+
<li>whether this is an ongoing situation, and if there is a threat to anyone's
429
+
physical safety</li>
393
430
</ul>
394
-
<p>The committee 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 committee will respond to the reporter(s) with an update and projected timeline for resolution.</p>
395
-
<h3id="acting-unilaterally">Acting Unilaterally</h3><p>Not every situation acted upon by the Code of Conduct Committee will be the result of a report from the community. In some cases, a Code of Conduct Committee member will witness a violation themselves. If the act is ongoing (such as someone engaging in harassment in an IRC channel or spamming a Slack channel), or involves a threat to anyone's safety (e.g. threats of violence), any committee 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 committee, including bans and blocks.</p>
396
-
<p>If the incident involves physical danger, any member of the committee may -- and should -- act unilaterally to protect safety. This can include contacting appropriate emergency personnel first or speaking on behalf of Creative Commons.</p>
397
-
<p>In situations where an individual committee member acts unilaterally, they must report their actions to the committee for review within 1 business day.</p>
398
-
<h3id="resolutions">Resolutions</h3><p>The committee should strive to agree on a resolution by consensus (i.e. no one on the committee chooses to veto the course of action). As soon as the committee determines it is unable to reach consensus or it has been deadlocked for over 2 business days after acknowledging receipt of the issue, the committee will turn the matter over to the CC legal team for resolution.</p>
431
+
<p>The committee should aim to have a resolution agreed upon within one week. In
432
+
the event that a resolution can't be determined in that time, the committee
433
+
will respond to the reporter(s) with an update and projected timeline for
434
+
resolution.</p>
435
+
<h3id="acting-unilaterally">Acting Unilaterally</h3><p>Not every situation acted upon by the Code of Conduct Committee will be the
436
+
result of a report from the community. In some cases, a Code of Conduct
437
+
Committee member will witness a violation themselves. If the act is ongoing
438
+
(such as someone engaging in harassment in an IRC channel or spamming a Slack
439
+
channel), or involves a threat to anyone's safety (e.g. threats of violence),
440
+
any committee member may act immediately (before reaching consensus) to end the
441
+
situation. In ongoing situations, any member may at their discretion employ any
442
+
of the tools available to the committee, including bans and blocks.</p>
443
+
<p>If the incident involves physical danger, any member of the committee may --
444
+
and should -- act unilaterally to protect safety. This can include contacting
445
+
appropriate emergency personnel first or speaking on behalf of Creative
446
+
Commons.</p>
447
+
<p>In situations where an individual committee member acts unilaterally, they must
448
+
report their actions to the committee for review within 1 business day.</p>
449
+
<h3id="resolutions">Resolutions</h3><p>The committee should strive to agree on a resolution by consensus (i.e. no one
450
+
on the committee chooses to veto the course of action). As soon as the
451
+
committee determines it is unable to reach consensus or it has been deadlocked
452
+
for over 2 business days after acknowledging receipt of the issue, the
453
+
committee will turn the matter over to the CC legal team for resolution.</p>
399
454
<p>Possible responses may include:</p>
400
455
<ul>
401
-
<li>Taking no further action (if the committee determines no violation occurred).</li>
402
-
<li>A private reprimand from the committee to the individual(s) involved. In this case, a committee member will deliver that reprimand to the individual(s) directly through appropriate means, cc'ing the committee.</li>
403
-
<li>A public reprimand. In this case, a committee member will attempt to deliver that reprimand in the same venue that the violation occurred (i.e. in Slack for an Slack violation; email for an email violation, etc.). The committee may choose to publish this message elsewhere for posterity.</li>
404
-
<li>A temporary or permanent ban from some or all Creative Commons spaces (mailing lists, Slack, etc.). The committee will maintain records of all such bans so that they may be reviewed in the future, extended to new Creative Commons fora, or otherwise maintained.</li>
456
+
<li>Taking no further action (if the committee determines no violation
457
+
occurred).</li>
458
+
<li>A private reprimand from the committee to the individual(s) involved. In this
459
+
case, a committee member will deliver that reprimand to the individual(s)
460
+
directly through appropriate means, cc'ing the committee.</li>
461
+
<li>A public reprimand. In this case, a committee member will attempt to deliver
462
+
that reprimand in the same venue that the violation occurred (i.e. in Slack
463
+
for an Slack violation; email for an email violation, etc.). The committee may
464
+
choose to publish this message elsewhere for posterity.</li>
465
+
<li>A temporary or permanent ban from some or all Creative Commons spaces
466
+
(mailing lists, Slack, etc.). The committee will maintain records of all such
467
+
bans so that they may be reviewed in the future, extended to new Creative
468
+
Commons fora, or otherwise maintained.</li>
405
469
</ul>
406
-
<p>Once a resolution is agreed upon, but before it is enacted, the committee will contact the original reporter and any other affected parties and explain the proposed resolution. The committee will ask if this resolution is acceptable, and must note feedback for the record. However, the committee is not required to act on this feedback.</p>
407
-
<h3id="reconsideration">Reconsideration</h3><p>Any of the parties directly involved or affected can request reconsideration of the committee’s decision. To make such a request, contact the <strong>CC Legal team at <ahref="mailto:legal@creativecommons.org">legal@creativecommons.org</a></strong> with your request and reason and they will review the case.</p>
408
-
<h2id="current-code-of-conduct-committee">Current Code of Conduct Committee</h2><ul>
<p>Once a resolution is agreed upon, but before it is enacted, the committee will
471
+
contact the original reporter and any other affected parties and explain the
472
+
proposed resolution. The committee will ask if this resolution is acceptable,
473
+
and must note feedback for the record. However, the committee is not required
474
+
to act on this feedback.</p>
475
+
<h3id="reconsideration">Reconsideration</h3><p>Any of the parties directly involved or affected can request reconsideration of
476
+
the committee’s decision. To make such a request, contact the <strong>CC Legal team
477
+
at <ahref="mailto:legal@creativecommons.org">legal@creativecommons.org</a></strong> with your
478
+
request and reason and they will review the case.</p>
479
+
<h2id="policy-revision">Policy Revision</h2><p>This policy may be revised and updated by Creative Commons from time to time.
480
+
You should not participate in our digital communities unless you agree with and
481
+
comply with the current policy.</p>
482
+
<h3id="last-revised">Last Revised</h3><ul>
483
+
<li>2019-03-06</li>
484
+
<li>For a detailed list of changes, see <ahref="https://github.com/creativecommons/creativecommons.github.io-source/commits/master/content/community/code-of-conduct/enforcement/contents.lr">History for
<h2id="policy-revision">Policy Revision</h2><p>This policy may be revised and updated by Creative Commons from time to time. You should not participate in our digital communities unless you agree with and comply with the current policy.</p>
<h2id="attribution">Attribution</h2><p>This document is adapted from the Django project's Code of Conduct <ahref="https://www.djangoproject.com/conduct/enforcement-manual/">enforcement manual</a> and <ahref="https://www.djangoproject.com/conduct/reporting/">reporting guidelines</a>, licensed under <ahref="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>.</p>
488
+
<h2id="attribution">Attribution</h2><p>This document is adapted from the Django project's Code of Conduct <ahref="https://www.djangoproject.com/conduct/enforcement-manual/">enforcement
489
+
manual</a> and <ahref="https://www.djangoproject.com/conduct/reporting/">reporting guidelines</a>, licensed
490
+
under <ahref="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>.</p>
0 commit comments