Skip to content

Commit 2c35610

Browse files
RoboroadsRoboroads
committed
feat: Code of Conduct
1 parent d3abb74 commit 2c35610

File tree

2 files changed

+345
-8
lines changed

2 files changed

+345
-8
lines changed

‎src/routes/PracticalInformationSection.svelte

+14-8
Original file line numberDiff line numberDiff line change
@@ -45,12 +45,18 @@
4545
</TagBlock>
4646
</a>
4747

48-
<a
49-
class="mt-10 inline"
50-
target="_blank"
51-
rel="noreferrer"
52-
href="https://github.com/OrdinaNederland/frontendfestival.nl"
53-
>
54-
<TagBlock backgroundColor="fountain" small>Source on GitHub</TagBlock>
55-
</a>
48+
<div class="mt-10 flex gap-6">
49+
<a class="inline" target="_blank" href="/code-of-conduct">
50+
<TagBlock backgroundColor="fountain" small>Code of Conduct</TagBlock>
51+
</a>
52+
53+
<a
54+
class="inline"
55+
target="_blank"
56+
rel="noreferrer"
57+
href="https://github.com/OrdinaNederland/frontendfestival.nl"
58+
>
59+
<TagBlock backgroundColor="fountain" small>Source on GitHub</TagBlock>
60+
</a>
61+
</div>
5662
</div>

‎src/routes/code-of-conduct/+page.svelte

