summaryrefslogtreecommitdiff
path: root/docs/intro
diff options
context:
space:
mode:
authorLily Foote <code@lilyf.org>2025-04-27 14:54:05 +0100
committernessita <124304+nessita@users.noreply.github.com>2025-05-13 21:38:04 -0300
commit188799e67c2c497419f448359775930c866fe28d (patch)
treeaca9adc2ab6035d1fb1429777a48f6946b3c139b /docs/intro
parent96c79be4e436f0b3045421556a2253cbff4533dc (diff)
Updated guidance to propose new feature ideas in contributing docs.
These changes include: * Clarification of the new feature proposal and evaluation process. * Reodering "points to consider" into reporting bugs section, since these are mostly trac-specific. * Narrowing the guide on user interface bugs and features to just bugs. * Updating documentation for Someday/Maybe triage stage. Co-authored-by: Tim Schilling <schilling711@gmail.com> Co-authored-by: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> Co-authored-by: Natalia <124304+nessita@users.noreply.github.com>
Diffstat (limited to 'docs/intro')
-rw-r--r--docs/intro/contributing.txt11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt
index 6b3249b823..65789bdc78 100644
--- a/docs/intro/contributing.txt
+++ b/docs/intro/contributing.txt
@@ -7,7 +7,8 @@ Introduction
Interested in giving back to the community a little? Maybe you've found a bug
in Django that you'd like to see fixed, or maybe there's a small feature you
-want added.
+want added (but remember that proposals for new features should follow the
+:ref:`process for suggesting new features <requesting-features>`).
Contributing back to Django itself is the best way to see your own concerns
addressed. This may seem daunting at first, but it's a well-traveled path with
@@ -264,11 +265,11 @@ __ https://djangoci.com
<running-unit-tests-settings>`. When making UI changes, you will need to
:ref:`run the Selenium tests <running-selenium-tests>`.
-Working on a feature
-====================
+Working on an approved new feature
+==================================
-For this tutorial, we'll work on a "fake ticket" as a case study. Here are the
-imaginary details:
+For this tutorial, we'll work on a "fake accepted ticket" as a case study. Here
+are the imaginary details:
.. admonition:: Ticket #99999 -- Allow making toast