mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-04-05 05:56:42 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #35908 - Retire django-developers and django-users mailing list

Browse Source
This commit is contained in:
Chaitanya Rahalkar 2024-11-14 08:51:38 +05:30
parent 299b072498
commit e3f868b218
No known key found for this signature in database
11 changed files with 32 additions and 98 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/faq/help.txt
View File

@ -21,7 +21,6 @@ Then, please post it in one of the following channels:
* The Django Forum section `"Using Django"`_. This is for web-based
discussions.
* The |django-users| mailing list. This is for email-based discussions.
* The `Django Discord server`_ for chat-based discussions.
* The `#django IRC channel`_ on the Libera.Chat IRC network. This is for
chat-based discussions. If you're new to IRC, see the `Libera.Chat
@ -40,20 +39,6 @@ your choice of words.
.. _message-does-not-appear-on-django-users:
Why hasn't my message appeared on *django-users*?
=================================================
|django-users| has a lot of subscribers. This is good for the community, as
it means many people are available to contribute answers to questions.
Unfortunately, it also means that |django-users| is an attractive target for
spammers.
In order to combat the spam problem, when you join the |django-users| mailing
list, we manually moderate the first message you send to the list. This means
that spammers get caught, but it also means that your first question to the
list might take a little longer to get answered. We apologize for any
inconvenience that this policy may cause.
Nobody answered my question! What should I do?
==============================================
@ -68,12 +53,6 @@ everybody that can help is busy.
You can also try asking on a different channel. But please don't post your
question in all three channels in quick succession.
You might notice we have a second mailing list, called |django-developers|.
This list is for discussion of the development of Django itself. Please don't
email support questions to this mailing list. Asking a tech support question
there is considered impolite, and you will likely be directed to ask on
|django-users|.
I think I've found a bug! What should I do?
===========================================

10
docs/internals/contributing/committing-code.txt
View File

@ -109,8 +109,8 @@ Django's Git repository:
discuss the situation with the team.
* For any medium-to-big changes, where "medium-to-big" is according to
your judgment, please bring things up on the `Django Forum`_ or
|django-developers| mailing list before making the change.
your judgment, please bring things up on the `Django Forum`_ before making
the change.
If you bring something up and nobody responds, please don't take that
to mean your idea is great and should be implemented immediately because
@ -227,14 +227,14 @@ When a mistaken commit is discovered, please follow these guidelines:
* If the original author can't be reached (within a reasonable amount
of time -- a day or so) and the problem is severe -- crashing bug,
major test failures, etc. -- then ask for objections on the `Django Forum`_
or |django-developers| mailing list then revert if there are none.
major test failures, etc. -- then ask for objections on the `Django Forum`_
then revert if there are none.
* If the problem is small (a feature commit after feature freeze,
say), wait it out.
* If there's a disagreement between the merger and the reverter-to-be then try
to work it out on the `Django Forum`_ or |django-developers| mailing list. If
to work it out on the `Django Forum`_. If
an agreement can't be reached then it should be put to a vote.
* If the commit introduced a confirmed, disclosed security

5
docs/internals/contributing/index.txt
View File

@ -26,11 +26,6 @@ a great ecosystem to work in:
place to ask and answer any questions related to installing, using, or
contributing to Django.
* Join the |django-users| mailing list and answer questions. This
mailing list has a huge audience, and we really want to maintain a
friendly and helpful atmosphere. If you're new to the Django community,
you should read the `posting guidelines`_.
* Join the `Django Discord server`_ or the `#django IRC channel`_ on
Libera.Chat to discuss and answer questions. By explaining Django to other
users, you're going to learn a lot about the framework yourself.

21
docs/internals/contributing/triaging-tickets.txt
View File

