Merge pull request #91 from django/docs/update-process-docs

Update the policy docs to align with Contributor Covenant 3

Author: dryan

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # What is django/code-of-conduct?
 
-This repository is used by Django Software Foundation Code of Conduct committee
-to transparently describe how the committee enforces the Code of Conduct for
+This repository is used by Django Software Foundation Code of Conduct Working Group
+to transparently describe how the working group enforces the Code of Conduct for
 Django community. It's our internal set of documentation with processes that
 drive our work that we decided to make public with an aim to:
 
@@ -21,7 +21,7 @@ While contributing ideas and feedback, please keep in mind that this is still
 our internal documentation, so suggesting concepts that work well for other
 communities may not directly translate to our work.
 
-### Changelog 
+### Changelog
 
 When submitting a pull request to suggest a change, make sure to also update
 our [change log](CHANGELOG.md).
@@ -30,5 +30,4 @@ our [change log](CHANGELOG.md).
 
 This repository is also under the [Django Code of
 Conduct](https://www.djangoproject.com/conduct/). By contributing to it, you
-agree to comply with it. 
-
+agree to comply with it.

README.md

@@ -3,43 +3,59 @@
 On 31st July 2013, [Django community adopted a Code of
 Conduct](https://www.djangoproject.com/weblog/2013/jul/31/django-adopts-code-of-conduct/).
 This documentation aims to transparently describe how the Django Code of Conduct
-committee enforces the Code of Conduct and how it all works behind the scenes. 
+Working Group enforces the Code of Conduct and how it all works behind the scenes.
 
 There is still a lot we're figuring out and learning as we go, so we don't
 consider this documentation to be finished or complete. However, we hope it's
 going to be useful base for other communities to not only adopt, but also
-implement and enforce the Code of Conduct.  
+implement and enforce the Code of Conduct.
 
-## Table of Contents
+**Note:** Within the scope of all the documents in this repository, any reference to the “working group” shall mean the "Code of Conduct Working Group", unless explicitly specified otherwise.
 
-- [Structure of membership in the committee](membership.md)
-- [Report handling procedure](reports.md)
-- [Communications guidelines](communications.md)
-- [Record-keeping](records.md)
-- [Support for conference organizers](conferences.md)
-- [Transparency](transparency.md)
-- [Statistics](statistics.md)
+## Documentation for the Community
+
+Public-facing documentation for community members:
+
+- [Reporting Guide](reporting-guide.md) - How to report Code of Conduct violations
+- [Enforcement Ladder](enforcement-ladder.md) - Overview of enforcement actions
+- [FAQ](faq.md) - Frequently asked questions about the Code of Conduct
+- [Support for Event Organizers](events.md) - How we support event organizers
+- [Support for Affiliated Programs](affiliated-programs.md) - How to become an affiliated program and transparency reporting requirements
+- [Transparency](transparency.md) - How we maintain transparency and accountability
+
+## Documentation for Working Group Members
+
+Internal procedures and guidelines:
+
+- [Working Group Manual](working-group-manual.md) - Complete internal manual covering:
+  - Report handling procedures
+  - Communications guidelines
+  - Record-keeping and confidentiality
+  - Evaluation criteria and enforcement
+- [Membership](membership.md) - Current and past working group members
+- [Statistics](statistics.md) - Aggregated data on reports and outcomes
 
 ## Other
 
 - [Contributing to this documentation](CONTRIBUTING.md)
 - [Change log](CHANGELOG.md)
+- [Sources](sources.md) - Documents and policies that inspired our approach
 
-## Related material
+## Related Material
 
 Here is how the Code of Conduct is presented on djangoproject.com:
 
 - [Content of the Django Code of Conduct](https://www.djangoproject.com/conduct/)
 - [Changes to the Code of Conduct contents](https://www.djangoproject.com/conduct/changes/)
 - [Django Code of Conduct - FAQ](https://www.djangoproject.com/conduct/faq/)
-- [List of Code of Conduct committee members](https://www.djangoproject.com/foundation/committees/#conduct)
+- [List of Code of Conduct working group members](https://www.djangoproject.com/foundation/committees/#conduct)
 - [Reporting Guide](https://www.djangoproject.com/conduct/reporting/)
 - [Enforcement Manual](https://www.djangoproject.com/conduct/enforcement-manual/)
 - [Django Software Foundation Code of Conduct requirement](https://www.djangoproject.com/foundation/code-of-conduct/)
 
+**Note:** The internal [Working Group Manual](working-group-manual.md) in this repository consolidates and expands upon the public enforcement manual with additional procedures and guidelines.
+
 ## License
 
 All content in this repository is licensed under a [Creative Commons
-Attribution](http://creativecommons.org/licenses/by/3.0/) license. 
-
-
+Attribution](http://creativecommons.org/licenses/by/3.0/) license.

affiliated-programs.md

@@ -0,0 +1,130 @@
+# Django Code of Conduct Support for Affiliated Programs and Communities
+
+The Django Code of Conduct Working Group can serve as an escalation point for Django-related projects and communities that maintain their own Code of Conduct processes.
+
+This document outlines the requirements for becoming an affiliated program or community, how the Django Code of Conduct Working Group supports affiliated programs, and transparency reporting guidelines.
+
+## Becoming an Affiliated Program or Community
+
+Django-related projects and spaces may ask to designate the Django Code of Conduct Working Group as an escalation point in their own Code of Conduct process. To do so, they must:
+
+1. Adopt their own complementary Code of Conduct
+2. Reach out to [conduct@djangoproject.com](mailto:conduct@djangoproject.com) and request to be added to the Django Code of Conduct's scope
+3. If approved, outline in their reporting procedures that reports may be escalated to the Django Code of Conduct Working Group in the following circumstances:
+   - The report concerns a member of the project's Code of Conduct Committee
+   - The project's Code of Conduct Committee has failed to respond to a report
+   - As a point of appeal within 30 days of the original decision
+4. Publish transparency reports at least annually (quarterly preferred) following the guidelines outlined in this document
+
+Upon approval of a request, the Django Code of Conduct Working Group will add the project or community to the list of affiliated projects and spaces in the [Code of Conduct's scope section](CODE_OF_CONDUCT.md#scope).
+
+## Working with the Django Code of Conduct Working Group
+
+### Initial Setup
+
+- When establishing your Code of Conduct process, you can reach out to us for guidance on creating effective reporting procedures and enforcement guidelines.
+- We can review your Code of Conduct documentation to ensure it clearly outlines how and when to escalate to the Django Code of Conduct Working Group.
+
+### Ongoing Operations
+
+- If you encounter a Code of Conduct violation that falls under the escalation criteria outlined in your procedures, you can escalate to the Django Code of Conduct Working Group.
+- We encourage you to keep records of all Code of Conduct incidents you handle, even those that don't require escalation. These records help create a comprehensive understanding of community safety across Django-related spaces.
+
+### Reporting to the Working Group
+
+Affiliated programs and communities are strongly encouraged to share summaries of Code of Conduct incidents they handle with the working group. While detailed private records should be maintained by your team, sharing incident summaries helps the Django Code of Conduct Working Group:
+
+- Maintain a central record of incidents across the Django ecosystem
+- Identify patterns that may require broader community attention
+- Better support all affiliated programs and communities
+- Ensure consistency in Code of Conduct enforcement across Django spaces
+
+Reports should include the date of the incident, a brief description of the facts, the actions taken, and the outcome. Names and identifiable information should only be included when necessary for escalation purposes.
+
+Upon receiving reports from an affiliated program or community, the working group will:
+
+- Confirm receipt of the reports
+- Review all reports
+- Assess whether any additional action from the working group is needed
+- Record all reports in the working group's records
+
+### Transparency Report Guidelines
+
+Publishing transparency reports is a critical step for building trust within your community and demonstrating that Code of Conduct issues are handled appropriately.
+
+Note that this is guidance for public-facing transparency reports. For operational purposes, affiliated programs should also keep private records of all reports and issues, which should be shared with the Django Code of Conduct Working Group as outlined above.
+
+#### When to release
+
+Affiliated programs and communities should publish transparency reports **at least annually**, though **quarterly reporting is preferred** for active communities.
+
+Regular reporting helps:
+
+- Reporters know that their reports are taken seriously
+- Community members see that Code of Conduct enforcement is an ongoing priority
+- Demonstrate accountability and build trust in the process
+- Track trends and improvements over time
+
+Reports should be released in a timely manner after the reporting period ends. Aim to publish within 30 days of the period's conclusion.
+
+#### How to publish
+
+Any official communication channel used with your community is appropriate for transparency reports. Examples include:
+
+- Official website or blog
+- Community newsletter or mailing list
+- Forum posts or announcements
+- GitHub repository (e.g., in a dedicated transparency or reports folder)
+
+Consider publishing in multiple channels to reach your entire community.
+
+#### What to include
+
+**General Information:**
+
+- The reporting period covered (e.g., "Q1 2026" or "January 1 - December 31, 2025")
+- Brief description of your Code of Conduct process and how to report issues
+- Who serves on your Code of Conduct Committee
+- How community members can find reporting information
+
+**Statistics:**
+
+- Number of reports received during the period
+- Status of each report (resolved, in progress, escalated)
+- General categories of violations (if any occurred)
+- Historical comparison (if available) to show trends over time
+
+**Process Information:**
+
+- Average response time to initial reports
+- Any improvements made to the Code of Conduct process during the period
+- Any escalations to the Django Code of Conduct Working Group (without identifying details)
+
+**Optional but Valuable:**
+
+- Results from community surveys about confidence in the reporting process
+- Changes or updates to your Code of Conduct or procedures
+- Educational initiatives or resources provided to the community
+
+#### What NOT to include
+
+- Names or any identifiable information about reporters or reported parties
+- Specific details that could allow community members to identify individuals involved
+- Private or sensitive communications
+- Details that could adversely affect any ongoing processes or legal matters
+- Information that could discourage future reports
+
+## Review and Renewal
+
+The Django Code of Conduct Working Group may periodically review affiliated program status to ensure:
+
+- The program continues to meet the affiliation requirements
+- Reporting procedures are being followed
+- Transparency reports are being published as expected
+- The relationship continues to serve both communities effectively
+
+Programs that are no longer active or that do not maintain their Code of Conduct processes may be removed from affiliated status.
+
+---
+
+Our documents and policies are adapted from and inspired by a number of [sources](sources.md).

communications.md

@@ -1,90 +1,3 @@
-:point_left: [Come back to index](README.md)
+# Django Code of Conduct - Communications Guidelines
 
-# Django Code of Conduct
-
-## Communications guidelines
-
-When communicating with reporters and subjects of the report, it's important to
-keep the following in mind:
-
-### Protect reporters
-
-* Protecting reporters is our first priority. Never forward communication or
-disclose identities of reporters outside of the code of conduct committee,
-without the express written permission of the person concerned.
-* If adding or removing people from the recipients list of an email thread, note
-the change at the top of the email, like this:
-
-  > [+ John]
-  > [- Eric]
-
-  this helps guard against someone accidentally sharing protected information
-  without being aware of the recipients. 
-
-### Communicate professionally
-
-* Different people will experience the same situation in different ways.
-Subjective or emotional language is easily misinterpreted or disputed, for
-example naming someone as thinking or feeling something. Instead, stick to
-observed facts.
-* Always cc conduct@djangoproject.com on communication, or forward replies that
-had the address removed.
-
-### Confronting subjects of reports
-
-* No matter how compelling the evidence, we need to give people who are subjects
-of reports some sort of "right of reply" before we finalise our decision. That
-doesn't mean we have to disclose details, or let them excuse their bad behavior -
-but we should engage them in a process, rather than just pronouncing a
-decision. If someone feels like they're engaged in a process, rather than just
-being railroaded, they're less likely to criticise the process after the fact.
-
-* We need to make sure we don't lose sight of the goal. The goal isn't "get them" -
-it's "make the community safer". It's a subtle point, but an important one,
-because it shapes some of the actions we might take.
-
-* To that end, one big piece of advice - don't underestimate just asking. If we
- ask problematic individuals not to attend Django events in future, rather than
- ban them, there's a good chance they'll just comply.
-
-
-### Sharing information about subjects of reports
-
-Going public, or telling others, is sometimes necessary when the community
-remains at risk after the actions we can take in private.
-
-When deciding to share information about a problematic individual, there's
-potential for claims of slander, libel, defamation of character and
-reputational damage. In serious cases we should seek legal advice. The
-following approaches mitigate this risk: 
-
-* We should do everything we can to get multiple corroboration of any complaint. 
-That enables us to do two things:
-
-	 1. Say "this is a pattern of behavior", not "this is one bad incident". This
-strengthens the case we can make for any action, because we're not
-"overreacting to one bad incident".
-	 2. Deflect the "blame" for reporting away from a specific reporter.
-
-* There's a difference between giving someone information, and telling them what
-to do. If we *told* event organizers "Don't invite this person", then we're the
-direct cause of any reputational damage they may suffer. If, however, we tell
-organizers that a person has been the subject of (1 or more) code of conduct
-complaints, relating to incidents x, y and z - but leave the decision as to
-whether they are banned/not invited up to the organizers - then the DSF has
-more legal cover, because all we're doing is providing information, not
-directing action.
-
-* Any information we communicate needs to be written down, not done over
-Skype/Hangout. If we tell community organizers about problem individuals, we
-need to email our response, and make sure we're very careful in our language so
-that it's perfectly clear that it's up to *them* what they choose to do with
-the information we give them.
-
-* We need to make sure we follow our process to the letter. Any claims made about
-"reckless behavior leading to loss of reputation" will hinge on whether we
-actually followed our own processes.
-
-----
-
-[Go to next chapter: Record-keeping](records.md) :point_right:
+**⚠️ DEPRECATED:** This document has been consolidated into the [Working Group Manual](working-group-manual.md#communications-guidelines).