This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Mariatta
Recipients Mariatta, docs@python
Date 2019-07-17.17:42:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563385356.62.0.425073313065.issue37611@roundup.psfhosted.org>
In-reply-to
Content
On the left of docs.python.org, is a link to "Report a Bug", which takes you to "Dealing with Bugs" section (https://docs.python.org/3/bugs.html)

One of the first few paragraphs of the page is telling people that documentation bugs can be reported at the bug tracker, or if they're short on time, it can be emailed to docs@python.org. 

The next section is talking about "using issue tracker", and at the very bottom are two links to external resources about how to report bugs effectively and bug reporting guidelines.

1. It would be great if the guidelines are at the top, instead of the bottom.

2. It would be great if we provide our own set of guidelines, instead of linking to external resources.

I think the guidelines are especially important for people who opted to write an email instead of creating an issue in bpo. In bpo, user is kinda restricted/reminded to select a specific type/component, but writing email can be more freeform. The better email they write, the easier it is for us to respond to them.
History
Date User Action Args
2019-07-17 17:42:36Mariattasetrecipients: + Mariatta, docs@python
2019-07-17 17:42:36Mariattasetmessageid: <1563385356.62.0.425073313065.issue37611@roundup.psfhosted.org>
2019-07-17 17:42:36Mariattalinkissue37611 messages
2019-07-17 17:42:36Mariattacreate