Here's what we have now:

As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of ability, ethnicity, gender, sexual orientation, sexual preferences, socioeconomic status, geographic location, or religion (or lack thereof).

This is Pantheon's:

In the interest of fostering an open and welcoming environment, we as community members, contributors, and maintainers pledge to making participation in Pantheon and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, sexual identity and orientation, socioeconomic status, or technical ability.

This is Lullabot's:

Employment opportunities at Lullabot are based upon one's qualifications and capabilities to perform the essential functions of a particular job and free from discrimination because of race, color, national origin, religion, sex, age, disability, citizenship status, genetic information, sexual orientation, gender identity, military status, or any other characteristic protected by law.

Can/should we take from these good examples and improve our own?

I'm not 100% sold on the weapons policy bit, it feels a little out of place between Unacceptable Behavior and Consequences of Unacceptable Behavior. Maybe we just move it somwehere else in the document?

There's a note in the code of conduct about an "organization's governing policies". We should make one.

[NOTE: Every organization's governing policies should dictate how you handle warnings and expulsions of community members. It is strongly recommended that you mention those policies here]

If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).

I have concerns about "permanent expulsion" from "the community" for "unacceptable behavior" without more careful consideration. The change below would make it specific to an event:

If a community member engages in unacceptable behavior at an event, the event organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event without warning (and without refund in the case of a paid event).

I'm okay with this section being limited to an event context, so let's start there and iterate.

Changes needed:

• make something similar that applies to both online and in-person contexts
• consequences in one context (online) may have results in another (in-person)
• specifically state that someone may be removed from any leadership positions (such as the PMC) and have privileges revoked (such as commit access on github).

If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link.

Was this written in the 90s? We should update this to be more appropriate and accurate for our community.

Also, since we've been making our own changes since this was forked from Django, we should update or remove this footer:

Revision 1.0, DRAFT, proposed March 2016 Reporting Guidelines derived from those of the Django Software Foundation.

GitHub lets us specify any branch we want as the default, and as of October 2020, now defaults to main as the default branch. This is part of a wider effort in technology to eliminate the use of terminology that has underlying references to slavery. See https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main

Suggestion:

• Rename master to main
• Set main as the default branch
• Update links, such as those in the README.md of core (backdrop/backdrop-issues#3632)

We use the [email protected] email address for a lot of things, and it's useful to have many people receive those emails so that various different tasks can get done more quickly and easily.

Reports of Code of Conduct violations, however, can be sensitive in nature, and should be sent only to a limited number of recipients, and only to members of the PMC, since the PMC is responsible for handling these reports.

I have created the email address [email protected]. An issue will be opened in the PMC queue to decide on official, permanent recipients of these messages.