Skip to content

Commit 23fce9d

Browse files
committed
Fix #505 Reorganise existing GfRC
This takes the existing content and reorganises it to separate out the Standards of Public Behaviour (which are not specific to the Foundation) from the rest of the content (which puts the Standards in their Foundation context). The Standards are given an identifiable 'version' (using a bigendian date).
1 parent 59136f4 commit 23fce9d

File tree

1 file changed

+92
-29
lines changed

1 file changed

+92
-29
lines changed

guidelines-for-respectful-communication/index.html

Lines changed: 92 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -12,54 +12,117 @@ <h1 class="text-2xl-5xl">Haskell Foundation Guidelines For Respectful Communicat
1212
<div class="mx-auto prose md:prose-lg">
1313

1414
<h2>Preamble</h2>
15-
<p>The Haskell Foundation has adopted these guidelines for respectful communication.</p>
1615

17-
<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>
16+
<p>The Haskell Foundation has adopted the Standards of Public Behaviour set
17+
out below. As representatives of the Foundation, we commit ourselves to
18+
those standards and we aspire to apply them in all our public interactions
19+
in the Haskell sphere, including email, social media and discussion forums.</p>
1820

19-
<h2>Motivation</h2>
20-
<p>We are motivated to adopt a set of guidelines for respectful communication for several reasons</p>
21+
<p> The standards apply to our behaviour; that is, what we do. They
22+
specifically do not, and should not, seek to constrain anyone's beliefs;
23+
that is, what they think.</p>
2124

22-
<ul>
23-
<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>
24-
<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>
25-
</ul>
25+
<p>If one of us fails to meet these standards, the ideal course of action is
26+
to write to that person privately, gently drawing attention to their lapse.
27+
If you are not comfortable with that, please contact the Chair of the
28+
Foundation, or (if the Chair is the problem) the Vice-Chair.</p>
2629

27-
<h2>Guidelines For Respectful Communication</h2>
28-
<p>As members of the Haskell Foundation, we commit ourselves to a high standard of public behaviour. We have one over-arching rule:</p>
30+
<p>Our response should usually be to apologise and stop doing what it was
31+
that you are unhappy about. Even if we feel we have been misinterpreted or
32+
unfairly accused, the chances are good there was something we could have
33+
communicated better, and an apology is far more likely to bring healing than
34+
is a counter-accusation.</p>
2935

30-
<p><b>We strive to treat every person with respect.</b></p>
36+
<p>We do not seek to impose these standards on members of the Haskell
37+
community. Rather, adopting the standards is a signal that we seek high
38+
standards of discourse in the Haskell community, and are willing to publicly
39+
hold ourselves to that standard, in the hope that others may voluntarily
40+
follow suit.</p>
3141

32-
<p>Specifically, we aspire to these behaviours:</p>
42+
<h2>Motivation</h2>
43+
44+
<p>We are motivated to adopt these standards for several reasons,
45+
including:</p>
3346

3447
<ul>
35-
<li>We welcome into the Haskell community people of all backgrounds, identities, and beliefs, provided only that they in turn behave in the respectful way articulated in these guidelines. </li>
36-
<li>We treat everyone with courtesy, aware that their diverse backgrounds, experiences, goals, and perspectives may be very different to ours.</li>
37-
<li>In our communication, we consistently honour and affirm the passion, professional expertise, and good intentions of others. When we doubt these qualities in someone else, we prefer to deal with those matters discreetly, instead of making public accusations.</li>
38-
<li>We strive to be scrupulously polite at all times. There should be no rudeness, name-calling, or harassment in our communication.</li>
39-
<li>We avoid forms of expression and other behaviours that attack, humiliate, demean, or marginalise - even where we disagree with that person.</li>
40-
<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>
41-
<li>Where we disagree, we try to be curious about the perspective, goals, motivation, and priorities of the other person.</li>
42-
</ul>
48+
<li>Diversity and inclusion. We recognize that the Haskell community,
49+
echoing the technology industry more generally, skews white and male. We
50+
see it as our duty and honour to spread the joy of Haskell widely and to
51+
broaden the patterns of participation, in the hopes that, one day, we will
52+
no longer be askew.</li>
4353

