blob: 4f8c54285dbdfc7f4d0b68ac6b361311d25c67c9 (
plain)
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
40
41
42
43
44
45
46
47
48
|
{% extends "diversity/base.html" %}
{% load date_format i18n %}
{% block title %}{% translate "Django Community Diversity Statement - Changes" %}{% endblock %}
{% block og_title %}{% translate "Django Community Diversity Statement - Changes" %}{% endblock %}
{% block content %}
<h1>{% translate "Django Community Diversity Statement - Changes" %}</h1>
<h2>{% translate "Change control process" %}</h2>
<p>
{% blocktranslate trimmed %}
We're (mostly) programmers, so we'll track changes to the diversity statement
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/djangoproject.com">djangoproject.com repository
on GitHub</a>. Changes will be reviewed by the membership first, and then
sent to the DSF and the Django community for comment.
We'll hold a comment period of at least one week, then the DSF board will vote on
the change. Approved changes will be merged, published, and noted below.
{% 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/djangoproject.com/commits/main/djangoproject/templates/diversity">on GitHub</a>;
major changes and releases are summarized below.
{% endblocktranslate %}
</p>
<h2>{% translate "Changelog" %}</h2>
<dl>
<dt>{% isodate "2015-06-16" %}</dt>
<dd><a href="https://github.com/django/djangoproject.com/commit/da5f784cf737c6d74c1233c3db3442732fd87d6d">
{% translate "Initial release" %}</a>.</dd>
</dl>
{% endblock %}
|