3 ms·
Hm, I think I know some of the cases you're thinking of. (Specifically, GNU and Stack Overflow come to mind?) But don't you think these were (at least in part)
by veddox 7y ago
Hm, I think I know some of the cases you're thinking of. (Specifically, GNU and Stack Overflow come to mind?)
But don't you think these were (at least in part) only the visible outbreaks of conflicts that had already been simmering for a long time? If that is so, introducing an explicit governance/CoC may have been a long overdue step that ended up breaking some crockery, but only because it wasn't enacted early enough...
- scrollaway 7y agoThe general rule is that a project shouldn't need a code of conduct. A code of conduct outlines basic decency rules in which case, if it gets to the point that the project needs to be explicit about them to keep a good ambiance, that project has deeper seated issues. Codes of conduct are great when the etiquette is ambiguous. Open source projects are not one of those. When the users are in the wrong, you should be able to kick them out uncontroversially. And when the maintainers are in the wrong... They tend to ignore their own CoC anyway. Speaking from experience, I've tried contributing to a particular PSF project in the past, adding a feature to support a use case the maintainer did not like (supporting tab indent option in a code formatter), which was ignored and closed; and when I pointed out to the maintainer that his behaviour was in breach of the CoC, that too was ignored. What are you gonna do? In the end I had to fork the project.