@@ -13,131 +13,200 @@ <h1 class="text-2xl-5xl">Haskell Foundation Guidelines For Respectful Communicat
1313
1414 < h2 > Preamble</ h2 >
1515
16- < p > The Haskell Foundation has adopted the Standards of Public Behaviour set
17- out below. Each representative of the Foundation commits themself to those
18- standards when interacting with other representatves and the public on
19- Haskell-related matters. We aspire to apply them in all our interactions in
20- the Haskell sphere, including email, social media and discussion forums.</ p >
21-
22- < p > The standards apply to our behaviour; that is, what we do. They
23- specifically do not, and should not, seek to constrain anyone's beliefs;
24- that is, what they think.</ p >
25-
26- < p > If one of us fails to meet these standards, the ideal course of action is
27- to write to that person privately, gently drawing attention to their lapse.
28- If you are not comfortable with that, please contact the Chair of the
29- Foundation, or (if the Chair is the problem) the Vice-Chair.</ p >
30-
31- < p > Our response should usually be to apologise and stop doing what it was
32- that you are unhappy about. Even if we feel we have been misinterpreted or
33- unfairly accused, the chances are good there was something we could have
34- communicated better, and an apology is far more likely to bring healing than
35- is a counter-accusation.</ p >
36-
37- < p > We do not seek to impose these standards on members of the Haskell
38- community. Rather, adopting the standards is a signal that we seek high
39- standards of discourse in the Haskell community, and are willing to publicly
40- hold ourselves to that standard, in the hope that others may voluntarily
41- follow suit.</ p >
16+ < p >
17+ The Haskell Foundation has adopted the Standards of Public Behaviour set
18+ out below. Each representative of the Foundation commits themself to those
19+ standards when interacting with other representatves and the public on
20+ Haskell-related matters. We aspire to apply them in all our interactions
21+ in the Haskell sphere, including email, social media and discussion
22+ forums.
23+ </ p >
24+
25+ < p >
26+ The standards apply to our behaviour; that is, what we do. They
27+ specifically do not, and should not, seek to constrain anyone's beliefs;
28+ that is, what they think.
29+ </ p >
30+
31+ < p >
32+ If one of us fails to meet these standards, the ideal course of action is
33+ to write to that person privately, gently drawing attention to their
34+ lapse. If you are not comfortable with that, please contact the Chair of
35+ the Foundation, or (if the Chair is the problem) the Vice-Chair.</ p >
36+
37+ < p >
38+ Our response should usually be to apologise and stop doing what it was
39+ that you are unhappy about. Even if we feel we have been misinterpreted or
40+ unfairly accused, the chances are good there was something we could have
41+ communicated better, and an apology is far more likely to bring healing
42+ than is a counter-accusation.
43+ </ p >
44+
45+ < p >
46+ We do not seek to impose these standards on members of the Haskell
47+ community. Rather, adopting the standards is a signal that we seek high
48+ standards of discourse in the Haskell community, and are willing to
49+ publicly hold ourselves to that standard, in the hope that others may
50+ voluntarily follow suit.
51+ </ p >
4252
4353 < h2 > Motivation</ h2 >
4454
45- < p > We are motivated to adopt these standards for several reasons,
46- including:</ p >
55+ < p >
56+ We are motivated to adopt these standards for several reasons, including:
57+ </ p >
4758
4859 < ul >
49- < li > Diversity and inclusion. We recognize that the Haskell community,
50- echoing the technology industry more generally, skews white and male. We
51- see it as our duty and honour to spread the joy of Haskell widely and to
52- broaden the patterns of participation, in the hopes that, one day, we will
53- no longer be askew.</ li >
54-
55- < li > Making an explicit commitment will encourage us to review our messages
56- to see if they meet the goals set out here, and will give others some
57- specifics to point to if we fail.</ li >
60+ < li >
61+ Diversity and inclusion. We recognize that the Haskell community,
62+ echoing the technology industry more generally, skews white and male. We
63+ see it as our duty and honour to spread the joy of Haskell widely and to
64+ broaden the patterns of participation, in the hopes that, one day, we
65+ will no longer be askew.
66+ </ li >
67+
68+ < li >
69+ Making an explicit commitment will encourage us to review our messages
70+ to see if they meet the goals set out here, and will give others some
71+ specifics to point to if we fail.
72+ </ li >
5873 </ ul >
5974
6075 < h2 > Acknowledgements</ h2 >
6176
62- < p > We would like to thank the communities and projects that established code
63- of conducts and diversity statements as our inspiration. They include:</ p >
77+ < p >
78+ We would like to thank the communities and projects that established code
79+ of conducts and diversity statements as our inspiration. They include:
80+ </ p >
6481
6582 < ul >
66- < li > A month before this document was first published, Michael Snoyman
67- proposed a
68- < a href ="https://www.snoyman.com/blog/2018/11/proposal-stack-coc " target ="_blank "> Stack code of conduct</ a >
69- with a motivation similar to ours.</ li >
70-
71- < li > The
72- < a href ="https://www.gnu.org/philosophy/kind-communication.html " target ="_blank "> GNU Kind Communication Guidelines</ a > ,
73- published in October 2018, also express the positive tone we seek;
74- < a href ="https://lwn.net/Articles/769167/ " target ="_blank "> Stallman’s post</ a >
75- explains the intent.</ li >
76-
77- < li > The
78- < a href ="https://wiki.snowdrift.coop/community/conduct " target ="_blank "> Snowdrift community code of conduct</ a >
79- also has a companion
80- < a href ="https://wiki.snowdrift.coop/community/honor-users " target ="_blank "> Guidelines for healthy communication</ a > .</ li >
81-
82- < li > < a href ="https://github.com/todogroup/opencodeofconduct/blob/gh-pages/index.md " target ="_blank "> Open code of conduct</ a > </ li >
83-
84- < 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 >
85-
86- < li > < a href ="https://www.rust-lang.org/policies/code-of-conduct " target ="_blank "> Rust code of conduct</ a > </ li >
87-
88- < li > < a href ="https://typelevel.org/code-of-conduct " target ="_blank "> TypeLevel code of conduct</ a > </ li >
89-
90- < li > < a href ="https://www.contributor-covenant.org/ " target ="_blank "> Contributor covenant</ a > </ li >
83+ < li >
84+ A month before this document was first published, Michael Snoyman
85+ proposed a
86+ < a href ="https://www.snoyman.com/blog/2018/11/proposal-stack-coc " target ="_blank ">
87+ Stack code of conduct
88+ </ a >
89+ with a motivation similar to ours.
90+ </ li >
91+
92+ < li >
93+ The
94+ < a href ="https://www.gnu.org/philosophy/kind-communication.html " target ="_blank ">
95+ GNU Kind Communication Guidelines</ a > ,
96+ published in October 2018, also express the positive tone we seek;
97+ < a href ="https://lwn.net/Articles/769167/ " target ="_blank ">
98+ Stallman’s post
99+ </ a >
100+ explains the intent.
101+ </ li >
102+
103+ < li >
104+ The
105+ < a href ="https://wiki.snowdrift.coop/community/conduct " target ="_blank ">
106+ Snowdrift community code of conduct
107+ </ a >
108+ also has a companion
109+ < a href ="https://wiki.snowdrift.coop/community/honor-users " target ="_blank ">
110+ Guidelines for healthy communication</ a > .
111+ </ li >
112+
113+ < li >
114+ < a href ="https://github.com/todogroup/opencodeofconduct/blob/gh-pages/index.md " target ="_blank ">
115+ Open code of conduct
116+ </ a >
117+ </ li >
118+
119+ < li >
120+ < a href ="https://github.com/python/pycon-code-of-conduct/blob/master/code_of_conduct.md " target ="_blank ">
121+ Pycon code of conduct
122+ </ a >
123+ </ li >
124+
125+ < li >
126+ < a href ="https://www.rust-lang.org/policies/code-of-conduct " target ="_blank ">
127+ Rust code of conduct
128+ </ a >
129+ </ li >
130+
131+ < li >
132+ < a href ="https://typelevel.org/code-of-conduct " target ="_blank ">
133+ TypeLevel code of conduct
134+ </ a >
135+ </ li >
136+
137+ < li >
138+ < a href ="https://www.contributor-covenant.org/ " target ="_blank ">
139+ Contributor covenant
140+ </ a >
141+ </ li >
91142 </ ul >
92143
93144 < h2 > Our Standards of Public Behaviour</ h2 >
94145
95146 < p > Version: 2025-05-29</ p >
96147
97148 < ul >
98- < li > The over-arching rule: < b > We strive to treat every person with
99- respect.</ b > </ p >
100-
101- < li > We welcome into the Haskell community people of all backgrounds,
102- identities, and beliefs, provided only that they in turn behave in the
103- respectful way articulated in these standards.</ li >
104-
105- < li > We treat everyone with courtesy, aware that their diverse backgrounds,
106- experiences, goals, and perspectives may be very different to ours.</ li >
107-
108- < li > In our communication, we consistently honour and affirm the passion,
109- professional expertise, and good intentions of others. When we doubt these
110- qualities in someone else, we prefer to deal with those matters
111- discreetly, instead of making public accusations.</ li >
112-
113- < li > We strive to be scrupulously polite at all times. There should be no
114- rudeness, name-calling, or harassment in our communication.</ li >
115-
116- < li > We avoid forms of expression and other behaviours that attack,
117- humiliate, demean, or marginalise - even where we disagree with that
118- person.</ li >
119-
120- < li > Disagreement itself is fine: we are enriched by robust technical
121- debate. But we seek to make the tone of that debate to be a conversation
122- among people who respect, or even admire, each other.</ li >
123-
124- < li > Where we disagree, we try to be curious about the perspective, goals,
125- motivation, and priorities of the other person.</ li >
126-
149+ < li >
150+ The over-arching rule: < b > We strive to treat every person with respect.</ b >
151+ </ li >
152+
153+ < li >
154+ We welcome into the Haskell community people of all backgrounds,
155+ identities, and beliefs, provided only that they in turn behave in the
156+ respectful way articulated in these standards.
157+ </ li >
158+
159+ < li >
160+ We treat everyone with courtesy, aware that their diverse backgrounds,
161+ experiences, goals, and perspectives may be very different to ours.
162+ </ li >
163+
164+ < li >
165+ In our communication, we consistently honour and affirm the passion,
166+ professional expertise, and good intentions of others. When we doubt
167+ these qualities in someone else, we prefer to deal with those matters
168+ discreetly, instead of making public accusations.
169+ </ li >
170+
171+ < li >
172+ We strive to be scrupulously polite at all times. There should be no
173+ rudeness, name-calling, or harassment in our communication.
174+ </ li >
175+
176+ < li >
177+ We avoid forms of expression and other behaviours that attack,
178+ humiliate, demean, or marginalise - even where we disagree with that
179+ person.
180+ </ li >
181+
182+ < li >
183+ Disagreement itself is fine: we are enriched by robust technical debate.
184+ But we seek to make the tone of that debate to be a conversation among
185+ people who respect, or even admire, each other.
186+ </ li >
187+
188+ < li >
189+ Where we disagree, we try to be curious about the perspective, goals,
190+ motivation, and priorities of the other person.
191+ </ li >
127192 </ ul >
128193
129194 < h3 > Copyright and licensing</ h3 >
130195
131- < p > To the extent that the Standards of Public Behaviour is a derivative
132- work (see the acknowledgements), the copyrights and licences of the original
133- works apply. To the extent that the Haskell Foundation holds any copyright
134- in the work, it releases it under
135- < a href ="https://creativecommons.org/publicdomain/zero/1.0/ "> CC0 1.0</ a > .
136- < img
137- src ="https://mirrors.creativecommons.org/presskit/icons/cc.svg "
138- style ="display: inline;max-width: 1em;max-height:1em;margin-left: .2em;margin-top: 0em;margin-bottom: 0em; ">
139- < img
140- src ="https://mirrors.creativecommons.org/presskit/icons/zero.svg "
141- style ="display: inline;max-width: 1em;max-height:1em;margin-left: .2em;margin-top: 0em;margin-bottom: 0em; "> </ p >
196+ < p >
197+ To the extent that the Standards of Public Behaviour is a derivative
198+ work (see the acknowledgements), the copyrights and licences of the
199+ original works apply. To the extent that the Haskell Foundation holds any
200+ copyright in the work, it releases it under
201+ < a href ="https://creativecommons.org/publicdomain/zero/1.0/ ">
202+ CC0 1.0</ a > .
203+ < img
204+ src ="https://mirrors.creativecommons.org/presskit/icons/cc.svg "
205+ style ="display: inline;max-width: 1em;max-height:1em;margin-left: .2em;margin-top: 0em;margin-bottom: 0em; "
206+ > < img
207+ src ="https://mirrors.creativecommons.org/presskit/icons/zero.svg "
208+ style ="display: inline;max-width: 1em;max-height:1em;margin-left: .2em;margin-top: 0em;margin-bottom: 0em; "
209+ >
210+ </ p >
142211 </ div >
143212</ div >
0 commit comments