44-
<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>
45-
<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>
54+
<li>Making an explicit commitment will encourage us to review our messages
55+
to see if they meet the goals set out here, and will give others some
56+
specifics to point to if we fail.</li>
57+
</ul>
4658

47-
<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>
59+
<h2>Acknowledgements</h2>
4860

49-
<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>
61+
<p>We would like to thank the communities and projects that established code
62+
of conducts and diversity statements as our inspiration. They include:</p>
5063

51-
<h2>Acknowledgements</h2>
52-
We'd like to thank the communities and projects that established code of conducts and diversity statements as our inspiration, including these:
5364
<ul>
54-
<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>
55-
<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>
56-
<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>
65+
<li>A month before this document was first published, Michael Snoyman
66+
proposed a
67+
<a href="https://www.snoyman.com/blog/2018/11/proposal-stack-coc" target="_blank">Stack code of conduct</a>
68+
with a motivation similar to ours.</li>
69+
70+
<li>The
71+
<a href="https://www.gnu.org/philosophy/kind-communication.html" target="_blank">GNU Kind Communication Guidelines</a>,
72+
published in October 2018, also express the positive tone we seek;
73+
<a href="https://lwn.net/Articles/769167/" target="_blank">Stallman’s post</a>
74+
explains the intent.</li>
75+
76+
<li>The
77+
<a href="https://wiki.snowdrift.coop/community/conduct" target="_blank">Snowdrift community code of conduct</a>
78+
also has a companion
79+
<a href="https://wiki.snowdrift.coop/community/honor-users" target="_blank">Guidelines for healthy communication</a>.</li>
80+
5781
<li><a href="https://github.com/todogroup/opencodeofconduct/blob/gh-pages/index.md" target="_blank">Open code of conduct</a></li>
82+
5883
<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>
84+
5985
<li><a href="https://www.rust-lang.org/policies/code-of-conduct" target="_blank">Rust code of conduct</a></li>
86+
6087
<li><a href="https://typelevel.org/code-of-conduct" target="_blank">TypeLevel code of conduct</a></li>
88+
6189
<li><a href="https://www.contributor-covenant.org/" target="_blank">Contributor covenant</a></li>
6290
</ul>
6391

92+
<h2>Our Standards of Public Behaviour</h2>
93+
94+
<p>Version: 2025-05-29</p>
95+
96+
<ul>
97+
<li>The over-arching rule: <b>We strive to treat every person with
98+
respect.</b></p>
99+
100+
<li>We welcome into the Haskell community people of all backgrounds,
101+
identities, and beliefs, provided only that they in turn behave in the
102+
respectful way articulated in these standards.</li>
103+
104+
<li>We treat everyone with courtesy, aware that their diverse backgrounds,
105+
experiences, goals, and perspectives may be very different to ours.</li>
106+
107+
<li>In our communication, we consistently honour and affirm the passion,
108+
professional expertise, and good intentions of others. When we doubt these
109+
qualities in someone else, we prefer to deal with those matters
110+
discreetly, instead of making public accusations.</li>
111+
112+
<li>We strive to be scrupulously polite at all times. There should be no
113+
rudeness, name-calling, or harassment in our communication.</li>
114+
115+
<li>We avoid forms of expression and other behaviours that attack,
116+
humiliate, demean, or marginalise - even where we disagree with that
117+
person.</li>
118+
119+
<li>Disagreement itself is fine: we are enriched by robust technical
120+
debate. But we seek to make the tone of that debate to be a conversation
121+
among people who respect, or even admire, each other.</li>
122+
123+
<li>Where we disagree, we try to be curious about the perspective, goals,
124+
motivation, and priorities of the other person.</li>
125+
126+
</ul>
64127
</div>
65128
</div>

0 commit comments

Comments
 (0)