Should we adopt a code of conduct? If so, which one?

edit

Of the CoCs I've read so far, this most closely matches how Wireshark works (at least, how I experience how Wireshark works) and my personal notions of how the project should work. Askbot won't let you vote for your own answer, but this is the one I'm leaning toward.

I like this one's brevity, lack of repetition, and that it doesn't refer to what sounds like a formal management group ('community leaders', 'project maintainers').

I like the succinctness of the KDE CoC. It encourages working through misunderstandings or differing opinions. The Overview mentions that moderators will exercise the right to suspend those who don’t follow the CoC. I favor this one, but lack points to up vote.

This is used by quite a few organizations and projects, including the Linux Kernel.

Sonds like a good match.

I lack the score to vote on answers, but this is my preferred code of conduct of the options available at time of writing. It gives clear examples of acceptable and unacceptable conduct, and it details specific steps that will be taken to resolve conflicts and enforce the code.

The KDE CoC "feels" good, but it doesn't give any information about what can or will be done if someone violates it in a way that discussion alone doesn't resolve.

Does the Linux Foundation have a preference or recommendation, or do they leave it up to the individual projects to decide their own Code of Conduct, if any?

@Boolean263 The KDE CoC could definitely use clearer instructions for resolution. Maybe that's something we could add?

I think this would also be a good match, although not quite as good as the KDE one.

The golang document is also a good document and based on a version of a Contributor Covenant. I am inclined to start with the KDE CoC..