Django Community Diversity Statement - Changes
Change control process
We're (mostly) programmers, so we'll track changes to the diversity statement the same way we track changes to code. All changes will proposed via a pull request to the djangoproject.com repository on GitHub. Changes will be reviewed by the membership 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.
- Jun 16, 2015
- Initial release.