<div dir="ltr"><div dir="ltr">I agree with and endorse KaiRo's points here.<br>One of the most eye opening articles I've ever read on the topic of dealing with unacceptable behavior came from a restaurant dealing with harassment from customers. They developed a soccer/football-style "yellow/orange/red" "card" system where the front-line staff who are directly exposed/vulnerable are able to tell a supervisor a color keyword with automatic, progressive responses to the problem.</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://www.forbes.com/sites/laurajames/2019/08/30/the-customer-is-not-always-right-this-new-system-for-restaurants-protects-workers-from-sexual-harassment/">https://www.forbes.com/sites/laurajames/2019/08/30/the-customer-is-not-always-right-this-new-system-for-restaurants-protects-workers-from-sexual-harassment/</a></div><div dir="ltr"><br></div><div dir="ltr">Obviously in digital, volunteer environments things will be very different from a restaurant, but from my experience in makerspaces I've seen firsthand how it's important to not have to convene a board meeting just to deal with a random idiot: when things are spelled out and pre-agreed-upon, offenses can be moderated proportionately and immediately by volunteers and community members. Ideally (and often, from what I've seen) a potentially abusive member hits a yellow/orange situation (testing the waters) and we have an opportunity to correct their misbehavior before it deserves a more formalized, consequential red response. In my work as a Reddit moderator, for example, I give out a lot of "hey your comment was removed for these reasons, this is your first warning" type messages, and it's always eye opening who manages to correct themselves and who goes for broke and earns themselves a ban. And as we see, often Reddit users themselves will reply with "messages like you're breaking the rules, please stop" without any moderator attention at all.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jan 10, 2021 at 1:34 PM Robert Kaiser <<a href="mailto:kairo@kairo.at" target="_blank">kairo@kairo.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Allan Mustard schrieb:<br>
> We have asked the Local Chapters and Communities Working Group<br>
> (LCCWG ) to take the lead on this and to work with signatories of<br>
> the open letter to the Board [1] as well as members of the Diversity<br>
> and Inclusion Special Committee to produce proposals for the Board<br>
> to consider at its January meeting. The LCCWG has accepted this<br>
> task. This issue will be on the agenda of the January meeting of<br>
> the Board of Directors, exact time and date yet to be determined,<br>
> though as is customary it will be posted to the Foundation's website<br>
> well in advance.<br>
<br>
Thanks for taking this on, I think it's good to have a set of rules or <br>
guidelines written down - and enforced - so all people participating in <br>
the community can feel to be in a safe space when taking part in any <br>
actions and discussions.<br>
<br>
Many of us feel like we should not need a CoC or similar because it <br>
should be common sense to treat everyone else with respect and don't <br>
discriminate against other groups or minorities, and I agree that it <br>
SHOULD not be necessary to have such rules - but reality unfortunately <br>
shows that there are people who end up undermining that common sense and <br>
then you actually need such an instrument. Also, due to bad experiences <br>
in their past, a number of people in underrepresented groups tend to not <br>
feel safe if they don't know if such a framework exists and will be <br>
enforced if necessary.<br>
<br>
We had those discussions years ago in the Mozilla community as well, and <br>
we ended up with a document that I think is really good, and also <br>
managed to avoid the "code of conduct" name that feels pretty <br>
indoctrinating to some people, while still being very clear about what <br>
this all means, the name we ended up with is "Community Participation <br>
Guidelines". Note that I strongly believe that any such framework isn't <br>
worth much if there is no enforcement, so let's make sure we define that <br>
for OSM when we go into this - the Mozilla document has the <br>
surface-level information for that in the "Consequences" and "Reporting" <br>
sections - it's of course important to have a defined process of how to <br>
treat reports and how they lead to said consequences.<br>
<br>
The Mozilla document is here in its current version: <br>
<a href="https://www.mozilla.org/en-US/about/governance/policies/participation/" rel="noreferrer" target="_blank">https://www.mozilla.org/en-US/about/governance/policies/participation/</a><br>
<br>
(Note: I am a long-term Mozilla community member, but just like in the <br>
OSM community, I'm not in any relevant power position there, I've just <br>
been a discussion participant when those guidelines were first designed.)<br>
<br>
I hope this can help as a constructive input to this topic.<br>
<br>
Cheers,<br>
KaiRo<br>
<br>
<br>
_______________________________________________<br>
osmf-talk mailing list<br>
<a href="mailto:osmf-talk@openstreetmap.org" target="_blank">osmf-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/osmf-talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/osmf-talk</a><br>
</blockquote></div>
</div>