Just think of it like a license. If you publish code, you should stick a license on it, so it's clear if/how other people can use it. If you publish a project,

Just think of it like a license. If you publish code, you should stick a license on it, so it's clear if/how other people can use it. If you publish a project, you should stick a code of conduct on it, so if any assholes show up, you can link them to something as you tell them to go away. For most developers, these can be glanced at and ignored "yeah, BSD again, great" / "contributors covenant again, blah blah". Having things like this is basically a requirement for getting N>5 when N is the number of developers working on the project, so just pick something sane. I do find conversations about codes of conduct particularly exhausting, akin to GPLv2 vs GLPv3 licensing debates. And usually an excessive interest in these things is a red flag.