Django Code of Conduct - Changes

Change control process

We're (mostly) programmers, so we'll track changes to the code of conduct and associated documents the same way we track changes to code. All changes will proposed via a pull request to the repository on GitHub. Changes will be reviewed by the conduct committee first, and then sent to the DSF, the Django core team, and the Django community for comment. We'll hold a comment period of at least one week, and then each group will vote on the change using its normal process (a board for the DSF, a core dev vote for the core team). Approved changes will be merged, published, and noted below.

This only applies to material changes; changes that don't effect the intent (typo fixes, re-wordings, etc.) can be made immediately.

A complete list of changes can always be found on GitHub; major changes and releases are summarized below.


October 3, 2014
Revised text to clarify that behavior outside the community is a contributing factor to involvement in the Django community; and explicitly provided a non-exhaustive list of diversity groups we consider included under the policy.
July 31, 2013
Documents approved and officially published.
July 15, 2013
Added the reporting guide and enforcement manual. Final draft presented to the board and core membership for vote.
April 1, 2013
Initial "beta" release and public call for comments.
Back to Top