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

Guido van Rossum added the comment: Thanks Berker! I agree the discussion shouldn't be narrowly about the keywords and how to assign them -- we could also do a better job of guiding new contributors. From Shubeksha's blog post it seems that we're doing almost nothing in this area -- people

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

R David Murray writes: > (At least, I think one can retire tags, I haven't actually > checked). I've done it on the XEmacs tracker, so it used to work fine, but that was a while ago. Steve ___ Tracker-discuss mailing list Tracker-discuss@python.org

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

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

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

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

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

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

Brett C. added the comment: If Berker is comfortable with his assessment then we can ignore my "conservative" suggestion and just rename the current label "easy (Python)" and reclassify as necessary. ___ PSF Meta Tracker

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

R David Murray added the comment: I'm not sure what you mean by "be conservative". Leave the current tag alone and add "easy (C)" and just apply it to the identified C issues? That would actually make sense. We could also add a *new* 'easy (python)', and retire the current 'easy' tag,

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

Brett C. added the comment: The other option is to be conservative and mark the current easy issues as "easy (C)" and then adjust accordingly. And I'm totally happy w/ David's interpretation of the bikeshed's plans as it's shorter. ___ PSF

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

Guido van Rossum added the comment: Go for that! On Mon, Sep 19, 2016 at 11:12 AM, Berker Peksag < metatrac...@psf.upfronthosting.co.za> wrote: > > Berker Peksag added the comment: > > I don't see a lot of C issues in the "easy issues" list. I agree that some > of them (including a few pure

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

Brett C. added the comment: "easy doc issue" wouldn't be hard to add either. Does anyone else have any feedback on this? ___ PSF Meta Tracker

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

Guido van Rossum added the comment: Those two sounds great -- maybe also add "easy documentation issue"? On Sun, Sep 18, 2016 at 10:57 AM, Brett C. < metatrac...@psf.upfronthosting.co.za> wrote: > > Brett C. added the comment: > > Adding a new keyword isn't hard; it can be done from >

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

New submission from Guido van Rossum: I've noticed we have a lot of "easy" issues on bugs.python.org that are only easy if you're fluent in C. We have (potentially) many new incoming contributors who aren't (yet) at that level but who would be happy to help out with other tasks that don't