summaryrefslogtreecommitdiff
path: root/docs/faq
diff options
context:
space:
mode:
authorCarlton Gibson <carlton.gibson@noumenal.es>2021-04-14 20:23:21 +0200
committerCarlton Gibson <carlton.gibson@noumenal.es>2021-04-15 17:16:22 +0200
commit99ea737a0fbc5c628f21389be9d563ad0ea05348 (patch)
tree8de595053689e6c7e547dc7382a2eff649262da5 /docs/faq
parent539d005aa5fb496f0a648a2385465eca06c604e9 (diff)
[3.2.x] Fixed #32652 -- Fixed links to new contributors FAQ.
Backport of e3e2276e6fe6fd77e4fbdeeb2a287288d31de3bb from main
Diffstat (limited to 'docs/faq')
-rw-r--r--docs/faq/contributing.txt16
1 files changed, 12 insertions, 4 deletions
diff --git a/docs/faq/contributing.txt b/docs/faq/contributing.txt
index 8d8eb2ded7..a65066307f 100644
--- a/docs/faq/contributing.txt
+++ b/docs/faq/contributing.txt
@@ -2,6 +2,8 @@
FAQ: Contributing code
======================
+.. _new-contributors-faq:
+
How can I get started contributing code to Django?
==================================================
@@ -79,10 +81,10 @@ people that will likely be affected by a given bug. Bugs that have the
potential to affect many people will generally get priority over those that
are edge cases.
-Another reason that bugs might be ignored for while is if the bug is a symptom
-of a larger problem. While we can spend time writing, testing and applying
-lots of little patches, sometimes the right solution is to rebuild. If a
-rebuild or refactor of a particular component has been proposed or is
+Another reason that a bug might be ignored for a while is if the bug is a
+symptom of a larger problem. While we can spend time writing, testing and
+applying lots of little patches, sometimes the right solution is to rebuild. If
+a rebuild or refactor of a particular component has been proposed or is
underway, you may find that bugs affecting that component will not get as much
attention. Again, this is a matter of prioritizing scarce resources. By
concentrating on the rebuild, we can close all the little bugs at once, and
@@ -97,3 +99,9 @@ entire community, instead of prioritizing the impact on one particular user.
This doesn't mean that we think your problem is unimportant -- just that in the
limited time we have available, we will always err on the side of making 10
people happy rather than making a single person happy.
+
+I'm sure my ticket is absolutely 100% perfect, can I mark it as "Ready For Checkin" myself?
+===========================================================================================
+
+Sorry, no. It's always better to get another set of eyes on a ticket. If
+you're having trouble getting that second set of eyes, see questions above.