4 ms·
I think it's reasonable for large software projects to have Code of Conduct. When I'm working on something small with few collaborators, it's too much process.
by JMTQp8lwXL 7y ago
I think it's reasonable for large software projects to have Code of Conduct. When I'm working on something small with few collaborators, it's too much process.
"No Code of Conduct", to me, looks like what All Lives Matter is to Black Lives Matter, that is, a deflection from the actual problem.
I somewhat agree with the general 'Don't be a jerk' principle. It has its place. But it doesn't scale for large projects.
This problem is, it's too discretionary. It isn't an actual policy you can point to if someone to decides to become zealously sexist or homophobic in a software project -- things that I haven't encountered much, but if you're maintaining a project with 10,000+ stars and hundreds of contributors, maintainers sometimes have to wear a moderator hat.
- downerending 7y agoYou do have to moderate, but it's not clear that a CoC makes any difference. You have people that are chill, people that will take direction when they unintentionally are not, and assholes. A CoC doesn't help with any of that. When I read some of the rather hateful comments coming from the most ardent proponents of CoCs, I feel like something's really gone wrong with the project.
- JMTQp8lwXL 7y agoHaving a CoC ensures moderator actions (bans, etc) are applied evenly when communities grow so large, they need multiple moderators. People that violate CoCs probably don't care to read them anyways, but I don't think that's the primary purpose of such a document. I would speculate the author of "No Code of Conduct" hasn't hasn't ever had to confront the complexities of moderating a large group of people.