Skip to content

Commit 297dbb9

Browse files
lektor-botlektor-bot
committed
Synchronized build
0 parents  commit 297dbb9

File tree

7 files changed

+641
-0
lines changed

7 files changed

+641
-0
lines changed

‎code-of-conduct/index.html‎

Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
<!DOCTYPE html>
2+
<html>
3+
4+
<head>
5+
<meta charset="utf-8" />
6+
<meta name="viewport" content="width=device-width, initial-scale=1" />
7+
<title>
8+
Code of Conduct— PuPPy
9+
</title>
10+
11+
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bulma@0.9.4/css/bulma.min.css" />
12+
<script defer src="https://use.fontawesome.com/releases/v5.0.7/js/all.js"></script>
13+
<link rel="stylesheet" href="../static/style.css?h=19d16282" />
14+
</head>
15+
16+
<body>
17+
18+
19+
<nav class="nav--fixed navbar is-fixed-top">
20+
<div class="container">
21+
<div class="navbar-brand">
22+
<div class="navbar-item">
23+
<a href="/" class="nav-link">
24+
<div class="nav-icon">
25+
<span class="fab fa-python fa-3x"></span>
26+
</div>
27+
28+
<div class="nav-title">
29+
<h3 class="is-size-4 has-text-weight-bold">PuPPy</h3>
30+
<p class="is-size-7 is-uppercase">Puget Sound Programming Python</p>
31+
</div>
32+
</a>
33+
</div>
34+
</div>
35+
</div>
36+
</nav>
37+
38+
39+
40+
<section class="main section">
41+
<div class="container">
42+
<div class="columns">
43+
<div class="column is-half">
44+
<h1 class="title">Code of Conduct</h1>
45+
<div class="content"><p>PuPPy is a Seattle-area Meetup made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission — including mentorship, teaching and connecting people.</p>
46+
<p>Diversity is one of our huge strengths, but it can also lead to communication issues. To support a welcoming environment for all, regardless of individual differences, we have a few ground rules that we ask people to adhere to when they participate in this community's activities. These rules apply equally to founders, organizers, moderators, sponsors, and affiliates — in short, to all participants.</p>
47+
<p>This isn’t an exhaustive list of things that you must do, or can’t do. Rather, take it in the spirit in which it’s intended. It’s a guide to make it easier to enrich all of us and the technical communities in which we participate, and which we represent.</p>
48+
</div>
49+
50+
<div class="content">
51+
<h2>The principles</h2>
52+
<ul>
53+
<li>Be friendly and welcoming. We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.</li>
54+
<li>Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Python community should be respectful when dealing with other members as well as with people outside the community.</li>
55+
<li>Be careful in the words that you choose. We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants, individually or as a group. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:<ul>
56+
<li>Violent threats or language directed against another person.</li>
57+
<li>Discriminatory jokes and language.</li>
58+
<li>Posting sexually explicit or violent material.</li>
59+
<li>Posting (or threatening to post) other people’s personally identifying information ("doxing").</li>
60+
<li>Personal insults, especially those using racist or sexist terms.</li>
61+
<li>Unwelcome sexual attention.</li>
62+
<li>Advocating for, or encouraging, any of the above behavior.</li>
63+
<li>Repeated harassment of others. In general, if someone asks you to stop, then stop.</li>
64+
</ul>
65+
</li>
66+
</ul>
67+
68+
</div>
69+
70+
<div class="content">
71+
<h2>Where does the code of conduct apply</h2>
72+
<p>This code of conduct applies to all spaces managed by PuPPy. This includes:</p>
73+
<ul>
74+
<li>Conferences (including social events and peripheral activities)</li>
75+
<li>Unconferences and sprints</li>
76+
<li>Meetups</li>
77+
<li>Workshops</li>
78+
<li>Presentation materials used in talks or sessions</li>
79+
<li>Slack</li>
80+
<li>Mailing lists</li>
81+
<li>GitHub</li>
82+
<li>Twitter hashtag</li>
83+
<li>meetup.com discussion boards</li>
84+
<li>Any other forums created by the community and used for communication.</li>
85+
</ul>
86+
<p>In addition, violations of this code outside these spaces may affect a person’s ability to participate within them.</p>
87+
88+
</div>
89+
90+
<div class="content">
91+
<h2>Sponsors, affiliates, and exhibitors</h2>
92+
<p>When you sponsor a PuPPy event, we welcome you as a member of our community, and we expect you to be respectful to the community you operate within.</p>
93+
<p>All exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the code of conduct. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) must not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.</p>
94+
<p>In addition, sponsors and affiliates of conference, meetups, and online activities should not employ aggressive recruiting techniques, invasive marketing behavior, or similar actions towards community members. In case of violations, sponsors might be sanctioned and expelled from the event or activity with no return of the sponsorship contribution.</p>
95+
96+
</div>
97+
98+
<div class="content">
99+
<h2>What to do in case of violations</h2>
100+
<p>If you believe that someone is violating the code of conduct during one of our events, please contact a member of the event staff immediately. Event staff are introduced at the beginning of every event, but if you missed the introduction or cannot find a staff member please reach out to one of the staff members listed in the <a href="../pages/code-of-conduct/reporting-guide">Reporting Guide</a>.</p>
101+
<p>If you believe someone is violating the code of conduct in one of our online platforms, we ask that you report it by emailing <a href="mailto:conduct@pspython.com">conduct@pspython.com</a>. To help us respond in the best way to the situation, please follow the <a href="../pages/code-of-conduct/reporting-guide">Code of Conduct Reporting Guide</a>. The code of conduct representatives employ the <a href="../pages/code-of-conduct/response-playbook">Code of Conduct Response Playbook</a> to handle reports.</p>
102+
<p>All reports will be kept confidential. In some cases a public statement might be required (for example in a CoC transparency report following an event), but these reports are anonymized and do not include any personally identifying information.</p>
103+
104+
</div>
105+
106+
<div class="content">
107+
<h2>Thanks</h2>
108+
<p>This code of conduct is largely based on the <a href="http://www.writethedocs.org/code-of-conduct/">Write The Docs Code of Conduct</a>, which in turn is based on the <a href="https://www.djangoproject.com/conduct/">Django Project Code of Conduct</a> and the original text of the Speak Up! project, inspired in its turn by the Fedora Project, as well as the Python Mentorship Project and many others.</p>
109+
110+
</div>
111+
</div>
112+
113+
<div class="column is-half">
114+
<div class="content">
115+
<h2>Related Pages</h2>
116+
<div class="conduct-pages">
117+
<ul>
118+
119+
<li>
120+
<a href="reporting-guide/">Reporting Guide</a>
121+
</li>
122+
123+
<li>
124+
<a href="response-playbook/">Response Playbook</a>
125+
</li>
126+
127+
</ul>
128+
</div>
129+
</div>
130+
</div>
131+
</div>
132+
</div>
133+
</section>
134+
135+
136+
</body>
137+
138+
</html>

