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 ncoghlan
Recipients brett.cannon, eli.bendersky, eric.araujo, ezio.melotti, ncoghlan, petri.lehtinen, pitrou, terry.reedy
Date 2011-11-23.00:16:45
SpamBayes Score 0.00027666643
Marked as misclassified No
Message-id <1322007406.02.0.207860052819.issue13455@psf.upfronthosting.co.za>
In-reply-to
Content
Documenting the tracker UI itself isn't the big issue - what is useful (and what I think Ezio is getting at) is having a single place where newcomers can get a better idea of how we *use* the tracker.

If someone just wants to report a bug, then sure, they shouldn't need to read the dev guide (so I disagree with the idea of making any significant changes to the bugs page in the docs), but making it easier for newcomers to learn the ropes is the main reason we have a devguide at all, so I'm definitely +1 on the general idea.

It would also give us a place to document the auto-linkification rules (similar to what was done recently for the post-commit hooks).
History
Date User Action Args
2011-11-23 00:16:46ncoghlansetrecipients: + ncoghlan, brett.cannon, terry.reedy, pitrou, ezio.melotti, eric.araujo, eli.bendersky, petri.lehtinen
2011-11-23 00:16:46ncoghlansetmessageid: <1322007406.02.0.207860052819.issue13455@psf.upfronthosting.co.za>
2011-11-23 00:16:45ncoghlanlinkissue13455 messages
2011-11-23 00:16:45ncoghlancreate