4 ms·
On average I've found projects with explicit CoC's to be more toxic than those projects without Coc's.
by tharne 5y ago
On average I've found projects with explicit CoC's to be more toxic than those projects without Coc's.
- worik 5y agoIt would be illuminating if you could back that up with examples
- throwaway19937 5y agoThis could be Berkson's paradox (https://en.wikipedia.org/wiki/Berkson%27s_paradox https://en.wikipedia.org/wiki/Berkson%27s_paradox) in action. Larger projects probably have more toxicity than smaller projects and are more likely to have a CoC. The result is that the two factors appear to be correlated even if they are independent variables.
- deleted 5y ago[deleted]
- zionic 5y agoWe’re almost there, I’ve blacklisted all OSS with CoC from our products/services. We’re down to the last 2, in house rewrites have replaced the rest with superior performing alternatives. I would normally support pushing our clean sheet rewrites MIT, but I need a license that prohibits the addition of CoC in all derivative/downstream/forks. In the mean time I’ll settle for a competitive advantage.
- blindmute 5y agoYou might find this entertaining https://github.com/domgetter/NCoC https://github.com/domgetter/NCoC
- School-Cotton 5y agoYou don’t use Linux?