1. =============
    
  2. Mailing lists
    
  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 has several official mailing lists on Google Groups that are open to
    
  14. anyone.
    
  15. 
    
  16. .. _django-users-mailing-list:
    
  17. 
    
  18. ``django-users``
    
  19. ================
    
  20. 
    
  21. This is the right place if you are looking to ask any question regarding the
    
  22. installation, usage, or debugging of Django.
    
  23. 
    
  24. .. note::
    
  25. 
    
  26.     If it's the first time you send an email to this list, your email must be
    
  27.     accepted first so don't worry if :ref:`your message does not appear
    
  28.     <message-does-not-appear-on-django-users>` instantly.
    
  29. 
    
  30. * `django-users mailing archive`_
    
  31. * `django-users subscription email address`_
    
  32. * `django-users posting email`_
    
  33. 
    
  34. .. _django-users mailing archive: https://groups.google.com/g/django-users
    
  35. .. _django-users subscription email address: mailto:[email protected]
    
  36. .. _django-users posting email: mailto:[email protected]
    
  37. 
    
  38. .. _django-developers-mailing-list:
    
  39. 
    
  40. ``django-developers``
    
  41. =====================
    
  42. 
    
  43. The discussion about the development of Django itself takes place here.
    
  44. 
    
  45. Before asking a question about how to contribute, read
    
  46. :doc:`/internals/contributing/index`. Many frequently asked questions are
    
  47. answered there.
    
  48. 
    
  49. .. note::
    
  50. 
    
  51.     Please make use of
    
  52.     :ref:`django-users mailing list <django-users-mailing-list>` if you want
    
  53.     to ask for tech support, doing so in this list is inappropriate.
    
  54. 
    
  55. * `django-developers mailing archive`_
    
  56. * `django-developers subscription email address`_
    
  57. * `django-developers posting email`_
    
  58. 
    
  59. .. _django-developers mailing archive: https://groups.google.com/g/django-developers
    
  60. .. _django-developers subscription email address: mailto:[email protected]
    
  61. .. _django-developers posting email: mailto:[email protected]
    
  62. 
    
  63. .. _django-announce-mailing-list:
    
  64. 
    
  65. ``django-announce``
    
  66. ===================
    
  67. 
    
  68. A (very) low-traffic list for announcing :ref:`upcoming security releases
    
  69. <security-disclosure>`, new releases of Django, and security advisories.
    
  70. 
    
  71. * `django-announce mailing archive`_
    
  72. * `django-announce subscription email address`_
    
  73. * `django-announce posting email`_
    
  74. 
    
  75. .. _django-announce mailing archive: https://groups.google.com/g/django-announce
    
  76. .. _django-announce subscription email address: mailto:[email protected]
    
  77. .. _django-announce posting email: mailto:[email protected]
    
  78. 
    
  79. .. _django-updates-mailing-list:
    
  80. 
    
  81. ``django-updates``
    
  82. ==================
    
  83. 
    
  84. All the ticket updates are mailed automatically to this list, which is tracked
    
  85. by developers and interested community members.
    
  86. 
    
  87. * `django-updates mailing archive`_
    
  88. * `django-updates subscription email address`_
    
  89. * `django-updates posting email`_
    
  90. 
    
  91. .. _django-updates mailing archive: https://groups.google.com/g/django-updates
    
  92. .. _django-updates subscription email address: mailto:[email protected]
    
  93. .. _django-updates posting email: mailto:[email protected]