Document how to subscribe to mailing lists without a Google account

[Unai Zalakain]

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

[Tim Graham]

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?

[Unai Zalakain]

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.

[Tim Graham]

Sure, I think something like docs/internals/mailing-lists.txt would be a useful addition.

[Unai Zalakain]

Working on it ;-)

BTW, I haven't found the way of changing the "Questions/Feedback" footer of Django's documentation pages (maybe is it embedded?). 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?

[Tim Graham]

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.

[Unai Zalakain]

What about making it link to the (future) mailing lists docs instead?

[Unai Zalakain]

​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.

If everything OK, I'll squash commits and make a pull request ;-)

[Tim Graham <timograham@…>]

In 3895d8899d7a01f2bdb1c206e45d8578a9739c91:

Fixed #21213 -- Added docs for Django's mailing lists.

Added docs/internals/mailing-lists.txt documenting the use of django's
mailing lists. All references across docs changed to point to this page.

The referencing makes use of substitution because there's no way to make
a :ref: link in a non-inline fashion in Sphinx. It also makes use of
rst_epilog Sphinx conf for making this substitutions across all the
docs.

[Tim Graham <timograham@…>]

In 54b04cc8e6e4ea3f40b6320afe7e8ecfa16a8651:

[1.6.x] Fixed #21213 -- Added docs for Django's mailing lists.

Added docs/internals/mailing-lists.txt documenting the use of django's
mailing lists. All references across docs changed to point to this page.

The referencing makes use of substitution because there's no way to make
a :ref: link in a non-inline fashion in Sphinx. It also makes use of
rst_epilog Sphinx conf for making this substitutions across all the
docs.

Backport of 3895d8899d from master