I am in general very pro code-of-conduct. Still, this call to build something better has interesting thoughts in it https://shiromarieke.github.io/coc.html
But I'm not sure what something better would be yet, so ATM I think having a CoC is best
As a note, my main hesitancy to post about anything considering on *iterating on* a code of conduct type design can be a dogwhistle for "CoCs are bad let's get rid of them"
I think CoCs have been a useful development. I do wonder if we can improve the design. I just don't know what that may be.
@cathal @cwebber I also agree.
I think comparing with licenses is a good approach.
Incidentally, I remember a time not too long ago when many developers were angry and annoyed about having to choose or respect licenses at all... which led things like the WTFPL.
I am not convinced this time has passed... ๐
@meff @cathal @cwebber Yes, they absolutely do.
But both also strive to define aspects of the community around a project, and both can be quite divisive because people have Opinions(tm), and both licenses and CoCs benefit from consideration and gradual improvements.
So there are many meta-things in common.
I think CoCs have been a good tool for moderators as how they should conduct their work rightfully and not be too arbitrary... but... Like for EULAs.. users doesn't really read them.
The best CoCs are short and simple.. the issues comes when they try to overreach or are unclear.
@HerraBRE @cathal More has been written on this before, especially by @brainwane http://crookedtimber.org/2015/04/10/codes-of-conduct-and-the-trade-offs-of-copyleft/
I once wrote about it too https://dustycloud.org/blog/code-of-copylefts/ but embarrassingly forgot that most of the ideas came from an in-person conversation with Sumana about her post. Oops..
At any rate it's good that this has been a thread about "how can we do these things better?" rather than "rawr down with CoCs"! In retrospect I really risked the latter especially with the post I started this thread with.