Opened 3 months ago
Last modified 9 days ago
#35908 assigned Cleanup/optimization
Retire django-developers and django-users mailing list
Reported by: | Thibaud Colas | Owned by: | Sarah Boyce |
---|---|---|---|
Component: | Documentation | Version: | 5.1 |
Severity: | Normal | Keywords: | community, docs, support, onboarding |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | 19141 build:success, | ||
Description (last modified by ) ¶
Following the forum thread (Proposal: retiring django-users and django-developers mailing lists), we can now move ahead with updating the developer documentation to remove or contextualize references to the django-developers and django-users mailing list.
There is a lot of content that needs removing, but in some cases it might make sense to replace the references to those mailing lists with a link to the Django Forum, or specific forum categories. Also worth noting the django-announce and django-updates mailing list are staying as-is.
Removal tasks ¶
- [ ] remove 2x mailing lists from the How to release Django docs
- [ ] Remove django-users from the FAQ - How do I do X
- [ ] Remove Why hasn't my message appeared on *django-users*? from the FAQ: Getting help
- [ ] Remove You might notice we have a second mailing list paragraph from the FAQ: Getting help
- [ ] Remove the 4x subscription and posting email addresses from Mailing lists and Forum
- [ ] Remove the django-users mention on the Contributing to Django index.
- [ ] Remove 4x mentions of django-developers from the Organization of the Django Project docs
- [ ] Remove 3x django-developers mentions on Comitting code
- [ ] Remove 6x django-developers mentions on Triaging tickets
- [ ] Remove 4x django-developers mentions on Submitting contributions
- [ ] Remove 1x django-developers mention from Writing your first contribution for Django
Rewrite tasks ¶
- [ ] Rewrite the Mailing lists and Forum explanations for django-users and django-developers to explain the mailing lists still exist and contain valuable history
- [ ] Replace the 4x django-users and django-developers mentions on Reporting bugs and requesting features to instead point to the forum
- [ ] Replace the django-users and IRC links on the What to read next with a link to the Django Community page
- [ ] Replace the django-users mention on contrib apps index with a link to the Django forum
Do nothing ¶
- Keep the
rst_epilog
references in the Sphinx config for now - Keep any references to the mailing lists in historical docs (for example old release notes)
According to the ticket's flags, the next step(s) to move this issue forward are:
- For anyone except the patch author to review the patch using the patch review checklist and either mark the ticket as "Ready for checkin" if everything looks good, or leave comments for improvement and mark the ticket as "Patch needs improvement".
Change History (11)
comment:1 by , 3 months ago
Description: | modified (diff) |
---|
comment:2 by , 3 months ago
Description: | modified (diff) |
---|
comment:3 by , 3 months ago
Description: | modified (diff) |
---|
comment:4 by , 3 months ago
Description: | modified (diff) |
---|
comment:5 by , 3 months ago
Description: | modified (diff) |
---|
comment:6 by , 3 months ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:7 by , 3 months ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:8 by , 3 months ago
Has patch: | set |
---|
comment:10 by , 3 months ago
Patch needs improvement: | set |
---|
comment:11 by , 9 days ago
Owner: | changed from | to
---|---|
Patch needs improvement: | unset |
Thank you for leading this discussion
I think adding the forum and discord to the
rst_epilog
is also something we should consider