Nick Coghlan <ncogh...@gmail.com> added the comment: 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). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13455> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
