Am 08.01.2011 23:22, schrieb Antoine Pitrou: > On Sat, 08 Jan 2011 23:05:06 +0100 > brett.cannon <python-checkins at python.org> wrote: >> +For bugs, an issue needs to: >> + >> +* Clearly explain the bug so it can be reproduced >> +* All relevant platform details are included >> +* What version(s) of Python are affected by the bug are fully known >> +* Is there a proper unit test that can reproduce the bug? >> + >> +These are things anyone can help with. > > FWIW, I'm really not fond of handing out triage tasks to beginners. > First because the claim that it doesn't require any specific knowledge > is wrong (in the case of Python, because it is a highly technical > product; it might be right for office suites, who knows). > Second because a newbie triager gets to interact with other newbies who > might be very confused if they are given misleading comments or asked > misleading (or completely irrelevant) questions. +1. Remember, this is not a purely hypothetical statement. > Things may be different when the person in question has been a long-time > community member, or has specific expertise, and is therefore able to > communicate meaningful advice. But for true beginners, I think it would > be much better to let them write a patch or a doc fix. Yep. Georg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4