@ -308,12 +308,11 @@ A ticket can be resolved in a number of ways:
* wontfix
Used when someone decides that the request isn't appropriate for
consideration in Django. Sometimes a ticket is closed as "wontfix" with a
request for the reporter to start a discussion on the `Django Forum`_ or
|django-developers| mailing list if they feel differently from the
rationale provided by the person who closed the ticket. Other times, a
discussion precedes the decision to close a ticket. Always use the forum
or mailing list to get a consensus before reopening tickets closed as
"wontfix".
request for the reporter to start a discussion on the `Django Forum`_
if they feel differently from the rationale provided by the person who
closed the ticket. Other times, a discussion precedes the decision to
close a ticket. Always use the forum or mailing list to get a consensus
before reopening tickets closed as "wontfix".
* duplicate
Used when another ticket covers the same issue. By closing duplicate
@ -333,7 +332,7 @@ If you believe that the ticket was closed in error -- because you're
still having the issue, or it's popped up somewhere else, or the triagers have
made a mistake -- please reopen the ticket and provide further information.
Again, please do not reopen tickets that have been marked as "wontfix" and
bring the issue to the `Django Forum`_ or |django-developers| instead.
bring the issue to the `Django Forum`_ instead.
.. _how-can-i-help-with-triaging:
@ -354,7 +353,7 @@ Then, you can help out by:
* Closing "Unreviewed" tickets as "needsinfo" when the description is too
sparse to be actionable, or when they're feature requests requiring a
discussion on the `Django Forum`_ or |django-developers|.
discussion on the `Django Forum`_.
* Correcting the "Needs tests", "Needs documentation", or "Has patch"
flags for tickets where they are incorrectly set.
@ -372,7 +371,7 @@ Then, you can help out by:
reports about a particular part of Django, it may indicate we should
consider refactoring that part of the code. If a trend is emerging,
you should raise it for discussion (referencing the relevant tickets)
on the `Django Forum`_ or |django-developers|.
on the `Django Forum`_.
* Verify if solutions submitted by others are correct. If they are correct
and also contain appropriate documentation and tests then move them to the
@ -399,11 +398,11 @@ the ticket database:
review a patch that you submit.
* Please **don't** reverse a decision without posting a message to the
`Django Forum`_ or |django-developers| to find consensus.
`Django Forum`_ to find consensus.
* If you're unsure if you should be making a change, don't make the
change but instead leave a comment with your concerns on the ticket,
or post a message to the `Django Forum`_ or |django-developers|. It's okay to
or post a message to the `Django Forum`_. It's okay to
be unsure, but your input is still valuable.
.. _Trac: https://code.djangoproject.com/

12
docs/internals/contributing/writing-code/submitting-patches.txt
View File

@ -154,11 +154,11 @@ or introduces breaking changes.
The following are different approaches for gaining feedback from the community.
The Django Forum or django-developers mailing list
The Django Forum
--------------------------------------------------
You can propose a change on the `Django Forum`_ or |django-developers| mailing
list. You should explain the need for the change, go into details of the
You can propose a change on the `Django Forum`_.
You should explain the need for the change, go into details of the
approach and discuss alternatives.
Please include a link to such discussions in your contributions.
@ -175,8 +175,8 @@ third-party package first. You can iterate on the public API much faster, while
also validating the need for the feature.
Once this package becomes stable and there are clear benefits of incorporating
aspects into Django core, starting a discussion on the `Django Forum`_ or
|django-developers| mailing list would be the next step.
aspects into Django core, starting a discussion on the `Django Forum`_ would
be the next step.
Django Enhancement Proposal (DEP)
---------------------------------
@ -188,7 +188,7 @@ specifications of features, along with rationales. DEPs are also the primary
mechanism for proposing and collecting community input on major new features.
Before considering writing a DEP, it is recommended to first open a discussion
on the `Django Forum`_ or |django-developers| mailing list. This allows the
on the `Django Forum`_. This allows the
community to provide feedback and helps refine the proposal. Once the DEP is
ready the :ref:`Steering Council <steering-council>` votes on whether to accept
it.

4
docs/internals/howto-release-django.txt
View File

@ -128,9 +128,7 @@ permissions.
* Access to create a post in the `Django Forum - Announcements category
<https://forum.djangoproject.com/c/announcements/7>`_ and to send emails to
the following mailing lists:
* `django-users <https://groups.google.com/g/django-users/>`_
* `django-developers <https://groups.google.com/g/django-developers/>`_
* `django-announce <https://groups.google.com/g/django-announce/>`_
* Access to the ``django-security`` repo in GitHub. Among other things, this

33
docs/internals/mailing-lists.txt
View File

