Message148138
| Author |
petri.lehtinen |
| Recipients |
brett.cannon, eli.bendersky, eric.araujo, ezio.melotti, ncoghlan, petri.lehtinen, pitrou, terry.reedy |
| Date |
2011年11月22日.19:15:59 |
| SpamBayes Score |
9.501705e-05 |
| Marked as misclassified |
No |
| Message-id |
<1321989359.84.0.0441169740063.issue13455@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
It seems to me there's not that much text on how the tracker itself works. Only sections "Checking if a bug already exists" and "Reporting an issue" have this kind of information. The text in these sections seems to be mostly from http://docs.python.org/bugs.html, so it's not new content.
Other sections mostly deal with the way the tracker is used or should be used for the development of CPython.
I like the idea of this patch. As Antoine said, people usually know how to use web applications nowadays, so moving the info from http://docs.python.org/bugs.html to devguide (replacing it with a shorter description) sounds good. |
|