summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/new-contributors.txt
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2013-04-08 19:49:08 +0200
committerAymeric Augustin <aymeric.augustin@m4x.org>2013-04-08 20:33:52 +0200
commit4a7292df3be2338ff5d915a9ab3107067f662534 (patch)
treee30e4608f752d90d31693db16cf3e0275a79c916 /docs/internals/contributing/new-contributors.txt
parented576b69f9cc0202adbb82da778f1ff6036626b4 (diff)
Removed references to the DDN triage state.
Rephrased "How can I help with triaging?" a bit to reflect the current practice.
Diffstat (limited to 'docs/internals/contributing/new-contributors.txt')
-rw-r--r--docs/internals/contributing/new-contributors.txt9
1 files changed, 0 insertions, 9 deletions
diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt
index b752503248..0d4ad0cf3f 100644
--- a/docs/internals/contributing/new-contributors.txt
+++ b/docs/internals/contributing/new-contributors.txt
@@ -140,12 +140,3 @@ FAQ
Short answer: 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
question 1, above.
-
-3. **My ticket has been in DDN forever! What should I do?**
-
- Design Decision Needed requires consensus about the right solution. At the
- very least it needs consensus among the core developers, and ideally it has
- consensus from the community as well. The best way to accomplish this is to
- start a thread on the django-developers mailing list, and for very complex
- issues to start a wiki page summarizing the problem and the possible
- solutions.