‎code-of-conduct/reporting-guide/index.html‎

Lines changed: 151 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,151 @@
1+
<!DOCTYPE html>
2+
<html>
3+
4+
<head>
5+
<meta charset="utf-8" />
6+
<meta name="viewport" content="width=device-width, initial-scale=1" />
7+
<title>
8+
Reporting Guide— PuPPy
9+
</title>
10+
11+
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bulma@0.9.4/css/bulma.min.css" />
12+
<script defer src="https://use.fontawesome.com/releases/v5.0.7/js/all.js"></script>
13+
<link rel="stylesheet" href="../../static/style.css?h=19d16282" />
14+
</head>
15+
16+
<body>
17+
18+
19+
<nav class="nav--fixed navbar is-fixed-top">
20+
<div class="container">
21+
<div class="navbar-brand">
22+
<div class="navbar-item">
23+
<a href="/" class="nav-link">
24+
<div class="nav-icon">
25+
<span class="fab fa-python fa-3x"></span>
26+
</div>
27+
28+
<div class="nav-title">
29+
<h3 class="is-size-4 has-text-weight-bold">PuPPy</h3>
30+
<p class="is-size-7 is-uppercase">Puget Sound Programming Python</p>
31+
</div>
32+
</a>
33+
</div>
34+
</div>
35+
</div>
36+
</nav>
37+
38+
39+
40+
<section class="main section">
41+
<div class="container">
42+
<div class="columns">
43+
<div class="column is-half">
44+
<h1 class="title">Reporting Guide</h1>
45+
<div class="content"><p>In any PuPPy space (events or online), if you believe someone is violating the <a href="../../pages/code-of-conduct">Code of Conduct</a>, we ask that you report it to the staff by emailing <a href="mailto:conduct@pspython.com">conduct@pspython.com</a> or reporting to a staff person in person, if possible. All reports will be kept confidential. In some cases, we may determine that a public statement will need to be made. If that’s the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.</p>
46+
<p>If you believe anyone is in physical danger, please notify appropriate law enforcement first. If you are unsure which law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.</p>
47+
<p>If the violation occurs at an event (such as workshop, meetup), get in touch with one of the event staff right away, in any of the following ways:</p>
48+
<ul>
49+
<li>In person</li>
50+
<li>By email</li>
51+
</ul>
52+
</div>
53+
54+
<div class="content">
55+
<h2>Staff Contact Information</h2>
56+
57+
<p>
58+
If for any reason you need to report an issue, please contact us! You can email us at
59+
<a href="mailto:conduct@pspython.com">conduct@pspython.com</a>.
60+
</p>
61+
62+
63+
<p>
64+
<strong>Miles Erickson</strong>
65+
</p>
66+
<ul>
67+
<li>
68+
<a href="mailto:miles@pspython.com">miles@pspython.com</a>
69+
</li>
70+
<li>slack: @miles</li>
71+
</ul>
72+
73+
<p>
74+
<strong>Maelle Vance</strong>
75+
</p>
76+
<ul>
77+
<li>
78+
<a href="mailto:maelle@pspython.com">maelle@pspython.com</a>
79+
</li>
80+
<li>slack: @Maelle (they/them)</li>
81+
</ul>
82+
83+
<p>
84+
<strong>Russell Duhon</strong>
85+
</p>
86+
<ul>
87+
<li>
88+
<a href="mailto:russell@pspython.com">russell@pspython.com</a>
89+
</li>
90+
<li>slack: @fugu13</li>
91+
</ul>
92+
93+
</div>
94+
95+
<div class="content">
96+
<h2>What to include in the report</h2>
97+
<ul>
98+
<li>Your contact information (so we can get in touch with you if we need to follow up)</li>
99+
<li>Names of any individuals involved (real names, nicknames, or pseudonyms). If there were other witnesses besides you, please try to include them as well.</li>
100+
<li>When and where the incident occurred. Please be as specific as possible.</li>
101+
<li>Your account of what occurred. If there is a publicly available record (e.g., a mailing list archive or a public chat logger) please include a link. Our Slack Team is currently on a free plan that does not retain more than 10,000 messages of history, if an incident occurred on Slack please take a screenshot so it is not lost.</li>
102+
<li>Any extra context you believe existed for the incident.</li>
103+
<li>Whether you believe this incident is ongoing.</li>
104+
<li>Any other information you believe we should have.</li>
105+
</ul>
106+
107+
</div>
108+
109+
<div class="content">
110+
<h2>What happens after you file a report</h2>
111+
<p>The PuPPy community team aims to follow the process outlined in the <a href="../../pages/code-of-conduct/response-playbook">Code of Conduct Response Playbook</a>.</p>
112+
<p>We promise to acknowledge receipt of any reports within 24 hours or sooner, and a resolution (or update in case a resolution is delayed) within 7 days.</p>
113+
<p>Note: If the violation is determined to be an ongoing incident or a threat to physical safety, the staff’s immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.</p>
114+
<p>Once we determine the final needed action, we’ll contact the original reporter to let them know what action we’ll be taking, if any. Please understand that while we take into account feedback from the reporter on the appropriateness of our response, we cannot guarantee we can or will act on it.</p>
115+
<p>Finally, the staff may choose to make a public report of the incident if it was reported outside one of our conferences.</p>
116+
117+
</div>
118+
119+
<div class="content">
120+
<h2>Appealing</h2>
121+
<p>Only permanent resolutions (such as bans) may be appealed. To appeal a decision, contact the PuPPy staff at <a href="mailto:conduct@pspython.com">conduct@pspython.com</a> with your appeal and they will review the case.</p>
122+
123+
</div>
124+
</div>
125+
126+
<div class="column is-half">
127+
<div class="content">
128+
<h2>Related Pages</h2>
129+
<div class="conduct-pages">
130+
<ul>
131+
132+
<li>
133+
<a href="../">Code of Conduct</a>
134+
</li>
135+
136+
<li>
137+
<a href="../response-playbook/">Response Playbook</a>
138+
</li>
139+
140+
</ul>
141+
</div>
142+
</div>
143+
</div>
144+
</div>
145+
</div>
146+
</section>
147+
148+
149+
</body>
150+
151+
</html>

0 commit comments

Comments
 (0)