path: root/djangoproject/templates/conduct/reporting.html

{% extends "conduct/base.html" %}
{% load i18n %}

{% block title %}{% translate "Django Code of Conduct - Reporting Guide" %}{% endblock %}

{% block og_title %}{% translate "Django Code of Conduct - Reporting Guide" %}{% endblock %}
{% block og_description %}{% translate "A guide to reporting issues in the community" %}{% endblock %}

{% block content %}
  <h1>{% translate "Django Code of Conduct - Reporting Guide" %}</h1>

  <p>
    {% blocktranslate trimmed %}
      If you believe someone is violating the code of conduct we ask that you report
      it to the Django Software Foundation by emailing <a
        href="mailto:conduct@djangoproject.com">conduct@djangoproject.com</a>.
      <strong>All reports will be kept confidential.</strong> In some cases we may
      determine that a public statement will need to be made. If that's the case, the
      identities of all victims and reporters will remain confidential unless those
      individuals instruct us otherwise.{% endblocktranslate %}</p>

  <p>
    {% blocktranslate trimmed %}
      <strong>If you believe anyone is in physical danger, please notify appropriate
        law enforcement first.</strong> If you are unsure what law enforcement agency is
      appropriate, please include this in your report and we will attempt to notify
      them.{% endblocktranslate %}</p>

  <h2 id="when-to-report">{% translate "Understanding When to Report" %} <a class="plink" href="#when-to-report">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      Not every conflict or disagreement represents a Code of Conduct violation.
      Tensions can occur between community members even when they are trying their best
      to collaborate in good faith. Differences of opinion, technical disagreements, and
      communication challenges are normal parts of working together. However, violations
      often occur in how we respond to these disagreements. It's acceptable to question
      the merit of a technical decision, but it's not acceptable to question the merit
      or value of the people who made that decision.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      If you are unsure whether an incident is a violation, or whether the space where
      it happened is covered by this Code of Conduct, we encourage you to still report
      it. We would much rather have a few extra reports where we decide to take no
      action, rather than miss a report of an actual violation. We do not look
      negatively on you if we find the incident is not a violation. And knowing about
      incidents that are not violations, or happen outside our spaces, can also help us
      to improve the Code of Conduct or the processes surrounding it.
    {% endblocktranslate %}
  </p>

  <h2 id="who-can-report">{% translate "Who Can Report" %} <a class="plink" href="#who-can-report">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      You do not need to be directly affected by an incident to report it. If you
      witness or become aware of behavior that violates the Code of Conduct, we
      encourage you to report it, even if you were not the target of the behavior.
    {% endblocktranslate %}
  </p>

  <h2 id="language-accessibility">{% translate "Language Accessibility" %} <a class="plink" href="#language-accessibility">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      While reports can be submitted in any language, please note that the working
      group primarily operates in English. If you use translation tools to prepare your
      report, please let us know so we can keep that in mind during our evaluation. We
      will make every effort to work with reports submitted in any language.
    {% endblocktranslate %}
  </p>

  <h2 id="what-to-include">{% translate "What to Include in Your Report" %} <a class="plink" href="#what-to-include">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      In your report please include:
    {% endblocktranslate %}
  </p>

  <ul>
    <li>{% translate "Your contact information (so we can get in touch with you if we need to follow up)" %}</li>
    <li>{% translate "Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well." %}</li>
    <li>{% translate "When and where the incident occurred. Please be as specific as possible." %}</li>
    <li>{% translate "Your account of what occurred. If there is a publicly available record (e.g. a forum post) please include a link." %}</li>
    <li>{% translate "Any extra context you believe existed for the incident." %}</li>
    <li>{% translate "If you believe this incident is ongoing." %}</li>
    <li>{% translate "Any other information you believe we should have." %}</li>
  </ul>

  <h2 id="confidentiality-privacy">{% translate "Confidentiality and Privacy" %} <a class="plink" href="#confidentiality-privacy">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      The working group is committed to protecting your privacy and the privacy of all
      individuals involved in Code of Conduct matters.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      Reports and the identity of reporters will be kept confidential to the extent
      possible. The working group will not share reporter identities with the reported
      party. However, in some situations, context may allow individuals to infer who
      made a report.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      Personal information is:
    {% endblocktranslate %}
  </p>

  <ul>
    <li>{% translate "Stored securely with access limited to working group members handling the specific report" %}</li>
    <li>{% translate "Used only for the purpose of investigating and resolving reports" %}</li>
    <li>{% translate "Retained in accordance with the Django Software Foundation's data retention policies and applicable privacy laws" %}</li>
    <li>{% translate "Protected in accordance with applicable data protection regulations" %}</li>
  </ul>

  <p>
    {% blocktranslate trimmed %}
      For details on how records are maintained, see the <a href="#record-keeping">Record
        Keeping section</a> below.
    {% endblocktranslate %}
  </p>

  <h2 id="protection-from-retaliation">{% translate "Protection from Retaliation" %} <a class="plink" href="#protection-from-retaliation">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      Retaliation against anyone who reports a concern in good faith is itself a
      violation of this Code of Conduct and will be treated seriously. If you
      experience retaliation after making a report, please report that as well.
    {% endblocktranslate %}
  </p>

  <h2 id="after-filing">{% translate "What Happens After You File a Report?" %} <a class="plink" href="#after-filing">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      You will receive an email from the DSF Code of Conduct Working Group
      acknowledging receipt. The working group strives to respond promptly, recognizing
      that as volunteers, coordination may take time. The working group will keep you
      informed of progress and any delays.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      The working group will immediately meet to review the incident and determine:
    {% endblocktranslate %}
  </p>

  <ul>
    <li>{% translate "What happened." %}</li>
    <li>{% translate "Whether this event constitutes a Code of Conduct violation." %}</li>
    <li>{% translate "Who was responsible for the behavior." %}</li>
    <li>{% translate "Whether this is an ongoing situation, or if there is a threat to anyone's physical safety." %}</li>
  </ul>

  <p>
    {% blocktranslate trimmed %}
      If this is determined to be an ongoing incident or a threat to physical safety,
      the working group's immediate priority will be to protect everyone involved. This
      means we may delay an "official" response until we believe that the situation has
      ended and that everyone is physically safe.
    {% endblocktranslate %}
  </p>

  <h3 id="ongoing-incidents">{% translate "Ongoing Incidents and Immediate Action" %} <a class="plink" href="#ongoing-incidents">#</a></h3>

  <p>
    {% blocktranslate trimmed %}
      Examples of ongoing incidents include: someone continuing to engage in harassment
      on a forum, persistent unwelcome contact, or any situation where harmful behavior
      is actively continuing.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      For ongoing situations or threats to safety, working group members may act
      immediately (before reaching consensus) to protect community members. This can
      include temporarily restricting someone's access to certain spaces or requiring
      they avoid contact with specific individuals. See our <a href="https://github.com/django/code-of-conduct/blob/main/working-group-manual.md#acting-unilaterally">Working
        Group Manual</a> for more details on how we handle urgent situations.
    {% endblocktranslate %}
  </p>

  <h3 id="investigation-resolution">{% translate "Investigation and Resolution" %} <a class="plink" href="#investigation-resolution">#</a></h3>

  <p>
    {% blocktranslate trimmed %}
      The working group aims to have an initial response to you within one week of
      receiving your report, though we recognize that complex cases may take longer.
      We will keep you informed throughout the investigation process.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      The working group must agree on a resolution by consensus. If the working group
      cannot reach consensus within a reasonable timeframe, the working group will turn
      the matter over to the board for resolution.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      Once the working group has a complete account of the events, they will make a
      decision as to how to respond using our <a href="https://github.com/django/code-of-conduct/blob/main/enforcement-ladder.md">Enforcement
        Ladder</a>. The enforcement ladder includes responses ranging from warnings to
      permanent bans, with the goal of repairing harm while considering the incident's
      impact on individuals and the community. Depending on the severity of a violation,
      lower levels may be skipped.
    {% endblocktranslate %}
  </p>

  <h3 id="resolution-input">{% translate "Your Input on the Resolution" %} <a class="plink" href="#resolution-input">#</a></h3>

  <p>
    {% blocktranslate trimmed %}
      Once a resolution is agreed upon, but before it is enacted, the working group will
      contact you and any other affected parties to explain the proposed resolution.
      The working group will ask if this resolution is acceptable, and will note your
      feedback for the record.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      However, the working group is not required to act on this feedback. The final
      decision rests with the working group, using their best judgment to balance the
      needs of the affected parties with the safety and health of the broader community.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      Once we've determined our final action, we'll contact you to let you know what
      action (if any) we'll be taking.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      Finally, the Working Group will make a report on the situation to the DSF board.
      The board may choose to issue a public report of the incident.
    {% endblocktranslate %}
  </p>

  <h2 id="reporting-member">{% translate "If Your Report Concerns a Code of Conduct Working Group Member" %} <a class="plink" href="#reporting-member">#</a></h2>

  <h3 id="conflicts-of-interest">{% translate "Conflicts of Interest" %} <a class="plink" href="#conflicts-of-interest">#</a></h3>

  <p>
    {% blocktrans trimmed %}
      Any member of the working group must immediately notify the other members in
      writing (by disclosure on the report email thread) and recuse themselves from
      handling a report if they:
    {% endblocktrans %}
  </p>

  <ul>
    <li>{% translate "Are involved in the incident itself" %}</li>
    <li>{% translate "Have a personal relationship with any involved party" %}</li>
    <li>{% translate "Work for the same employer as an involved party" %}</li>
    <li>{% translate "Have access to private information that could bias their judgment" %}</li>
    <li>{% translate "Have any other conflict of interest that could affect their impartiality" %}</li>
  </ul>

  <p>
    {% blocktranslate trimmed %}
      If your report concerns a current member of the Code of Conduct working group,
      you may not feel comfortable sending your report to the working group, as all
      members will see the report.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      In that case, you can make a report directly to any or all of the current chairs
      of the Code of Conduct working group. Their email addresses are listed on the
      <a href="{% url 'members:teams' %}#code-of-conduct-team">Code of Conduct working
        group</a> page. The chairs will follow the usual enforcement process with the
      other members, but will exclude the member(s) that the report concerns from any
      discussion or decision making.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      If your report concerns all current chairs of the working group, please send your
      report directly to the DSF board at
      <a href="mailto:foundation@djangoproject.com">foundation@djangoproject.com</a>
      instead.
    {% endblocktranslate %}
  </p>

  <h2 id="reconsideration">{% translate "Reconsideration" %} <a class="plink" href="#reconsideration">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      Any of the parties directly involved or affected can request reconsideration of
      the working group's decision. To make such a request, contact the DSF Board at
      <a href="mailto:foundation@djangoproject.com">foundation@djangoproject.com</a>
      with your request and motivation and the DSF board will review the case.
    {% endblocktranslate %}
  </p>

  <h2 id="transparency">{% translate "Transparency and Public Accountability" %} <a class="plink" href="#transparency">#</a></h2>

  <p>
    {% blocktranslate trimmed %}
      The working group will never publicly discuss specific incidents. All public
      statements about individual Code of Conduct matters will be made by the DSF board,
      if deemed necessary.
    {% endblocktranslate %}
  </p>

  <p>
    {% blocktranslate trimmed %}
      However, to demonstrate that the Code of Conduct is being actively and fairly
      enforced, the working group will publish annual transparency reports including
      anonymized statistics such as:
    {% endblocktranslate %}
  </p>

  <ul>
    <li>{% translate "Number of reports received" %}</li>
    <li>{% translate "Types of violations reported" %}</li>
    <li>{% translate "General outcomes (warnings, suspensions, bans)" %}</li>
    <li>{% translate "Any trends or patterns observed" %}</li>
  </ul>

  <p>
    {% blocktranslate trimmed %}
      These reports will be prepared in a way that protects the confidentiality of all
      involved parties while providing community accountability.
    {% endblocktranslate %}
  </p>

  <h2 id="record-keeping">{% translate "Record Keeping" %} <a class="plink" href="#record-keeping">#</a></h2>

  <h3 id="record-retention">{% translate "Record Retention" %} <a class="plink" href="#record-retention">#</a></h3>

  <p>
    {% blocktranslate trimmed %}
      The working group maintains records of all information and communications related
      to incident reports, including:
    {% endblocktranslate %}
  </p>

  <ul>
    <li>{% translate "Initial reports and all communications with reporters" %}</li>
    <li>{% translate "Investigation materials and evidence" %}</li>
    <li>{% translate "Email discussions and documented deliberations" %}</li>
    <li>{% translate "Notes and key takeaways from meetings" %}</li>
    <li>{% translate "Decisions made in DSF Slack (recorded into meeting notes)" %}</li>
    <li>{% translate "Communications with all involved parties" %}</li>
    <li>{% translate "Final resolutions and any follow-up actions" %}</li>
  </ul>

  <p>
    {% blocktranslate trimmed %}
      Records are retained in accordance with the Django Software Foundation's data
      retention policies and applicable privacy laws.
    {% endblocktranslate %}
  </p>

  <h3 id="record-access">{% translate "Access to Records" %} <a class="plink" href="#record-access">#</a></h3>

  <p>
    {% blocktranslate trimmed %}
      All members of the working group involved in handling a specific incident report
      have access to all records related to that report. This ensures informed
      decision-making. The board may request access to records for oversight purposes.
    {% endblocktranslate %}
  </p>
{% endblock %}