summaryrefslogtreecommitdiffstats
path: root/Doc/bugs.rst
diff options
context:
space:
mode:
authorZachary Ware <zachary.ware@gmail.com>2014-01-14 22:03:11 (GMT)
committerZachary Ware <zachary.ware@gmail.com>2014-01-14 22:03:11 (GMT)
commit71337cb28199c0cf6d90f54bc5559bc75159077f (patch)
tree00e8ded8135f5567df6a225f0d97d96e2d25cb16 /Doc/bugs.rst
parent9774ce0cabb0811b0eac146f0051787cf25ee76a (diff)
downloadcpython-71337cb28199c0cf6d90f54bc5559bc75159077f.zip
cpython-71337cb28199c0cf6d90f54bc5559bc75159077f.tar.gz
cpython-71337cb28199c0cf6d90f54bc5559bc75159077f.tar.bz2
Issue #20255: Update the about and bugs pages.
Diffstat (limited to 'Doc/bugs.rst')
-rw-r--r--Doc/bugs.rst30
1 files changed, 21 insertions, 9 deletions
diff --git a/Doc/bugs.rst b/Doc/bugs.rst
index 3785ccb..847c010 100644
--- a/Doc/bugs.rst
+++ b/Doc/bugs.rst
@@ -13,15 +13,17 @@ Documentation bugs
==================
If you find a bug in this documentation or would like to propose an improvement,
-please send an e-mail to docs@python.org describing the bug and where you found
-it. If you have a suggestion how to fix it, include that as well.
+please submit a bug report on the :ref:`tracker <using-the-tracker>`. If you
+have a suggestion how to fix it, include that as well.
-docs@python.org is a mailing list run by volunteers; your request will be
-noticed, even if it takes a while to be processed.
+If you're short on time, you can also email your bug report to docs@python.org.
+'docs@' is a mailing list run by volunteers; your request will be noticed,
+though it may take a while to be processed.
-Of course, if you want a more persistent record of your issue, you can use the
-issue tracker for documentation bugs as well.
+.. seealso::
+ `Documentation bugs`_ on the Python issue tracker
+.. _using-the-tracker:
Using the Python issue tracker
==============================
@@ -62,9 +64,6 @@ taken on the bug.
.. seealso::
- `Python Developer's Guide <http://docs.python.org/devguide/>`_
- Detailed description of the issue workflow and developers tools.
-
`How to Report Bugs Effectively <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_
Article which goes into some detail about how to create a useful bug report.
This describes what kind of information is useful and why it is useful.
@@ -73,3 +72,16 @@ taken on the bug.
Information about writing a good bug report. Some of this is specific to the
Mozilla project, but describes general good practices.
+
+Getting started contributing to Python yourself
+===============================================
+
+Beyond just reporting bugs that you find, you are also welcome to submit
+patches to fix them. You can find more information on how to get started
+patching Python in the `Python Developer's Guide`_. If you have questions,
+the `core-mentorship mailing list`_ is a friendly place to get answers to
+any and all questions pertaining to the process of fixing issues in Python.
+
+.. _Documentation bugs: http://bugs.python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity
+.. _Python Developer's Guide: http://docs.python.org/devguide/
+.. _core-mentorship mailing list: https://mail.python.org/mailman/listinfo/core-mentorship/