Debian Codegraph @

docs/internals/mailing-lists.txt

raw
1 =======================
2 Mailing lists and Forum
3 =======================
4
5 .. Important::
6
7 Please report security issues **only** to
8 [email protected]. This is a private list only open to
9 long-time, highly trusted Django developers, and its archives are
10 not public. For further details, please see :doc:`our security
11 policies </internals/security>`.
12
13 Django Forum
14 ============
15
16 Django has an `official Forum`_ where you can input and ask questions.
17
18 There are several categories of discussion including:
19
20 * `Using Django`_: to ask any question regarding the installation, usage, or
21 debugging of Django.
22 * `Internals`_: for discussion of the development of Django itself.
23
24 .. note::
25
26 Before asking a question about how to contribute, read
27 :doc:`/internals/contributing/index`. Many frequently asked questions are
28 answered there.
29
30 .. _official Forum: https://forum.djangoproject.com
31 .. _Internals: https://forum.djangoproject.com/c/internals/5
32 .. _Using Django: https://forum.djangoproject.com/c/users/6
33
34 In addition, Django has several official mailing lists on Google Groups that
35 are open to anyone.
36
37 .. _django-announce-mailing-list:
38
39 ``django-announce``
40 ===================
41
42 A (very) low-traffic list for announcing :ref:`upcoming security releases
43 <security-disclosure>`, new releases of Django, and security advisories.
44
45 * `django-announce mailing archive`_
46 * `django-announce subscription email address`_
47 * `django-announce posting email`_
48
49 .. _django-announce mailing archive: https://groups.google.com/g/django-announce
50 .. _django-announce subscription email address: mailto:[email protected]
51 .. _django-announce posting email: mailto:[email protected]
52
53 .. _django-updates-mailing-list:
54
55 ``django-updates``
56 ==================
57
58 All the ticket updates are mailed automatically to this list, which is tracked
59 by developers and interested community members.
60
61 * `django-updates mailing archive`_
62 * `django-updates subscription email address`_
63 * `django-updates posting email`_
64
65 .. _django-updates mailing archive: https://groups.google.com/g/django-updates
66 .. _django-updates subscription email address: mailto:[email protected]
67 .. _django-updates posting email: mailto:[email protected]
68
69 Archived mailing lists
70 ======================
71
72 The following mailing lists are archived and no longer active. These are still
73 available as a historical resource.
74
75 .. _django-users-mailing-list:
76
77 ``django-users``
78 ----------------
79
80 .. note::
81
82 The `Using Django`_ category of the `official Forum`_ is now the preferred
83 venue for asking usage questions.
84
85 This was used for questions regarding the installation, usage, or debugging of
86 Django projects.
87
88 * `django-users mailing archive`_
89
90 .. _django-users mailing archive: https://groups.google.com/g/django-users
91
92 .. _django-developers-mailing-list:
93
94 ``django-developers``
95 ---------------------
96
97 .. note::
98
99 The `Internals`_ category of the `official Forum`_ is now the preferred
100 venue for discussing the development of Django.
101
102 This was used for discussions about the development of Django itself.
103
104 * `django-developers mailing archive`_
105
106 .. _django-developers mailing archive: https://groups.google.com/g/django-developers