Updating the Code of Conduct

Django Internals
1

Today the Code of Conduct Working Group is announcing our plan to adopt Contributor Covenant 3 as our new Code of Conduct. The group has been discussing for the past year how we might best update our CoC that hasn’t seen a change since 2014. When the Beeware Project announced its change to using the Contributor Covenant it inspired us that this could be the right starting point for Django as well.

Why do we think the Contributor Covenant is a good fit for us?

We’re going to embark on a multi-step process to gather feedback from the community via our Github Repo. We hope each step of this process will take approximately one month which follows the group’s regular meeting schedule, though if we need more time to incorporate feedback we will take it.

  1. Open a pull request to add new documentation to the CoC repo outlining procedures for making changes to policies and the CoC itself. Plan to merge by February 15.

  2. Open a pull request to update our Enforcement Manual, Reporting Guidelines, and FAQs. Plan to merge by March 15.

  3. Open a pull request to adopt the Contributor Covenant 3 with proposed changes from the working group. Plan to merge by April 15.

Currently the djangoproject.com GitHub repo has been the source of truth for many of our documents. We have recently made copies of all of these into our CoC repo and they will serve as the source of truth moving forward, though we will keep the website updated as well.

If you’re not comfortable using GitHub to make comments we also welcome feedback via conduct@djangoproject.com; reaching out to @coc in the DSF member Slack; or looking for anyone with the `Code of Conduct WG` role on Discord. We’re not all regularly active in the forum, though we will try to keep an eye out here as well.

4 Likes
Updating the Code of Conduct's process documentation
2

Thank you for doing this! This looks like a nice improvement.

Will the new CoC guidelines provide any guidance for sub-communities that rely on Django’s CoC reporting? For example, Djangonaut Space and Django Commons both have their own CoC reporting mechanisms, then point out that if a person wants to they can make a CoC report to Django.

I don’t know if standardization around that would be helpful or even desired. I guess, another topic would be “should these sub-groups have their own CoC processes?”

3

I think the approach is cumulative. Related spaces can and should have their own CoC and enforcement processes that may include the Django project CoC as well. There’s language in the Contributor Covenant guidelines for IRL events that I think applies here. We’ll make sure to make our guidance there broad enough to include our related communities.

1 Like