[Django] #21213: mailing lists subscriptions
Django
--------------------------+------------------------------------------------
Reporter: | Owner: unaizalakain
unaizalakain | Status: new
Type: Bug | Version: 1.5
Component: | Keywords: mailing list, subscription, google
Documentation | Has patch: 0
Severity: Normal | UI/UX: 0
Triage Stage: |
Unreviewed |
Easy pickings: 1 |
--------------------------+------------------------------------------------
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-user...@googlegroups.com }}}
- {{{ django-develo...@googlegroups.com }}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21213>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by timo):
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.5 => master
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
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?
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by unaizalakain):
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by timo):
Sure, I think something like `docs/internals/mailing-lists.txt` would be a
useful addition.
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:3>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by unaizalakain):
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-
us...@googlegroups.com" 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?
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by timo):
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by unaizalakain):
What about making it link to the (future) mailing lists docs instead?
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:6>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
* has_patch: 0 => 1
Comment:
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 ;-)
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:7>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"3895d8899d7a01f2bdb1c206e45d8578a9739c91"]:
{{{
#!CommitTicketReference repository=""
revision="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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:8>
Django
-------------------------------------+-------------------------------------
Reporter: unaizalakain | Owner:
Type: | unaizalakain
Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: mailing list, | Triage Stage: Accepted
subscription, google | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"54b04cc8e6e4ea3f40b6320afe7e8ecfa16a8651"]:
{{{
#!CommitTicketReference repository=""
revision="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
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21213#comment:9>