So I do not know much about codes of conduct. I know they're old hat but I don't have personal experience in interacting with them. Are there any "off-the-shelf" CoCs other than the Contributor Covenant I should be aware of? It seems like it's better to use one that's met with success elsewhere than to try to write your own but the Contributor Covenant is the only one I've heard of.
Community Participation Guidelines

Mozilla
@mhoye In your opinion is there an argument for using CPG over CC (or vice versa?)
@mcc Not really. I can nitpick, but the specific text of the CoC anyone picks is far less important than having a principled enforcement process, with teeth and a spine. The text is just velvet-rope crowd management, the actions of the people running enforcement are going to be where your real CoC is born and raised.
@mhoye @mcc this reminds me of something some said years ago… “culture isn’t what you support. It’s what you tolerate”.

@mcc I’ve heard of one other, but it’s Not Good™.

CC is great, but all codes are bad unless they’re actually enforced

@listrophy Is there, for example, some best practices one could read as a companion document to CC, if one were going to be responsible for enforcing CC and wanted to be sure they were doing it right?

@mcc the homepage has some resources: https://www.contributor-covenant.org under “Before You Adopt Contributor Covenant”

I personally don’t have experience using a code of conduct in OSS

Contributor Covenant | A Code of Conduct for Digital Communities

The most widely adopted code of conduct in open source.

@mcc I have found that it can be really valuable to assemble your own (standing on the shoulders of giants of course) because it tends to bring out the areas in an organization that actually are in dire need of a CoC.

@mcc There were a few, but it seems like they've mostly dropped off. If you don't have an existing community, just adopting CC is a good starting place. Otherwise, it's a much better idea to take parts you like from many projects codes of conduct to create something that works for everyone. Simply adopting an off-the-shelf code of conduct can create more conflict.

https://github.com/todogroup/opencodeofconduct and https://web.archive.org/web/20180707014644/http://citizencodeofconduct.org/ are two of the more well-known OTS attempts.

GitHub - todogroup/opencodeofconduct: An easy to reuse open source code of conduct template for communities.

An easy to reuse open source code of conduct template for communities. - GitHub - todogroup/opencodeofconduct: An easy to reuse open source code of conduct template for communities.

GitHub

@mcc

(from an open source perspective)

Ubuntu CoC used to be quite popular. It was one of the first major projects adopting a CoC. But it really shows its age, with the large focus on "meritocracy". Nevertheless, many others, such as the Django one, have taken inspiration from it.

Another one is the Citizen CoC: https://web.archive.org/web/20200330154000/http://citizencodeofconduct.org/

Imo, enforcement is much more important than what's actually in it. For example, Ubuntu Discourse is a great place thanks to the mods, not the CoC itself.

Citizen Code of Conduct | A project of Stumptown Syndicate

@mcc as part the oceanic Splatoon competitive community leadership team, I definitely was in over my head in trying to draft up a code of conduct. The Australian Smash leadership made a conduct panel and wrote up a code of conduct that we adopted to use for the Splatoon community. Their CoC itself used a more general FGC CoC as a basis, as outlined in their document: https://t.co/ycc2QXzRy4
Australian Smash Ultimate Code of Conduct

Google Docs
@mcc oops I forgot copying a twitter link does that. It links to this google doc in case you're wary about clicking links like that.
https://docs.google.com/document/d/1wIK9yXx0ET56b1E3c2nuQ7G_DVq7QS-KLS9oLyZSlMY/edit?usp=sharing
Australian Smash Ultimate Code of Conduct

Google Docs