summaryrefslogtreecommitdiff
path: root/docs/faq
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq')
-rw-r--r--docs/faq/contributing.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/faq/contributing.txt b/docs/faq/contributing.txt
index 71a6a7a476..d281ce8b75 100644
--- a/docs/faq/contributing.txt
+++ b/docs/faq/contributing.txt
@@ -53,8 +53,8 @@ To determine the right time, you need to keep an eye on the schedule. If you
post your message right before a release deadline, you're not likely to get the
sort of attention you require.
-Gentle IRC reminders can also work -- again, strategically timed if possible.
-During a bug sprint would be a very good time, for example.
+Gentle reminders in the ``#contributing-getting-started`` channel in the
+`Django Discord server`_ can work.
Another way to get traction is to pull several related tickets together. When
someone sits down to review a bug in an area they haven't touched for
@@ -68,6 +68,8 @@ issue over and over again. This sort of behavior will not gain you any
additional attention -- certainly not the attention that you need in order to
get your issue addressed.
+.. _`Django Discord server`: https://discord.gg/xcRH6mN4fa
+
But I've reminded you several times and you keep ignoring my contribution!
==========================================================================