[Python-checkins] devguide: Placeholder for docs covering how to gain the Developer role on the tracker.

[brett.cannon]

brett.cannon pushed 250a8a8e79e6 to devguide:

http://hg.python.org/devguide/rev/250a8a8e79e6
changeset:   65:250a8a8e79e6
user:        Brett Cannon <brett at python.org>
date:        Sun Jan 09 17:14:36 2011 -0800
summary:
  Placeholder for docs covering how to gain the Developer role on the tracker.

files:
  devrole.rst
  helptriage.rst
  index.rst
  triage.rst

diff --git a/devrole.rst b/devrole.rst
new file mode 100644
--- /dev/null
+++ b/devrole.rst
@@ -0,0 +1,6 @@
+.. _devrole:
+
+Gaining the 'Developer' Role on the Issue Tracker
+=================================================
+
+XXX
diff --git a/index.rst b/index.rst
--- a/index.rst
+++ b/index.rst
@@ -11,7 +11,8 @@
    docquality
    silencewarnings
    fixingissues
-   helptriage
+   triage
+   devrole
 
 
 .. todolist::
@@ -39,8 +40,8 @@
     * Fixing issues found by the buildbots_
     * :ref:`silencewarnings`
     * :ref:`fixingissues`
-    * :ref:`helptriage`
-* `Gaining 'Developer' privileges for the issue tracker <XXX>`_
+    * :ref:`triage`
+* :ref:`devrole`
     * `Marking issues as languishing <XXX>`_
 * `Following Python's development <XXX>`_
 * `Gaining commit privileges <XXX>`_
diff --git a/helptriage.rst b/triage.rst
rename from helptriage.rst
rename to triage.rst
--- a/helptriage.rst
+++ b/triage.rst
@@ -1,4 +1,4 @@
-.. _helptriage:
+.. _triage:
 
 Helping Triage Issues
 =====================
@@ -31,9 +31,10 @@
 maintenance mode. And if the bug lacks a unit test that should end up in
 Python's test suite, having that written can be very helpful.
 
-This is all helpful as it allows triagers (i.e., people with Developer
-privileges on the issue tracker) to properly classify an issue so it
-can be handled by the right core developers in a timely fashion.
+This is all helpful as it allows triagers (i.e.,
+:ref:`people with the Developer role on the issue tracker <devrole>`) to
+properly classify an issue so it can be handled by the right core developers in
+a timely fashion.
 
 
 Patches
@@ -49,9 +50,9 @@
 * The proper documentation changes are included
 * The person is listed in ``Misc/ACKS``, either already or the patches add them
 
-Doing all of this allows core developers and triagers to more quickly look for
-subtle issues that only people with extensive experience working on Python's
-code base will notice.
+Doing all of this allows core developers and :ref:`triagers <devrole>` to more
+quickly look for subtle issues that only people with extensive experience
+working on Python's code base will notice.
 
 There is a complete list of `open issues with patches`_, although to make sure
 that someone has not already done the checklist above as it is possible the

--
Repository URL: http://hg.python.org/devguide