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.
@cwebber I agree. I think that, similarly to how widespread use and discussion of FL/OSS licenses made coders consider the legal and social dimensions of code re/use, CoCs may also help force techies to consider their personal actions and inactions WRT inclusiveness. That is, at minimum if someone has a CoC, you know they at least thought about it, once. That's more than some ever did! :)
@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... ๐
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.
