Skip to content

affiliated-programs.md

Latest commit

 

History

History
131 lines (85 loc) · 6.91 KB

affiliated-programs.md

File metadata and controls

131 lines (85 loc) · 6.91 KB

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. Designate at least one named Code of Conduct point of contact and provide their individual email address (not a shared group address) to the Django Code of Conduct Working Group to keep on file
  3. Reach out to [email protected] and request to be added to the Django Code of Conduct's scope
  4. 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
  5. 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.

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.