@ -28,33 +28,6 @@ There are several categories of discussion including:
In addition, Django has several official mailing lists on Google Groups that
are open to anyone.
.. _django-users-mailing-list:
``django-users``
================
.. note::
The `Using Django`_ category of the `official Forum`_ is now the preferred
venue for asking usage questions.
This is the right place if you are looking to ask any question regarding the
installation, usage, or debugging of Django.
.. note::
If it's the first time you send an email to this list, your email must be
accepted first so don't worry if :ref:`your message does not appear
<message-does-not-appear-on-django-users>` instantly.
* `django-users mailing archive`_
* `django-users subscription email address`_
* `django-users posting email`_
.. _django-users mailing archive: https://groups.google.com/g/django-users
.. _django-users subscription email address: mailto:django-users+subscribe@googlegroups.com
.. _django-users posting email: mailto:django-users@googlegroups.com
.. _django-developers-mailing-list:
``django-developers``
@ -71,12 +44,6 @@ Before asking a question about how to contribute, read
:doc:`/internals/contributing/index`. Many frequently asked questions are
answered there.
.. note::
Please make use of
:ref:`django-users mailing list <django-users-mailing-list>` if you want
to ask for tech support, doing so in this list is inappropriate.
* `django-developers mailing archive`_
* `django-developers subscription email address`_
* `django-developers posting email`_

16
docs/internals/organization.txt
View File

@ -215,8 +215,6 @@ who demonstrate:
Django ecosystem
- Reviewing pull requests and/or triaging Django project tickets
- Documentation, tutorials or blog posts
- Discussions about Django on the django-developers mailing list or the Django
Forum
- Running Django-related events or user groups
- A history of engagement with the direction and future of Django. This does
@ -230,8 +228,7 @@ works as follows:
#. The steering council directs one of its members to notify the Secretary of the
Django Software Foundation, in writing, of the triggering of the election,
and the condition which triggered it. The Secretary post to the appropriate
venue -- the |django-developers| mailing list and the `Django forum`_ to
announce the election and its timeline.
venue -- the `Django forum`_ to announce the election and its timeline.
#. As soon as the election is announced, the `DSF Board`_ begin a period of
voter registration. All `individual members of the DSF`_ are automatically
registered and need not explicitly register. All other persons who believe
@ -251,9 +248,9 @@ works as follows:
believes are registering in bad faith.
#. Registration of candidates close one week after it has opened. One week
after registration of candidates closes, the Secretary of the DSF publish
the roster of candidates to the |django-developers| mailing list and the
`Django forum`_, and the election begin. The DSF Board provide a voting form
accessible to registered voters, and is the custodian of the votes.
the roster of candidates to the `Django forum`_, and the election begin.
The DSF Board provide a voting form accessible to registered voters, and
is the custodian of the votes.
#. Voting is by secret ballot containing the roster of candidates, and any
relevant materials regarding the candidates, in a randomized order. Each
voter may vote for up to five candidates on the ballot.
@ -261,9 +258,8 @@ works as follows:
votes and produce a summary, including the total number of votes cast and
the number received by each candidate. This summary is ratified by a
majority vote of the DSF Board, then posted by the Secretary of the DSF to
the |django-developers| mailing list and the Django Forum. The five
candidates with the highest vote totals are immediately become the new
steering council.
the Django Forum. The five candidates with the highest vote totals are
immediately become the new steering council.
A member of the steering council may be removed by:

2
docs/intro/contributing.txt
View File

@ -41,7 +41,7 @@ so that it can be of use to the widest audience.
.. admonition:: Where to get help:
If you're having trouble going through this tutorial, please post a message
on the `Django Forum`_, |django-developers|, or drop by
on the `Django Forum`_, or drop by
`#django-dev on irc.libera.chat`__ to chat with other Django users who
might be able to help.

4
docs/intro/whatsnext.txt
View File

@ -123,8 +123,8 @@ ticket system and use your feedback to improve the documentation for everybody.
Note, however, that tickets should explicitly relate to the documentation,
rather than asking broad tech-support questions. If you need help with your
particular Django setup, try the |django-users| mailing list or the `#django
IRC channel`_ instead.
particular Django setup, try the Django Community page at https://www.djangoproject.com/community
instead.
.. _ticket system: https://code.djangoproject.com/
.. _#django IRC channel: https://web.libera.chat/#django

2
docs/ref/contrib/index.txt
View File

@ -138,4 +138,4 @@ Other add-ons
=============
If you have an idea for functionality to include in ``contrib``, let us know!
Code it up, and post it to the |django-users| mailing list.
Code it up, and post it to the Django forum at https://forum.djangoproject.com.