diff options
| author | AfiMaameDufie <afimaamedufie@gmail.com> | 2024-11-12 21:33:39 +0000 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2024-11-14 11:38:05 +0100 |
| commit | 0c2c33bc87beb26afd988c19a08e669c92bc41c6 (patch) | |
| tree | 1e51552e0dcbca4e09e18412d21d4a4ba20a736e | |
| parent | c387d86882817fe007e1b217e9f6bc62ff513693 (diff) | |
[5.1.x] Replaced message suggestions from IRC to Discord in contributing docs.
Backport of da2432cccae841f0d7629f17a5d79ec47ed7b7cb from main.
| -rw-r--r-- | docs/faq/contributing.txt | 6 | ||||
| -rw-r--r-- | docs/internals/contributing/index.txt | 1 | ||||
| -rw-r--r-- | docs/internals/contributing/new-contributors.txt | 7 |
3 files changed, 9 insertions, 5 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! ========================================================================== diff --git a/docs/internals/contributing/index.txt b/docs/internals/contributing/index.txt index 6e3fd948ee..b547e468b7 100644 --- a/docs/internals/contributing/index.txt +++ b/docs/internals/contributing/index.txt @@ -46,7 +46,6 @@ a great ecosystem to work in: .. _posting guidelines: https://code.djangoproject.com/wiki/UsingTheMailingList .. _#django IRC channel: https://web.libera.chat/#django -.. _#django-dev IRC channel: https://web.libera.chat/#django-dev .. _community page: https://www.djangoproject.com/community/ .. _Django Discord server: https://discord.gg/xcRH6mN4fa .. _Django forum: https://forum.djangoproject.com/ diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt index c728abccd6..201fe4afc2 100644 --- a/docs/internals/contributing/new-contributors.txt +++ b/docs/internals/contributing/new-contributors.txt @@ -128,8 +128,11 @@ Be cautious when marking things "Ready For Check-in" If you're really not certain if a ticket is ready, don't mark it as such. Leave a comment instead, letting others know your thoughts. If you're mostly certain, -but not completely certain, you might also try asking on IRC to see if someone -else can confirm your suspicions. +but not completely certain, you might also try asking on the +``#contributing-getting-started`` channel in the `Django Discord server`_ to +see if someone else can confirm your suspicions. + +.. _`Django Discord server`: https://discord.gg/xcRH6mN4fa Wait for feedback, and respond to feedback that you receive ----------------------------------------------------------- |