- Apply suggestions from code review
- Add guidance for location-relevant safety policies in events
- Add affiliated programs documentation and scope section
- Add escalation process for disagreements between CoC WG and Online Community WG
- 📝 make twitter reference more general
- Update membership.md
- Update README.md
- Update working-group-manual.md
- 📝 add reference to Djangonaut Space CoC referencing our CoC
- Rename conferences.md to events.md for broader scope
- Add transparency report guidelines for conference organizers
- 📝 document how to handle multi-person reports
- Add CODEOWNERS for CoC committee
- 📝 comment out statistics iframe because GitHub doesn't allow them; keep it around for the website�
- 📝 update statistics with a live embed
- 📝 clarify when reporting process may vary because a current CoC WG member is involved in the reported issue
- 📝 updated member terms to reflect decision from the February 2026 meeting
- Update docs with new tracking sheet columns and stats logic
- 📝 correcting some descriptions around reporting and statistics
- 📝 update statistics
- 📝 added 2023 statistics�
- 📝 updated FAQs
- 📝 change all references to committee to working group
- 📝 added 2024 and 2025 statistics
- 📝 consolidating working-group policies into a single manual
- 📝 reformatting markdown files
- 📝 add a common sources.md link to all docs
- 📝 update our membership docs
- 📝 update our conferences guidelines
- 📝 update our communications guidelines
- 📝 update changelog with recent changes and fix heading levels
- 📝 move Enforcement Ladder to its own file
- 📝 updates to reporting guide
- 📝 update the enforcement manual to align with Contributor Covenant 3, their recommended resources, and the lessons the working group has learned
- Use GitHub /contents/ API to create signed commits
- Use GitHub API via gh CLI to create signed commits
- Use gh cli instead of third-party action for PR creation
- Change changelog workflow to create PR instead of direct push
- Update issue template and updates
This document should be updated whenever a change is made after this documentation will be made public. This is to transparently show how and what changes to the documentation are made without forcing people through the experience of looking at commit log. This may also include summary of rationale behind a change.
- 📝 copied Enforcement Manual from djangoproject.com
- 📝 copied Reporting Guide from djangoproject.com
- 📝 copied CoC from djangoproject.com
- 📝 copied FAQs from djangoproject.com
- 📝 Updates ordering
- Update membership.md
- 📝 Updates last updated date on stats
- 📝 Updates name
- 💎 Updates changelog
- 📝 Updates membership
- 📝 Updates stats for 2017 in progress
- Update membership.md
- Move TODO from docs into issue #26
- Adding few more internal links
- Re #20 Fix typo; neutral gender.
- Re #20 first draft communications guidelines
- Re #8 adding case-closure actions.
- Proofing. NB I have also changed the language of the initial response emails to convey why we appreciate receiving reports.
- Re #20 Fix typo; neutral gender.
- Re #20 first draft communications guidelines
- Rewording information about data retention. Thanks @phalt
- Fix typos in contributing.md
- Fix #11 - Add contributing docs, changelog and improve readme
- Add membership length timetable
- Information what happens when someone leaks sensitive data
- Fixes #4 -- Add information about data retention and access
- Added shepherding
- Fix typos in contributing.md
- Fix #11 - Add contributing docs, changelog and improve readme
- Add membership length timetable
- Fix typos in contributing.md
- Fix #11 - Add contributing docs, changelog and improve readme
- Added shepherding
- Fix grammar in Transparency chapter
2016-05-26: Fixes #6 -- Add details about receiving reports, on-call duty and example initial responses
- Typos in grammar in receiving reports chapter