[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

2016-09-22 Thread Nick Coghlan
Nick Coghlan added the comment: OK, I've created the "easy (C)" keyword: http://bugs.python.org/keyword18 I've left the existing "easy" keyword alone for the time being, as the Python vs Documentation split is already implied by the component, but changing the keyword to "easy (Python)" would

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

2016-09-22 Thread Nick Coghlan
Nick Coghlan added the comment: Guido: good points, so I've instead filed https://github.com/python/devguide/issues/38 to discuss updating the Triaging section of the devguide with a bit more guidance on when it's a good idea to set these keywords.

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

2016-09-22 Thread Guido van Rossum
Guido van Rossum added the comment: The term "well defined" would not resonate with people looking for starter bugs. Read this piece for an overview of how other projects (esp. Mozilla) try to lure new contributors, and how that's seen by someone eager to contribute:

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

2016-09-22 Thread Nick Coghlan
Nick Coghlan added the comment: If we're tinkering with the "easy" tag, would it make sense to switch to a more objectively definable phrase like "well defined (Python)" and "well defined (C)"? The reason I ask is that good starter issues for folks that just want to work on CPython in