4 ms·
The Mozilla CoC seems to be oddly "oh, you'll figure it out". Not only am I fairly certain that doesn't work too well - see your "adult enough" argument - there
by groby_b 11y ago
The Mozilla CoC seems to be oddly "oh, you'll figure it out". Not only am I fairly certain that doesn't work too well - see your "adult enough" argument - there's also no way for Mozilla to know if it has any effect.
I'm looking more at something like the LLVM CoC[1], which specifies how exactly disagreement should be escalated, and how it'll be handled.
To me, that's a major point of a CoC - if you have a disagreement what proper behavior is, it's incredibly difficult to handle at the peer level. You need an escalation path. As you say, and as I alluded to above - you need someone to enforce those standards.
What does a CoC achieve? It sets a tone for the community, spells out what is considered unacceptable, how you can ask for help with unacceptable behavior, and what the consequences of unacceptable behavior are. Or at least the kind of CoC I refer to.
I completely agree that a generic feel-good document does nothing.
[1] http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218...
- rockdoe 11y agoI completely agree that a generic feel-good document does nothing. It shuts the people up who demand a CoC. (Not disagreeing with anything you said). If I get it correctly, the LLVM one (comparing to the Mozilla one) spells out more explicit examples of things that are not allowed, and provides a simpler/more clear resolution process. Interestingly the LLVM CoC points out both of these as things that are required to make it effective in practice.