Title Add 'website' component to report issues
Priority feature Status resolved
Superseder Nosy List eric.araujo, ezio.melotti, techtonik, yaniv.aknin
Assigned To Topics

Created on 2010-06-02.11:58:50 by yaniv.aknin, last changed 2010-10-29.06:52:00 by loewis.

msg1667 (view) Author: yaniv.aknin Date: 2010-06-02.11:58:49
The topic says it all; I believe just like we have a 'documentation' component we should have a 'website' component to allow bugs/patches to be reported against itself (especially the development documents, but maybe not just).
msg1668 (view) Author: techtonik Date: 2010-06-02.15:44:17 - for now the last entry in Miscellaneous. I've put it on hold, because Rich Leland proposed to make a research of pydotorg infrastructure and present a proposal for improvement. The full research is planned to be presented in two weeks.
msg1669 (view) Author: techtonik Date: 2010-06-02.17:02:02
Given that supporting yet another Roundup tracker takes too much energy (due to badly defined and outdated process), I wonder if we could/should use Google Code (or any other tracker) for this purpose.
msg1756 (view) Author: ezio.melotti Date: 2010-08-01.02:46:18
The website doesn't have a bug tracker, and I'm not sure it needs one (are there really so many reports about it?). says "To report a bug or to suggest an enhancement, send an e-mail to <>.".
FWIW there are plans to move the dev docs to, to make it easier to maintain. Once that is done it will be possible to file documentation issues in the normal bug tracker (and also contribute patches more easily).
msg1811 (view) Author: eric.araujo Date: 2010-10-29.02:02:48
The rule of thumb is that the bug tracker collect reports for things that are shipped in a CPython distribution.  There is a documentation component not because there is but because there is a Doc directory in source distributions.  Mailing lists are used for website bugs and improvements, as Ezio reminded.  Suggest closing this.
Date User Action Args
2010-10-29 06:52:00loewissetstatus: chatting -> resolved
2010-10-29 02:02:49eric.araujosetnosy: + eric.araujo
messages: + msg1811
2010-08-01 02:46:19ezio.melottisetnosy: + ezio.melotti
messages: + msg1756
2010-06-02 17:02:02techtoniksetmessages: + msg1669
2010-06-02 15:44:17techtoniksetstatus: unread -> chatting
nosy: + techtonik
messages: + msg1668
2010-06-02 11:58:50yaniv.aknincreate