<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I have many opinions about the topic of CoC but don't feel up for
getting into depth here.<br>
<br>
I like much of what I see from that Funkwhale adaptation. My
general concern for CoC in practice is that there's usually not
enough combination of methods for cutting off immediate harm ASAP
while also having restorative process focused on learning and
growth. Most of the time, subtle harms are allowed to continue for
too long and then after they get worse, punitive and threatening
actions are taken that cause people to get defensive and
everything leads to limits and bans. So, there is neither a truly
high-standard of healthy interactions being maintained nor an
effective learning and restoration process.<br>
<br>
I've given talks about this in the past, and I like this article:<br>
<a class="moz-txt-link-freetext" href="https://authenticengine.com/2016/adopting-a-code-of-conduct-is-an-adaptive-challenge-not-a-technical-one/">https://authenticengine.com/2016/adopting-a-code-of-conduct-is-an-adaptive-challenge-not-a-technical-one/</a><br>
<br>
And FWIW, I'm a co-author of both<br>
<a class="moz-txt-link-freetext" href="https://wiki.snowdrift.coop/community/conduct">https://wiki.snowdrift.coop/community/conduct</a><br>
and <a class="moz-txt-link-freetext" href="https://wiki.social.coop/wiki/Code_of_conduct">https://wiki.social.coop/wiki/Code_of_conduct</a></p>
<p>neither of which I feel is ideal but which bring up some other
approaches that some CoC are missing<br>
<br>
I'm working on a much longer-term project that will eventually
offer a different class of CoC and practices altogether but it's
not yet usable enough to discuss practically here.<br>
<br>
I would just urge the core ideas that:<br>
<br>
- tensions should be addressed sooner rather than later<br>
- tensions should be processed *privately* while following some
fair predetermined method<br>
- the goal should be to get everyone back to good standing and
continual learning and improvement *without* letting conduct
issues be noise that disrupts or distresses the community or turns
anyone off<br>
<br>
Some of this is technical, like it's unfortunately not possible
with email for me to make a mistake that upsets someone, see it,
edit and fix it. There's no editing with email. But I'll say
personally: if I ever say something that upsets anyone in any way,
I would like to know about it ASAP, discuss privately (with that
person or someone else who is facilitating), and figure out the
best way to fix/resolve things. I do NOT want minor issues to be
ignored nor to make lots of public noise. Clear up any tensions
while they are still subtle.<br>
<br>
I wish I could suggest a simple pop-in solution but it's not that
easy because of the interacting problems with mediocre
social-norms and mediocre communication moderation tools.<br>
<br>
All for now,<br>
Aaron<br>
</p>
<div class="moz-cite-prefix">On 7/11/25 7:41, Xavier Coadic wrote:<br>
</div>
<blockquote type="cite"
cite="mid:sGPThNigbP1vnSgQYaZZzE7eHL4QfUetH_Cbu8agKjwZMnispAT7jNp7plPRkMnK-UHN-79tpgZNSQHR5wZrMpIvLc_wCI4ONBzzbJl39zM=@protonmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
FunkWhale did a particular adaptation of this CoC / Contributor
Covenant that I find very inspiring<br>
<a href="https://www.funkwhale.audio/code-of-conduct/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.funkwhale.audio/code-of-conduct/</a><br>
<br>
<br>
<div
style="font-family: Arial, sans-serif; font-size: 14px; color: rgb(0, 0, 0);"><span>Xavier
Coadic<br>
</span></div>
<div><br>
</div>
<div><b><a title="https://xavcc.frama.io/"
href="https://xavcc.frama.io/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://xavcc.frama.io </a></b><br>
</div>
<div><br>
</div>
<br>
-------- Message d'origine --------<br>
Le 11 juil. 2025 à 16:19, Ben Cotton <
<a class="moz-txt-link-abbreviated" href="mailto:bcotton@funnelfiasco.com">bcotton@funnelfiasco.com</a>> a écrit :<br>
On Thu, Jul 10, 2025 at 9:09 PM Bradley M. Kuhn wrote: > >
I'm curious if folks have a particular CoC template that they
particularly > like and think would be good for copyleft-next?
> > I did some poking around and discussion with colleagues
well-versed in this > area, and frankly there is no clear
standard, and I don't think (other than > the HBR addendum)
that we should write our own from scratch. I'm generally in favor
of the Contributor Covenant (<a
href="https://www.contributor-covenant.org/),"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.contributor-covenant.org/),</a>
although it's been long enough since I had to think about it that
I don't remember any particular details of what I liked or
disliked about it. Fedora's "new" (it's been several years now)
code of conduct is largely based on it, with some modifications,
and it has served well. -- Ben Cotton (he/him)
TZ=America/Indiana/Indianapolis
_______________________________________________ next mailing list
<a class="moz-txt-link-abbreviated" href="mailto:next@lists.copyleft.org">next@lists.copyleft.org</a> <a
href="https://lists.copyleft.org/mailman/listinfo/next"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.copyleft.org/mailman/listinfo/next</a>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
next mailing list
<a class="moz-txt-link-abbreviated" href="mailto:next@lists.copyleft.org">next@lists.copyleft.org</a>
<a class="moz-txt-link-freetext" href="https://lists.copyleft.org/mailman/listinfo/next">https://lists.copyleft.org/mailman/listinfo/next</a>
</pre>
</blockquote>
</body>
</html>