Skip to content

Commit d2dca48

Browse files
cmaureircmaureir
authored
Add missing reporting and enforcing pages (#168)
1 parent 391dc04 commit d2dca48

File tree

3 files changed

+338
-10
lines changed

3 files changed

+338
-10
lines changed

‎content/about/_index.md

+9-10
Original file line numberDiff line numberDiff line change
@@ -197,10 +197,10 @@ event are required to conform to the following Code of Conduct as set forth by
197197
the Python Software Foundation. Organizers will enforce this code throughout
198198
the event.
199199

200-
The Python community is made up of members from around the globe with a diverse
201-
set of skills, personalities, and experiences. It is through these differences
202-
that our community experiences great successes and continued growth. When you're
203-
working with members of the community, this Code of Conduct will help steer your
200+
The Python community is made up of members from around the globe with a diverse
201+
set of skills, personalities, and experiences. It is through these differences
202+
that our community experiences great successes and continued growth. When you're
203+
working with members of the community, this Code of Conduct will help steer your
204204
interactions and keep Python a positive, successful, and growing community.
205205

206206

@@ -290,7 +290,7 @@ including warning the offender or expulsion from the community and community
290290
events with no refund of event tickets.
291291

292292
The full list of consequences for inappropriate behavior is listed in
293-
[the Enforcement Procedures](/enforcement).
293+
[the Enforcement Procedures](/coc/enforcement).
294294

295295
Thank you for helping make this a welcoming, friendly community for everyone.
296296
{{% /togglebutton-content %}}
@@ -359,14 +359,13 @@ The organizing and Code of Conduct team will be happy to assist any attendee to
359359
feel safe for the duration of the conference. We value your attendance.
360360

361361
## Procedure for handling incidents
362-
<a href="coc-reporting.html">Procedure For Reporting Code of Conduct Incidents</a>
363-
<a href="coc-enforcement.html">Enforcement procedures</a>
362+
* [Procedure For Reporting Code of Conduct Incidents](/coc/reporting)
363+
* [Enforcement procedures](/coc/enforcement)
364364

365365
## License
366366

367-
This Code of Conduct is licensed under the <a
368-
href="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons
369-
Attribution-ShareAlike 3.0 Unported License.</a>
367+
This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported
368+
License](https://creativecommons.org/licenses/by-sa/3.0/).
370369

371370
## Attribution
372371

‎content/coc/enforcement.md

+195
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,195 @@
1+
+++
2+
title = 'Code of Conduct Enforcement'
3+
draft = false
4+
layout = 2
5+
description = "PyLadies Conference (PyLadiesCon) is the second Pyladies conference held– an exciting online and FREE event dedicated to empowerment, learning, and diversity within the Python community! Date: December 6th-8th At PyLadiesCon, we're bringing the Python world right to your doorstep. Make sure to mark your calendars for the first weekend of December as we embark on a two-day journey that promises to be unforgettable."
6+
image = "/img/about-photo-1.png"
7+
imagealt = "Video call with 6 female participants with a diversity of hair styles and colours, skin tones and are all smiling."
8+
+++
9+
10+
{{< pageheadersmall
11+
"Code of Conduct Enforcement"
12+
"This document summarizes the procedures the PyLadies Con CoC team uses to enforce the Code of Conduct."
13+
"/img/about-icon-2.png"
14+
>}}
15+
16+
{{< rawhtml >}}
17+
<div class="d-md-flex flex-md-equal w-100">
18+
<div class="bg-white overflow-hidden">
19+
<img class="w-100" src="/img/about-photo-1.png" alt="Video call with 6 female participants with
20+
a diversity of hair styles and colours, skin tones and are all smiling."/>
21+
</div>
22+
<div class="bg-white overflow-hidden">
23+
<img class="w-100" src="/img/about-photo-2.png" alt="Three recially diverse women sitting on a sofa each with a
24+
laptop on their lap and smiling." />
25+
</div>
26+
</div>
27+
{{< /rawhtml >}}
28+
29+
30+
## Summary of processes
31+
32+
When the work group receives a report of a possible Code of Conduct violation, it will:
33+
34+
1. Acknowledge the receipt of the report.
35+
2. Evaluate conflicts of interest.
36+
3. Call a meeting of Code of Conduct responders who do not have a conflict of interest.
37+
4. Evaluate the reported incident.
38+
5. Propose a behavioral modification plan.
39+
6. Propose consequences for the reported behavior.
40+
7. Vote on behavioral modification plan and consequences for the reported person.
41+
8. Contact online community administrators/moderators to approve the behavioral modification plan
42+
and consequences.
43+
9. Follow up with the reported person.
44+
10. Decide further responses.
45+
11. Follow up with the reporter.
46+
47+
## Acknowledge the report
48+
49+
We will have members of the Code of Conduct team online at all times during the conference.
50+
Reporters should receive an emailed acknowledgment of the receipt of their report within 2 hours.
51+
52+
## Conflict of interest policy
53+
54+
Examples of conflicts of interest include:
55+
56+
* The reporter or reported person is your manager
57+
* You have a romantic or platonic relationship with either the reporter or the reported person. It’s
58+
fine to participate if they are an acquaintance.
59+
* The reporter or reported person is your metamour. (This is a term used in the poly community;
60+
[see the short definition for metamour](https://www.urbandictionary.com/define.php?term=Metamour),
61+
[and a longer description](https://solopoly.net/2012/09/29/whats-a-metamour-on-my-terms/)).
62+
* The reporter or reported person is your family member
63+
* The reporter or reported person is your direct client
64+
* The reporter or reported person is someone you work closely with. This could be someone on your
65+
team or someone who works on the same project as you.
66+
* The reporter or reported person is a maintainer who regularly reviews your contributions
67+
68+
Committee members do not need to state why they have a conflict of interest, only that one exists.
69+
Other work group members should not ask why the person has a conflict of interest.
70+
71+
Anyone who has a conflict of interest will remove themselves from the discussion of the incident,
72+
and recuse themselves from voting on a response to the report.
73+
74+
## Evaluating a report
75+
76+
### Jurisdiction
77+
78+
* Is this a Code of Conduct violation? Is this behavior on our list of inappropriate behavior? Is it
79+
borderline inappropriate behavior? Does it violate our community norms?
80+
* Did this occur in a space that is within our Code of Conduct’s scope? If the incident occurred
81+
outside the community, but a community member’s mental health or physical safety may be negatively
82+
impacted if no action is taken, the incident may be in scope. Private conversations in community
83+
spaces are also in scope.
84+
85+
### Impact
86+
87+
* Did this incident occur in a private conversation or in a public space? Incidents that all
88+
community members can see will have more negative impact.
89+
* Does this behavior negatively impact a marginalized group in our community? Is the reporter a
90+
person from a marginalized group in our community? How is the reporter being negatively impacted
91+
by the reported person’s behavior? Are members of the marginalized group likely to disengage with
92+
the community if no action was taken on this report?
93+
* Does this incident involve a community leader? Community members often look up to community
94+
leaders to set the standard of acceptable behavior.
95+
96+
### Risk
97+
98+
* Does this incident include sexual harrasment?
99+
* Does this pose a safety risk? Does the behavior put a person’s physical safety at risk? Will this
100+
incident severely negatively impact someone’s mental health?
101+
* Is there a risk of this behavior being repeated? Does the reported person understand why their
102+
behavior was inappropriate? Is there an established pattern of behavior from past reports?
103+
104+
Reports which involve higher risk or higher impact may face more severe consequences than reports
105+
which involve lower risk or lower impact.
106+
107+
## Propose a behavioral modification plan
108+
109+
The CoC team will determine a concrete behavioral modification plan that ensures the inappropriate
110+
behavior is not repeated.
111+
The CoC team will also discuss what actions may need to be taken if the reported person does not
112+
agree to the behavioral modification plan.
113+
114+
What follows are examples of possible behavioral modification plans for incidents that occur in
115+
online spaces under the scope of this Code of Conduct.
116+
This behavioral modification list is not inclusive, and the event staff reserves the right to take
117+
any action it deems necessary.
118+
119+
* Requiring that the reported person not use specific language
120+
* Requiring that the reported person not join in on specific types of discussions
121+
* Requiring that the reported person not send private messages to a community member
122+
* Requiring that the reported person not join specific communication channels
123+
* Removing the reported person from administrator or moderator rights to community infrastructure
124+
* Removing a volunteer from their duties and responsibilities
125+
* Removing a person from leadership of relevant organizations
126+
* Removing a person from membership of relevant organizations
127+
128+
## Propose consequences
129+
130+
What follows are examples of possible consequences of an incident report.
131+
This consequences list is not inclusive, and the event staff reserves the right to take any action
132+
it deems necessary.
133+
134+
Possible private responses to an incident include:
135+
* Nothing, if the behavior was determined to not be a Code of Conduct violation
136+
* A verbal or emailed warning
137+
* A final warning
138+
* Temporarily removing the reported person from the online community
139+
* Permanently removing the reported person from the online community
140+
* Publishing an account of the incident
141+
* Escalating the incident to the PSF Code of Conduct Working Group
142+
143+
## Follow up with the reported person
144+
145+
The CoC team will draft a response to the reported person.
146+
The email should contain:
147+
148+
* A description of the person’s behavior in neutral language
149+
* The negative impact of that behavior
150+
* A concrete behavioral modification plan
151+
* Any consequences of their behavior
152+
153+
The CoC team should not state who reported this incident.
154+
They should attempt to anonymize any identifying information from the report.
155+
The reported person should be discouraged from contacting the reporter to discuss the report.
156+
If they wish to apologize to the reporter, the CoC team can accept the apology on behalf of the
157+
reporter.
158+
159+
### Decide further responses
160+
161+
If the reported person provides additional context, the CoC team may need to re-evaluate the
162+
behavioral modification plan and consequences.
163+
164+
## Follow up with the reporter
165+
166+
A person who makes a report should receive a follow-up email stating what action was taken in
167+
response to the report.
168+
If the CoC team decided no response was needed, they should provide an email explaining why it was
169+
not a Code of Conduct violation.
170+
Reports that are not made in good faith (such as “reverse sexism” or “reverse racism”) may receive
171+
no response.
172+
173+
The follow-up email should be sent no later than one week after the receipt of the report.
174+
If deliberation or follow up with the reported person takes longer than one week, the CoC group
175+
should send a status email to the reporter.
176+
177+
## License
178+
179+
This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported
180+
License](https://conference.pyladies.com/about/#code-of-conduct).
181+
182+
## Attribution
183+
184+
* This Code of Conduct is based on the [PyCon US Code of
185+
Conduct](https://us.pycon.org/2023/about/code-of-conduct/) which was forked from the example
186+
policy from the [Geek Feminism wiki, created by the Ada Initiative and other
187+
volunteers](https://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy), which is under
188+
a [Creative Common Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
189+
* Audrey Eschright of [Safety First PDX](http://safetyfirstpdx.org/) provided the impact vs risk
190+
assessment framework, which is licensed under a [Creative Commons Attribution Share-Alike 3.0
191+
Unported License](http://creativecommons.org/licenses/by-sa/3.0/) by Audrey Eschright of [Safety
192+
First PDX](http://safetyfirstpdx.org/)
193+
* [Code of Conduct template](https://github.com/sagesharp/code-of-conduct-template/) was created by
194+
[Otter Tech](https://otter.technology/code-of-conduct-training) and is licensed under a [Commons
195+
Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/).

‎content/coc/reporting.md

+134
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
+++
2+
title = 'Code of Conduct Reporting'
3+
draft = false
4+
layout = 2
5+
description = "PyLadies Conference (PyLadiesCon) is the second Pyladies conference held– an exciting online and FREE event dedicated to empowerment, learning, and diversity within the Python community! Date: December 6th-8th At PyLadiesCon, we're bringing the Python world right to your doorstep. Make sure to mark your calendars for the first weekend of December as we embark on a two-day journey that promises to be unforgettable."
6+
image = "/img/about-photo-1.png"
7+
imagealt = "Video call with 6 female participants with a diversity of hair styles and colours, skin tones and are all smiling."
8+
+++
9+
10+
{{< pageheadersmall
11+
"Code of Conduct Reporting"
12+
"Steps for doing a proper report of an event that happened in the conference"
13+
"/img/about-icon-2.png"
14+
>}}
15+
16+
{{< rawhtml >}}
17+
<div class="d-md-flex flex-md-equal w-100">
18+
<div class="bg-white overflow-hidden">
19+
<img class="w-100" src="/img/about-photo-1.png" alt="Video call with 6 female participants with
20+
a diversity of hair styles and colours, skin tones and are all smiling."/>
21+
</div>
22+
<div class="bg-white overflow-hidden">
23+
<img class="w-100" src="/img/about-photo-2.png" alt="Three recially diverse women sitting on a sofa each with a
24+
laptop on their lap and smiling." />
25+
</div>
26+
</div>
27+
{{< /rawhtml >}}
28+
29+
30+
If you believe someone has violated the <a href="/about/#code-of-conduct">Code of Conduct</a>, we encourage
31+
you to report it. If you are unsure whether the incident is a violation, or whether the space where
32+
it happened is covered by the Code of Conduct, we encourage you to still report it. We are fine with
33+
receiving reports where we decide to take no action for the sake of creating a safer space.
34+
35+
## General reporting procedure
36+
37+
The best way to contact the Code of Conduct team is by email at
38+
[[email protected]](mailto:[email protected]) which is monitored by the
39+
Code of Conduct team (Cecilia, Debbie, Jessica, Maaya, and Tania).
40+
41+
In case of a conflict of interest, you can individually contact:
42+
* Tania Allard ([[email protected]](mailto:[email protected]))
43+
* Mariatta Wijaya ([[email protected]](mailto:[email protected]))
44+
45+
## Report Data
46+
47+
When reporting an incident, please include as much information as possible, including:
48+
49+
* Your contact info (so we can get in touch with you if we need to follow up)
50+
* Date and time of the incident
51+
* Location of incident
52+
* Whether the incident is ongoing
53+
* Description of the incident
54+
* Identifying information of the reported person: name, screen name (Slack, Hubilo, etc.), physical
55+
appearance, height, clothing, voice accent, identifying information such as company name, or other
56+
information displayed on the conference platform.
57+
* Additional circumstances surrounding the incident
58+
* Other people involved in or witnesses to the incident and their contact information or description
59+
60+
## Confidentiality
61+
62+
**All reports will be kept confidential.**
63+
When we discuss incidents with people who are reported, we will anonymize details as much as we can
64+
to protect reporter privacy.
65+
66+
However, some incidents happen in one-on-one interactions, and even if the details are anonymized,
67+
the reported person may be able to guess who made the report.
68+
If you have concerns about retaliation or your personal safety, please note those in your report.
69+
We still encourage you to report, so that we can support you while keeping our conference attendees
70+
safe.
71+
In some cases, we can compile several anonymized reports into a pattern of behavior, and take action
72+
on that pattern.
73+
74+
In some cases, we may determine that a public statement will need to be made.
75+
If that's the case, the identities of all individuals involved and reporters will remain
76+
confidential unless those individuals instruct us otherwise.
77+
78+
## Report handling procedure
79+
80+
When you make a report to an incident responder, they will gather information about the incident
81+
according to the [Procedure For Incident Reponse](/coc/enforcement).
82+
83+
After an incident responder takes the report, they will immediately consult with the CoC team,
84+
unless there is a conflict of interest, in which case any non-interested parties will be contacted.
85+
86+
If the incident is ongoing and needs to be immediately addressed, any lead incident responder may
87+
take appropriate action to ensure the safety of everyone involved.
88+
If the situation requires it, this may take the form of a referral to an appropriate non-PyLadiesCon
89+
agency, including the local police.
90+
The CoC team is not equipped to handle emergency situations.
91+
92+
If the incident is less urgent, the report will be discussed by the CoC team, who will meet to
93+
determine an appropriate response.
94+
Examples of possible incident responses are outlined in the [Procedure For Incident
95+
Response](/coc/enforcement).
96+
97+
Before the conference, the CoC team review the outlined procedures.
98+
After the conference, all CoC team members will attend a debriefing session with the CoC team chair
99+
to discuss all incidents and determine any necessary follow-up actions.
100+
101+
## Following up with reporters
102+
103+
Within one week of an incident report, a member of the CoC team
104+
will follow up with the person who made the report and provided their contact information. The
105+
follow-up may include:
106+
107+
* An acknowledgment that the Code of Conduct team discussed the situation
108+
* Whether or not the report was determined to be a violation of the Code of Conduct
109+
* What actions (if any) were taken to correct the reported behavior
110+
111+
In some cases, the CoC team members may need to ask additional questions about the incident in order
112+
to identify the reported person.
113+
114+
## Conflicts of interest
115+
116+
If an incident responder has a conflict of interest for a report, they will recuse themselves from
117+
the discussion and handling of the incident.
118+
The incident documentation will not be available to them, and they will excuse themselves from any
119+
conversations involving handling the incident.
120+
121+
Should more than two members of the CoC lead responders need to recuse themselves, another
122+
PyLadiesCon organizer will step in as a temporary lead incident responder.
123+
124+
## License
125+
126+
This Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported
127+
License](https://conference.pyladies.com/about/#code-of-conduct).
128+
129+
## Attribution
130+
131+
* This Code of Conduct is based on the [PyCon US Code of Conduct](https://us.pycon.org/2023/about/code-of-conduct/)
132+
which was forked from the example policy from the
133+
[Geek Feminism wiki, created by Ada Initiative and other volunteers](https://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy),
134+
which is under a [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).

0 commit comments

Comments
 (0)