Hella biased opinion: the Contributor Covenant is not a good CoC and people should stop using it.
Show this thread
-
I say my opinion is biased because I adapted a CoC years ago that leads with an enforcement process, and I've had IMMENSE success with it in communities, vs when I was using a Contributor Covenant-like CoC: https://github.com/WeAllJS/weallbehave/blob/latest/CODE_OF_CONDUCT.md …
Show this thread
Have you considered packaging this in a way that makes it easy for folks to use? I think most folks go for CC because it's there, and they're not sure of what else to reach for
-
-
There's literally a CLI tool: $ npx weallbehave > CODE_OF_CONDUCT.md It's just very hard to make any headway vs the Contributor Covenant because it has such a "blessed" position in the Github ecosystem.
-
Sorry, I didn't realize that this was a project for generating codes of conduct, I thought that link was to the CoC for a project you run just as an example. FWIW plenty of folks don't have NPM installed, and I wouldn't have ever found this if you hadn't mentioned it here
- 5 more replies
New conversation -
-
-
Really we should have something similar to https://choosealicense.com/ for codes of conduct. Both are things that every project needs, and both are things that are hard to have a full grasp on all the tradeoffs and their consequences
-
I’ve done a lot of training and consulting on this, and CoC and license adoption have way different needs. A checkbox approach tends to leave people very unprepared for enforcement, especially the governance aspects.
- 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.