mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-07 07:15:35 +00:00
Code Issues 32 Releases Wiki Activity

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

Browse Source 
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
This commit is contained in:
Unai Zalakain
2013-10-04 00:51:22 +02:00
committed by Tim Graham
parent 438f9edff6
commit 54b04cc8e6
18 changed files with 161 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/internals/contributing/triaging-tickets.txt
View File

@@ -308,9 +308,9 @@ A ticket can be resolved in a number of ways:
* wontfix
Used when a core developer decides that this request is not
appropriate for consideration in Django. This is usually chosen after
discussion in the `django-developers`_ mailing list. Feel free to
discussion in the |django-developers| mailing list. Feel free to
start or join in discussions of "wontfix" tickets on the
django-developers_ mailing list, but please do not reopen tickets
|django-developers| mailing list, but please do not reopen tickets
closed as "wontfix" by a :doc:`core developer</internals/committers>`.
* duplicate
@@ -331,7 +331,7 @@ If you believe that the ticket was closed in error -- because you're
still having the issue, or it's popped up somewhere else, or the triagers have
made a mistake -- please reopen the ticket and provide further information.
Again, please do not reopen tickets that have been marked as "wontfix" by core
developers and bring the issue to django-developers_ instead.
developers and bring the issue to |django-developers| instead.
.. _how-can-i-help-with-triaging:
@@ -355,7 +355,7 @@ Then, you can help out by:
* Closing "Unreviewed" tickets as "needsinfo" when the description is too
sparse to be actionnable, or when they're feature requests requiring a
discussion on `django-developers`_.
discussion on |django-developers|.
* Correcting the "Needs tests", "Needs documentation", or "Has patch"
flags for tickets where they are incorrectly set.
@@ -373,7 +373,7 @@ Then, you can help out by:
reports about a particular part of Django, it may indicate we should
consider refactoring that part of the code. If a trend is emerging,
you should raise it for discussion (referencing the relevant tickets)
on `django-developers`_.
on |django-developers|.
* Verify if patches submitted by other users are correct. If they are correct
and also contain appropriate documentation and tests then move them to the
@@ -405,15 +405,14 @@ the ticket database:
* Please **don't** reverse a decision that has been made by a :doc:`core
developer</internals/committers>`. If you disagree with a decision that
has been made, please post a message to `django-developers`_.
has been made, please post a message to |django-developers|.
* If you're unsure if you should be making a change, don't make the
change but instead leave a comment with your concerns on the ticket,
or post a message to `django-developers`_. It's okay to be unsure,
or post a message to |django-developers|. It's okay to be unsure,
but your input is still valuable.
.. _Trac: https://code.djangoproject.com/
.. _django-developers: http://groups.google.com/group/django-developers
.. _i18n branch: https://code.djangoproject.com/browser/django/branches/i18n
.. _`tags/releases`: https://code.djangoproject.com/browser/django/tags/releases
.. _`easy pickings`: https://code.djangoproject.com/query?status=!closed&easy=1