djangoproject/templates/conduct/changes.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39

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

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

{% block og_title %}{% translate "Django Code of Conduct - Changes" %}{% endblock %}
{% block og_description %}{% translate "Changes to the Code of Conduct" %}{% endblock %}

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

  <h2>{% translate "Change control process" %}</h2>

  <p>
    {% blocktranslate trimmed %}
      We're (mostly) programmers, so we'll track changes to the code of conduct and
      associated documents the same way we track changes to code. All changes will
      be proposed via a pull request to the
      <a href="https://github.com/django/code-of-conduct">Django Code of Conduct
        repository on GitHub</a>. Changes will be reviewed by the code of conduct
      working group first, and then sent to the DSF and the Django community for
      comment. We'll hold a comment period of at least one month. Changes to the Code
      of Conduct itself will be voted on by the DSF board; other documentation changes
      will be approved by the code of conduct working group. Approved changes will be
      merged, published, and noted in <a href="https://github.com/django/code-of-conduct/blob/main/CHANGELOG.md">
        our changelog</a>.{% endblocktranslate %}</p>

  <p>
    {% blocktranslate trimmed %}
      This only applies to material changes; changes that don't affect the intent
      (typo fixes, re-wordings, etc.) can be made immediately{% endblocktranslate %}</p>

  <p>
    {% blocktranslate trimmed %}
      A complete list of changes can always be found
      <a href="https://github.com/django/code-of-conduct/blob/main/CHANGELOG.md">on
        GitHub</a>.{% endblocktranslate %}</p>

{% endblock %}