summaryrefslogtreecommitdiff
path: root/docs/internals/contributing
diff options
context:
space:
mode:
Diffstat (limited to 'docs/internals/contributing')
-rw-r--r--docs/internals/contributing/bugs-and-features.txt3
-rw-r--r--docs/internals/contributing/triaging-tickets.txt15
2 files changed, 14 insertions, 4 deletions
diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt
index 1f39a61595..4249424b69 100644
--- a/docs/internals/contributing/bugs-and-features.txt
+++ b/docs/internals/contributing/bugs-and-features.txt
@@ -27,6 +27,9 @@ Before reporting a bug on the `ticket tracker
* Don't reopen issues that have been marked "wontfix" without finding consensus
to do so on the `Django Forum`_.
+* Don't reopen issues that have been marked "needsnewfeatureprocess" without
+ shepherding an issue through the `new feature ideas`_ GitHub project.
+
* Don't use the ticket tracker for lengthy discussions, because they're
likely to get lost. If a particular ticket is controversial, please move the
discussion to the `Django Forum`_.
diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt
index 66f0cc661e..3ac720ebce 100644
--- a/docs/internals/contributing/triaging-tickets.txt
+++ b/docs/internals/contributing/triaging-tickets.txt
@@ -327,6 +327,11 @@ A ticket can be resolved in a number of ways:
close a ticket. Always use the forum to get a consensus before reopening
tickets closed as "wontfix".
+* needsnewfeatureprocess
+ Used when the ticket merits a new feature, which will need to get
+ community input and support.
+ See the :ref:`process for suggesting new features <requesting-features>`.
+
* duplicate
Used when another ticket covers the same issue. By closing duplicate
tickets, we keep all the discussion in one place, which helps
@@ -344,8 +349,10 @@ A ticket can be resolved in a number of ways:
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`_ instead.
+Again, please do not reopen tickets that have been marked as "wontfix" or
+"needsnewfeatureprocess". For "wontfix" tickets, bring the issue to the
+`Django Forum`_ instead. For "needsnewfeatureprocess" tickets, propose the
+feature through the :ref:`new features process <requesting-features>`.
.. _how-can-i-help-with-triaging:
@@ -361,8 +368,8 @@ reset page`_.
Then, you can help out by:
-* Closing "Unreviewed" tickets as "invalid", "worksforme", or "duplicate", or
- "wontfix".
+* Closing "Unreviewed" tickets as "invalid", "worksforme", "duplicate",
+ "wontfix", or "needsnewfeatureprocess".
* Closing "Unreviewed" tickets as "needsinfo" when the description is too
sparse to be actionable.