|
|
|
|
|
by meowface
2058 days ago
|
|
I'd prefer to make the implicitness explicit, in that case: "if the project owners consider your behavior overly assholish, you may be blocked from contributing, and the owners will add a notice to a page documenting the sanction and rationale". This makes it clear upfront that it's inherently and deliberately subjective. Then people understand what the CoC is: the project owners just moderating the project as they see fit. This is basically what all open source projects have done since forever. If others read the public list of moderation actions and disagree with the project owners' enforcement behavior (it being too lax or too strict or otherwise unfair or wrong), they can choose not to participate. Trying to codify every possible violation into a set of explicit rules, or, worse, trying to codify good behavior, just leads to this sort of "you technically violated this part here" bludgeoning. |
|
I mean, that's basically a CoC-by-example. I don't really disagree with that modulo some surmountable reservations about giving too much attention to either bad actors or victims. Where I think this falls short is that, when spinning up a new project, you'd start with a blank page, so people _don't_ have the opportunity to determine whether they disagree with your moderation style until enough bad things have actually happened. Why not carry over your learnings from previous projects?