summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code
diff options
context:
space:
mode:
Diffstat (limited to 'docs/internals/contributing/writing-code')
-rw-r--r--docs/internals/contributing/writing-code/submitting-patches.txt27
1 files changed, 19 insertions, 8 deletions
diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt
index 424cc8b944..fe354a0ba1 100644
--- a/docs/internals/contributing/writing-code/submitting-patches.txt
+++ b/docs/internals/contributing/writing-code/submitting-patches.txt
@@ -36,7 +36,8 @@ and time availability), claim it by following these steps:
reset it using the `password reset page`_.
* If a ticket for this issue doesn't exist yet, create one in our
- `ticket tracker`_.
+ `ticket tracker`_. Remember that proposals for new features should follow
+ the :ref:`process for suggesting new features <requesting-features>`.
* If a ticket for this issue already exists, make sure nobody else has
claimed it. To do this, look at the "Owned by" section of the ticket.
@@ -154,11 +155,20 @@ or introduces breaking changes.
The following are different approaches for gaining feedback from the community.
+The new feature ideas tracker
+-----------------------------
+
+If you have an idea for a new feature, please create a new proposal (or join an
+existing discussion) following the :ref:`process for suggesting new features
+<requesting-features>`. You should explain the need for the change, go into
+details of the approach and discuss alternatives.
+
The Django Forum
----------------
-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.
+You can propose a change (that is not a new feature idea) 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.
@@ -174,8 +184,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`_ would be
-the next step.
+aspects into Django core, the next step is to propose its inclusion by
+following the :ref:`process for suggesting new features <requesting-features>`.
Django Enhancement Proposal (DEP)
---------------------------------
@@ -187,9 +197,10 @@ 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`_. 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.
+following the :ref:`process for suggesting new features <requesting-features>`.
+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: