-
Notifications
You must be signed in to change notification settings - Fork 47
/
Copy pathindex.html
65 lines (51 loc) · 5.9 KB
/
index.html
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
---
title: Guidelines for Respectful Communications
---
<div class="max-w-screen-xl mx-auto py-16 md:py-24">
$partial("templates/corners.html")$
<div class="text-center pt-12 md:pt-20 px-12 sm:px-16 md:px-24 lg:px-36 ">
<h1 class="text-2xl-5xl">Haskell Foundation Guidelines For Respectful Communication</h1>
</div>
</div>
<div class="px-4 sm:px-8 md:px-12 lg:px-16">
<div class="mx-auto prose md:prose-lg">
<h2>Preamble</h2>
<p>The Haskell Foundation has adopted these guidelines for respectful communication.</p>
<p>We do not seek to impose these guidelines on members of the Haskell community generally. Rather it is a signal that we seek high standards of discourse in the Haskell community, and are willing to publicly hold ourselves to that standard, in the hope that others may voluntarily follow suit.</p>
<h2>Motivation</h2>
<p>We are motivated to adopt a set of guidelines for respectful communication for several reasons</p>
<ul>
<li>Diversity and inclusion. We recognize that the Haskell community, echoing the technology industry more generally, skews white and male. We see it as our duty and honour to spread the joy of Haskell widely and to broaden the patterns of participation, in the hopes that, one day, we will no longer be askew.</li>
<li>Making an explicit commitment will encourage us to review our messages to see if they meet the goals set out here, and will give others some specifics to point to if we fail.</li>
</ul>
<h2>Guidelines For Respectful Communication</h2>
<p>As members of the Haskell Foundation, we commit ourselves to a high standard of public behaviour. We have one over-arching rule:</p>
<p><b>We strive to treat every person with respect.</b></p>
<p>Specifically, we aspire to these behaviours:</p>
<ul>
<li>We welcome as members of the Haskell community people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, colour, 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>
<li>We treat everyone with courtesy, aware that their diverse backgrounds, experiences, goals, and perspectives may be very different to ours.</li>
<li>In our communication, we consistently honour and affirm the passion, professional expertise, and good intentions of others. Even if we occasionally doubt these qualities in someone else, we will not make public accusations of incompetence, malice or ulterior motives.</li>
<li>We strive to be scrupulously polite at all times. There should be no rudeness, name-calling, or harassment in our communication.</li>
<li>Where we disagree with someone, we avoid forms of expression that might make our dialogue partner feel attacked, humiliated, demeaned, or marginalised. Our critique should always be of specific statements and claims, never of people.</li>
<li>Disagreement itself is fine: we are enriched by robust technical debate. But we seek to make the tone of that debate to be a conversation among people who respect, or even admire, each other.</li>
<li>Where we disagree, we try to be curious about the perspective, goals, motivation, and priorities of the other person.</li>
</ul>
<p>We seek to apply these standards in all our public interactions in the Haskell sphere, including email, social media, discussion forums, and so on.</p>
<p> All these guidelines apply to our behaviour; that is, what we do. They specifically do not, and should not, seek to constrain anyone's beliefs; that is, what they think.</p>
<p>If one of us fails to meet these standards, the ideal course of action is to write to that person privately, gently drawing attention to their lapse. If you're not comfortable with that, please contact the chair of the Foundation, or (if the chair is the problem) the vice-chair or co-chair.</p>
<p>Our response should usually be to apologise and stop doing what it was that you are unhappy about. Even if we feel we have been misinterpreted or unfairly accused, the chances are good there was something we could have communicated better, and an apology is far more likely to bring healing than is a counter-accusation.</p>
<h2>Acknowledgements</h2>
We'd like to thank the communities and projects that established code of conducts and diversity statements as our inspiration, including these:
<ul>
<li>A month before this document was first published, Michael Snoyman proposed a <a href="https://www.snoyman.com/blog/2018/11/proposal-stack-coc" target="_blank">Stack code of conduct</a> with a motivation similar to ours.</li>
<li>The <a href="https://www.gnu.org/philosophy/kind-communication.html" target="_blank">GNU Kind Communication Guidelines</a>, published in October 2018, also express the positive tone we seek; <a href="https://lwn.net/Articles/769167/" target="_blank">Stallman’s post</a> explains the intent.</li>
<li>The <a href="https://wiki.snowdrift.coop/community/conduct" target="_blank">Snowdrift community code of conduct</a> also has a companion <a href="https://wiki.snowdrift.coop/community/honor-users" target="_blank">Guidelines for healthy communication</a>.</li>
<li><a href="https://github.com/todogroup/opencodeofconduct/blob/gh-pages/index.md" target="_blank">Open code of conduct</a></li>
<li><a href="https://github.com/python/pycon-code-of-conduct/blob/master/code_of_conduct.md" target="_blank">Pycon code of conduct</a></li>
<li><a href="https://www.rust-lang.org/policies/code-of-conduct" target="_blank">Rust code of conduct</a></li>
<li><a href="https://typelevel.org/code-of-conduct" target="_blank">TypeLevel code of conduct</a></li>
<li><a href="https://www.contributor-covenant.org/" target="_blank">Contributor covenant</a></li>
</ul>
</div>
</div>