#21213 closed Cleanup/optimization (fixed)
Document how to subscribe to mailing lists without a Google account
Reported by: | Unai Zalakain | Owned by: | Unai Zalakain |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | mailing list, subscription, google |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
Leaving the google-dependency as a matter for an other discussion, the way for non-google users to subscribe to this mailing lists should be made more clear in doc. The only way for non-google users to subscribe is by sending an email to:
django-users+subscribe@googlegroups.com
django-developers+subscribe@googlegroups.com
Change History (9)
comment:1 by , 11 years ago
Summary: | mailing lists subscriptions → Document how to subscribe to mailing lists without a Google account |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Bug → Cleanup/optimization |
Version: | 1.5 → master |
comment:2 by , 11 years ago
Yep, I was planning to submit a patch myself but I wanted to wait for some kind of feedback.
What do you think about creating a mailing list specific page instead of mentioning the django-users, django-developers and django-updates mailing lists directly on every single page? In this way, secondary information can be given without mentioning it on every single page.
comment:3 by , 11 years ago
Sure, I think something like docs/internals/mailing-lists.txt
would be a useful addition.
comment:4 by , 11 years ago
Working on it ;-)
BTW, I haven't found the way of changing the "Questions/Feedback" footer of Django's documentation pages (is it embedded maybe?). The thing is that pointing the "post a question" link directly to "mailto:django-users@…" would be the correct thing, now it is pointing to the same place that the "archives of the django-users mailing" link does.
Any thought about how could I make this change happen?
comment:5 by , 11 years ago
It's part of a separate repo: https://github.com/django/djangoproject.com
I'm a bit hesitant to make that change though since I believe you need to be a member of the group in order to post, so it may be confusing to new users to click on that link only to have their message rejected.
comment:7 by , 11 years ago
Has patch: | set |
---|
https://github.com/unaizalakain/django/compare/ticket_21213
Some notes:
- I added the django-announce mailing list
- I made use of substitution and rst_epilog because:
- Writing :ref:
django-core-mentorship <django-core-mentorship-mailing-list>
every time wasn't an option - Adding all mailing list substitution like .. |django-core-mentorship| replace:: :ref:
django-core-mentorship <django-core-mentorship-mailing-list>
to every file wasn't an option either.
- Writing :ref:
If everything OK, I'll squash commits and make a pull request ;-)
comment:8 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Were you planning to provide a patch since you assigned this to yourself? If not, could you indicate where in the docs you expected to see this info?