Ezio Melotti <ezio.melo...@gmail.com> added the comment: > Well, it does hurt, because the more sentences you write, the more the > devguide becomes bloated and difficult to follow
OTOH is easy to ignore an "how to register to the tracker" section if you are already registered or if you don't need to register now or you think you know how to do it. Also note that I'm not adding these sections, but I'm just moving them from the bugs page in the doc (with some markup changes and refactoring). The only section I added is "Finding an Issue You Can Help With". > The devguide is *not* primarily for core developers. It's for new > contributors who want to get set up, so that they don't give up in the > absence of clear indications. Agreed, and registering and using the bug tracker is part of this set up, regardless of how obvious the process is (or should be). Anyway, it would be fine with me to not document these "basic" tasks (how to register/login/search), but it seems to me that people think that the content of the bugs page is useful, and I would rather have it with the rest in the devguide, rather than having it in a separate page. ---------- _______________________________________ 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