+331
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,331 @@
1+
<script>
2+
import Spacer from '../Spacer.svelte';
3+
</script>
4+
5+
<Spacer />
6+
<div class="flex-center w-full bg-black p-10 text-left text-white">
7+
<div class="w-full max-w-screen-md">
8+
<h1 class="text-4xl">Code of Conduct - Frontend Festival 2024</h1>
9+
<p>
10+
Frontend Festival is a community event intended for networking and collaboration in the
11+
developer community. We value the participation of each member of the Frontend Festival
12+
community and want all participants to have an enjoyable and fulfilling experience.
13+
Accordingly, all attendees are expected to show respect and courtesy to other attendees
14+
throughout the conference and at all conference events. To make clear what is expected, all
15+
staff, attendees, speakers, exhibitors, organisers, and volunteers at Frontend Festival are
16+
required to conform to the following Code of Conduct. Organisers will enforce this code
17+
throughout the event.
18+
</p>
19+
20+
<h2>OUR COMMUNITY</h2>
21+
<p>
22+
Members of the Frontend Festival community are <strong
23+
>open, considerate, and respectful.</strong
24+
> Behaviors that reinforce these values contribute to a positive environment, and include:
25+
</p>
26+
<ul>
27+
<li><strong>Being open.</strong> Members of the community are open to collaboration.</li>
28+
<li>
29+
<strong>Focusing on what is best for the community.</strong> We’re respectful of the processes
30+
set forth in the community, and we work within them.
31+
</li>
32+
<li>
33+
<strong>Acknowledging time and effort.</strong> We’re respectful of the volunteer efforts that
34+
permeate the Frontend Festival community. We’re thoughtful when addressing the efforts of others,
35+
keeping in mind that oftentimes the labour was completed simply for the good of the community.
36+
</li>
37+
<li>
38+
<strong>Showing empathy towards other community members.</strong> We’re attentive in our communications,
39+
whether in person or online, and we’re tactful when approaching differing views.
40+
</li>
41+
<li>
42+
<strong>Being considerate.</strong> Members of the community are considerate of their peers.
43+
</li>
44+
<li>
45+
<strong>Being respectful.</strong> We’re respectful of others, their positions, their skills,
46+
their commitments, and their efforts. We’re receptive to constructive comments and criticism,
47+
as the experiences and skill sets of other members
48+
</li>
49+
contribute to the whole of our efforts.
50+
<li>
51+
<strong>Gracefully accepting constructive criticism.</strong> When we disagree, we are courteous
52+
in raising our issues.
53+
</li>
54+
<li>
55+
<strong>Using welcoming and inclusive language.</strong> We’re accepting of all who wish to take
56+
part in our activities, fostering an environment where anyone can participate and everyone can
57+
make a difference.
58+
</li>
59+
</ul>
60+
61+
<h2>OUR STANDARDS</h2>
62+
<p>
63+
Every member of our community has the right to have their identity respected. The Frontend
64+
Festival community is dedicated to providing a positive experience for everyone, regardless of
65+
age, gender identity and expression, sexual orientation, disability, physical appearance, body
66+
size, ethnicity, nationality, race, religion (or lack thereof), education, cultural and
67+
cognitive variations, or socio-economic status.
68+
</p>
69+
70+
<h2>INAPPROPRIATE BEHAVIOR</h2>
71+
<p>Examples of unacceptable behaviour by participants include:</p>
72+
<ul>
73+
<li>Harassment of any participants in any form</li>
74+
<li>Deliberate intimidation, stalking, or following</li>
75+
<li>Logging or taking screenshots of online activity for harassment purposes</li>
76+
<li>
77+
Publishing others’ private information, such as a physical or electronic address, without
78+
explicit permission
79+
</li>
80+
<li>Violent threats or language directed against another person</li>
81+
<li>
82+
Incitement of violence or harassment towards any individual, including encouraging a person
83+
to commit suicide or to engage in self-harm
84+
</li>
85+
<li>
86+
Creating additional online accounts in order to harass another person or circumvent a ban
87+
</li>
88+
<li>
89+
Language and imagery in online communities or in any conference venue, including talks, that
90+
sexualises, insults, demeans, or attacks groups or specific individuals
91+
</li>
92+
<li>
93+
Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that
94+
hold others up for ridicule
95+
</li>
96+
<li>Unwelcome sexual attention or advances</li>
97+
<li>
98+
Unwelcome physical contact, including simulated physical contact (e.g., textual descriptions
99+
like “hug” or “backrub”) without consent or after a request to stop
100+
</li>
101+
<li>
102+
Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of
103+
intimacy with others
104+
</li>
105+
<li>
106+
Sustained disruption of online community discussions, in-person presentations, or other
107+
in-person events
108+
</li>
109+
<li>Continued one-on-one communication after requests to cease</li>
110+
<li>
111+
Other conduct that is inappropriate for a professional audience including people of many
112+
different backgrounds
113+
</li>
114+
</ul>
115+
<p>
116+
The Frontend Festival organisation will be happy to answer any questions related to marketing
117+
or recruiting activities.
118+
</p>
119+
120+
<h2>BE PROFESSIONAL AND DON'T SPAM</h2>
121+
<p>
122+
We consider Frontend Festival a great setting to showcase the work of the community and would
123+
like to encourage networking and business related discussions, as well as keep the conference
124+
presentations meaningful and interesting for everyone. We therefore:
125+
</p>
126+
<ul>
127+
<li>
128+
primarily make company marketing, promotional or recruiting related activities at the
129+
conference available to our paid sponsors, unless agreed otherwise;
130+
</li>
131+
<li>
132+
request presentations - outside the official recruiting sessions - to focus on Frontend
133+
Festival related topics, not on recruitment.
134+
</li>
135+
</ul>
136+
<p>
137+
The Frontend Festival organisation will be happy to answer any questions related to marketing
138+
or recruiting activities.
139+
</p>
140+
141+
<h2>CONSEQUENCES</h2>
142+
<p>
143+
If a participant engages in behaviour that violates this Code of Conduct, the Frontend
144+
Festival organization team may take action they deem appropriate, including warning the
145+
offender or expulsion from the community and community events with no refund of event tickets.
146+
Thank you for helping make this a welcoming, friendly community for everyone.
147+
</p>
148+
149+
<h2>SCOPE</h2>
150+
<h3>Frontend Festival</h3>
151+
<p>This Code of Conduct applies to the following people at Frontend Festival:</p>
152+
<ul>
153+
<li>staff</li>
154+
<li>speakers</li>
155+
<li>panellists</li>
156+
<li>tutorial or workshop leaders</li>
157+
<li>poster presenters</li>
158+
<li>people invited to meetings or summits</li>
159+
<li>exhibitors</li>
160+
<li>organisers</li>
161+
<li>volunteers</li>
162+
<li>sponsors</li>
163+
<li>all attendees</li>
164+
</ul>
165+
<p>The Code of Conduct applies in official venue event spaces, including:</p>
166+
<ul>
167+
<li>exhibit hall or vendor tabling area</li>
168+
<li>panel and presentation rooms</li>
169+
<li>hackathon or sprint rooms</li>
170+
<li>tutorial or workshop rooms</li>
171+
<li>poster session rooms</li>
172+
<li>summit or meeting rooms</li>
173+
<li>staff areas</li>
174+
<li>meal areas</li>
175+
<li>party suites</li>
176+
<li>walkways, hallways, elevators, and stairs that connect any of the above spaces</li>
177+
</ul>
178+
<p>
179+
The Code of Conduct applies to interactions with official event accounts on social media
180+
spaces and phone applications, including:
181+
</p>
182+
<ul>
183+
<li>comments made on official conference phone apps</li>
184+
<li>comments made on event video hosting services</li>
185+
<li>comments made on the official event hashtag or panel hashtags</li>
186+
</ul>
187+
<p>Event organizers will enforce this code throughout the event.</p>
188+
189+
<h2>CONTACT INFORMATION</h2>
190+
<p>
191+
If you believe that someone is violating the code of conduct, or have any other concerns,
192+
please contact a member of the Frontend Festival organization immediately. They can be reached
193+
by emailing codeandcomedy@ordina.com which is monitored by Bjorn Schijff, Roderick Huijgen,
194+
Mark Poelstra and Michael Awad. In case of a conflict of interest, you can individually
195+
contact:
196+
</p>
197+
<ul>
198+
<li>Eva Munscher – eva.munscher@ordina.com</li>
199+
</ul>
200+
<p>
201+
Conference staff will be happy to help participants contact venue security or local law
202+
enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration
203+
of the conference. We value your attendance. Local Emergency Numbers:
204+
</p>
205+
<ul>
206+
<li>(European) emergency services: 112</li>
207+
<li>Non-emergency police services: 0900-8844</li>
208+
</ul>
209+
210+
<h2>PROCEDURE FOR HANDLING INCIDENTS</h2>
211+
<p>
212+
When the organization team receives a report of a possible Code of Conduct violation, it will:
213+
</p>
214+
<ol>
215+
<li>Acknowledge the receipt of the report.</li>
216+
<li>Evaluate conflicts of interest.</li>
217+
<li>Call a meeting with the organization team who do not have a conflict of interest.</li>
218+
<li>Evaluate the reported incident.</li>
219+
<li>Propose a behavioral modification plan.</li>
220+
<li>Propose consequences for the reported behavior.</li>
221+
<li>Vote on behavioral modification plan and consequences for the reported person.</li>
222+
<li>
223+
Contact online community administrators/moderators to approve the behavioral modification
224+
plan and consequences.
225+
</li>
226+
<li>Follow up with the reported person.</li>
227+
<li>Decide further responses.</li>
228+
<li>Follow up with the reporter.</li>
229+
</ol>
230+
231+
<h2>LICENSE</h2>
232+
<p>
233+
This Code of Conduct is licensed under the <a
234+
href="https://creativecommons.org/licenses/by-sa/3.0/"
235+
target="_blank">Creative Commons Attribution-ShareAlike 3.0 Unported License</a
236+
>.
237+
</p>
238+
239+
<h2>ATTRIBUTIONS</h2>
240+
<p>
241+
This code of conduct is based on the <a
242+
href="https://policies.python.org/us.pycon.org/code-of-conduct/"
243+
target="_blank">PyCon US Code of Conduct</a
244+
>. The PyCon US Code of Conduct was forked from the example policy from the
245+
<a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy" target="_blank"
246+
>Geek Feminism wiki, created by the Ada Initiative and other volunteers</a
247+
>, which is under a
248+
<a href="https://creativecommons.org/publicdomain/zero/1.0/" target="_blank"
249+
>Creative Commons Zero license</a
250+
>. Language was incorporated from the following Codes of Conduct:
251+
</p>
252+
<ul>
253+
<li>
254+
<a href="https://affectconf.com/coc/" target="_blank">Affect Conf Code of Conduct</a>,
255+
licensed under a
256+
<a href="http://creativecommons.org/licenses/by-sa/3.0/" target="_blank"
257+
>Creative Commons Attribution-ShareAlike 3.0 Unported License</a
258+
>.
259+
</li>
260+
<li>
261+
<a href="https://www.contributor-covenant.org/version/1/4/code-of-conduct" target="_blank"
262+
>Contributor Covenant version 1.4</a
263+
>, licensed
264+
<a
265+
href="https://github.com/ContributorCovenant/contributor_covenant/blob/master/LICENSE.md"
266+
target="_blank">Creative Commons Attribution 4.0 Licence</a
267+
>.
268+
</li>
269+
<li>
270+
<a href="https://www.djangoproject.com/conduct/" target="_blank"
271+
>Django Project Code of Conduct</a
272+
>, licensed under a
273+
<a href="http://creativecommons.org/licenses/by/3.0/" target="_blank"
274+
>Creative Commons Attribution 3.0 Unported License</a
275+
>.
276+
</li>
277+
<li>
278+
<a href="https://lgbtq.technology/coc.html" target="_blank"
279+
>LGBTQ in Tech Slack Code of Conduct</a
280+
>, licensed under a
281+
<a href="https://creativecommons.org/publicdomain/zero/1.0/" target="_blank"
282+
>Creative Commons Zero License</a
283+
>.
284+
</li>
285+
<li>
286+
<a href="https://us.pycon.org/2018/about/code-of-conduct/" target="_blank"
287+
>PyCon 2018 Code of Conduct</a
288+
>
289+
and
290+
<a href="https://us.pycon.org/2022/about/code-of-conduct/" target="_blank"
291+
>PyCon 2022 Code of Conduct</a
292+
>, licensed under a
293+
<a href="http://creativecommons.org/licenses/by/3.0/" target="_blank"
294+
>Creative Commons Attribution 3.0 Unported License</a
295+
>.
296+
</li>
297+
<li>
298+
<a href="https://www.rust-lang.org/en-US/conduct.html" target="_blank"
299+
>Rust Code of Conduct</a
300+
>
301+
</li>
302+
</ul>
303+
</div>
304+
</div>
305+
<Spacer />
306+
307+
<style lang="postcss">
308+
h1 {
309+
@apply text-4xl;
310+
}
311+
312+
h2 {
313+
@apply mt-6 text-2xl;
314+
}
315+
316+
h3 {
317+
@apply mt-3 text-xl;
318+
}
319+
320+
ul {
321+
@apply list-disc py-3 pl-5;
322+
}
323+
324+
ol {
325+
@apply list-decimal py-3 pl-5;
326+
}
327+
328+
a {
329+
@apply underline;
330+
}
331+
</style>

0 commit comments

Comments
 (0)