summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code/submitting-patches.txt
diff options
context:
space:
mode:
authorSarah Boyce <42296566+sarahboyce@users.noreply.github.com>2025-02-05 13:11:35 +0100
committerSarah Boyce <42296566+sarahboyce@users.noreply.github.com>2025-02-19 12:16:20 +0100
commit463e87e249693d1fd810b925c2da2c71426929cf (patch)
tree72134c322df404460c191c441f89d4d7ca2e7c26 /docs/internals/contributing/writing-code/submitting-patches.txt
parent9b7944896d9e96c60fe609308d152c358effdd39 (diff)
[5.2.x] Fixed #35908 -- Retired the django-developers and django-users mailing lists.
Co-authored-by: Chaitanya Rahalkar <chaitanyarahalkar@squareup.com> Backport of 86493307f97b9795a74227b6af2d59a267160847 from main.
Diffstat (limited to 'docs/internals/contributing/writing-code/submitting-patches.txt')
-rw-r--r--docs/internals/contributing/writing-code/submitting-patches.txt20
1 files changed, 9 insertions, 11 deletions
diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt
index c3d0e1745f..424cc8b944 100644
--- a/docs/internals/contributing/writing-code/submitting-patches.txt
+++ b/docs/internals/contributing/writing-code/submitting-patches.txt
@@ -154,12 +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
-approach and discuss alternatives.
+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 +174,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,10 +187,9 @@ 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
-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.
+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.
Some examples of DEPs that have been approved and fully implemented: