[IshKebab]

They go a bit further than that, for example the second result in Google for "open source code of conduct" is this one: https://www.contributor-covenant.org/version/2/0/code_of_con...

It includes things like:

* The use of sexualized language * insulting or derogatory comments * Other conduct which could reasonably be considered inappropriate in a professional setting

Obviously on the face of it these are extremely reasonable. The problem is that they are also extremely vague. Is it ok to say "fuck" in a comment? Or is that "sexualized language"? Can I say "this code is stupid" or is that too insulting? What if it isn't directed at anyone?

The fear is that there is a certain kind of person who loves picking people up over these sort of inconsequential rule ("social justice warriors"). For some reason they like to get into positions of power and then enforce petty rules.

I don't think that happens 99% of the time, but it does seem like CoCs encourage it and I've never seen evidence that extensive CoCs help so why bother? Just put a comment in your readme like you suggested - "CoC: Thou shalt not be an asshole."

[psv1]

Even if we agree with everything in your comment, the question is "Is the <1% of the time this happens a good enough reason the reject every project with a CoC?". Personally, I would answer no to this.

[username90]

CoC's are inherently political, they say something about the people you have to deal with when contributing to the project. If you like that kind of people you'd see a CoC as a positive, but if you don't like them then you'd avoid CoC's. I don't see why this is so hard to understand.