Skip to content

Commit 204571c

Browse files
mpilgremmpilgrem
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 24924de commit 204571c

File tree

1 file changed

+74
-83
lines changed

1 file changed

+74
-83
lines changed

‎guidelines-for-respectful-communication/index.html‎

Lines changed: 74 additions & 83 deletions
Original file line numberDiff line numberDiff line change
@@ -14,22 +14,42 @@ <h1 class="text-2xl-5xl">Haskell Foundation Guidelines For Respectful Communicat
1414
<h2>Preamble</h2>
1515

1616
<p>
17-
The Haskell Foundation has adopted these guidelines for respectful
18-
communication.
17+
The Haskell Foundation has adopted the Standards of Public Behaviour set
18+
out below. As representatives of the Foundation, we commit ourselves to
19+
those standards and we aspire to apply them in all our public interactions
20+
in the Haskell sphere, including email, social media and discussion
21+
forums.
1922
</p>
2023
<p>
21-
We do not seek to impose these guidelines on members of the Haskell
22-
community generally. Rather it is a signal that we seek high standards of
23-
discourse in the Haskell community, and are willing to publicly hold
24-
ourselves to that standard, in the hope that others may voluntarily follow
25-
suit.
24+
The standards apply to our behaviour; that is, what we do. They
25+
specifically do not, and should not, seek to constrain anyone's beliefs;
26+
that is, what they think.
27+
</p>
28+
<p>
29+
If one of us fails to meet these standards, the ideal course of action is
30+
to write to that person privately, gently drawing attention to their
31+
lapse. If you are not comfortable with that, please contact the Chair of
32+
the Foundation, or (if the Chair is the problem) the Vice-Chair.
33+
</p>
34+
<p>
35+
Our response should usually be to apologise and stop doing what it was
36+
that you are unhappy about. Even if we feel we have been misinterpreted or
37+
unfairly accused, the chances are good there was something we could have
38+
communicated better, and an apology is far more likely to bring healing
39+
than is a counter-accusation.
40+
</p>
41+
<p>
42+
We do not seek to impose these standards on members of the Haskell
43+
community. Rather, adopting the standards is a signal that we seek high
44+
standards of discourse in the Haskell community, and are willing to
45+
publicly hold ourselves to that standard, in the hope that others may
46+
voluntarily follow suit.
2647
</p>
2748

2849
<h2>Motivation</h2>
2950

3051
<p>
31-
We are motivated to adopt a set of guidelines for respectful communication
32-
for several reasons
52+
We are motivated to adopt these standards for several reasons, including:
3353
</p>
3454
<ul>
3555
<li>
@@ -46,83 +66,11 @@ <h2>Motivation</h2>
4666
</li>
4767
</ul>
4868

49-
<h2>Guidelines For Respectful Communication</h2>
50-
51-
<p>
52-
As members of the Haskell Foundation, we commit ourselves to a high
53-
standard of public behaviour. We have one over-arching rule:
54-
</p>
55-
<p>
56-
<b>We strive to treat every person with respect.</b>
57-
</p>
58-
<p>
59-
Specifically, we aspire to these behaviours:
60-
</p>
61-
<ul>
62-
<li>
63-
We welcome into the Haskell community people of all backgrounds,
64-
identities, and beliefs, provided only that they in turn behave in the
65-
respectful way articulated in these guidelines.
66-
</li>
67-
<li>
68-
We treat everyone with courtesy, aware that their diverse backgrounds,
69-
experiences, goals, and perspectives may be very different to ours.
70-
</li>
71-
<li>
72-
In our communication, we consistently honour and affirm the passion,
73-
professional expertise, and good intentions of others. When we doubt
74-
these qualities in someone else, we prefer to deal with those matters
75-
discreetly, instead of making public accusations.
76-
</li>
77-
<li>
78-
We strive to be scrupulously polite at all times. There should be no
79-
rudeness, name-calling, or harassment in our communication.
80-
</li>
81-
<li>
82-
We avoid forms of expression and other behaviours that attack,
83-
humiliate, demean, or marginalise - even where we disagree with that
84-
person.
85-
</li>
86-
<li>
87-
Disagreement itself is fine: we are enriched by robust technical debate.
88-
But we seek to make the tone of that debate to be a conversation among
89-
people who respect, or even admire, each other.
90-
</li>
91-
<li>
92-
Where we disagree, we try to be curious about the perspective, goals,
93-
motivation, and priorities of the other person.
94-
</li>
95-
</ul>
96-
<p>
97-
We seek to apply these standards in all our public interactions in the
98-
Haskell sphere, including email, social media, discussion forums, and so
99-
on.
100-
</p>
101-
<p>
102-
All these guidelines apply to our behaviour; that is, what we do. They
103-
specifically do not, and should not, seek to constrain anyone's beliefs;
104-
that is, what they think.
105-
</p>
106-
<p>
107-
If one of us fails to meet these standards, the ideal course of action is
108-
to write to that person privately, gently drawing attention to their
109-
lapse. If you're not comfortable with that, please contact the chair of
110-
the Foundation, or (if the chair is the problem) the vice-chair or
111-
co-chair.
112-
</p>
113-
<p>
114-
Our response should usually be to apologise and stop doing what it was
115-
that you are unhappy about. Even if we feel we have been misinterpreted or
116-
unfairly accused, the chances are good there was something we could have
117-
communicated better, and an apology is far more likely to bring healing
118-
than is a counter-accusation.
119-
</p>
120-
12169
<h2>Acknowledgements</h2>
12270

12371
<p>
124-
We'd like to thank the communities and projects that established code of
125-
conducts and diversity statements as our inspiration, including these:
72+
We would like to thank the communities and projects that established code
73+
of conducts and diversity statements as our inspiration. They include:
12674
</p>
12775
<ul>
12876
<li>
@@ -179,5 +127,48 @@ <h2>Acknowledgements</h2>
179127
</li>
180128
</ul>
181129

130+
<h2>Our Standards of Public Behaviour</h2>
131+
132+
<p>Version: 2025-05-29</p>
133+
134+
<ul>
135+
<li>
136+
The over-arching rule: <b>We strive to treat every person with respect.</b>
137+
</li>
138+
<li>
139+
We welcome into the Haskell community people of all backgrounds,
140+
identities, and beliefs, provided only that they in turn behave in the
141+
respectful way articulated in these standards.
142+
</li>
143+
<li>
144+
We treat everyone with courtesy, aware that their diverse backgrounds,
145+
experiences, goals, and perspectives may be very different to ours.
146+
</li>
147+
<li>
148+
In our communication, we consistently honour and affirm the passion,
149+
professional expertise, and good intentions of others. When we doubt
150+
these qualities in someone else, we prefer to deal with those matters
151+
discreetly, instead of making public accusations.
152+
</li>
153+
<li>
154+
We strive to be scrupulously polite at all times. There should be no
155+
rudeness, name-calling, or harassment in our communication.
156+
</li>
157+
<li>
158+
We avoid forms of expression and other behaviours that attack,
159+
humiliate, demean, or marginalise - even where we disagree with that
160+
person.
161+
</li>
162+
<li>
163+
Disagreement itself is fine: we are enriched by robust technical debate.
164+
But we seek to make the tone of that debate to be a conversation among
165+
people who respect, or even admire, each other.
166+
</li>
167+
<li>
168+
Where we disagree, we try to be curious about the perspective, goals,
169+
motivation, and priorities of the other person.
170+
</li>
171+
</ul>
172+
182173
</div>
183174
</div>

0 commit comments

Comments
 (0)