Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-25 Thread Stephen J. Turnbull
Karthikeyan writes: > I would also recommend waiting for a core dev or someone to provide some > feedback or confirmation on even an easy issue's fix FWIW, I don't think waiting on core devs is a very good idea, because we just don't have enough free core dev time, and I don't think we (or any

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-24 Thread Karthikeyan
On Sun, Feb 24, 2019 at 1:07 PM Terry Reedy wrote: > On 2/23/2019 2:50 PM, Cheryl Sabella wrote: > > AM Karthikeyan wrote: > > I would also recommend waiting for a core dev or someone to provide > > some feedback or confirmation on even an easy issue's fix since it's > > easy to pr

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-23 Thread Terry Reedy
On 2/23/2019 2:50 PM, Cheryl Sabella wrote: AM Karthikeyan wrote: I would also recommend waiting for a core dev or someone to provide some feedback or confirmation on even an easy issue's fix since it's easy to propose a fix to be later rejected due to various reasons resulting

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-23 Thread Cheryl Sabella
On Fri, Feb 22, 2019 at 11:11 AM Karthikeyan wrote: > I would also suggest cleaning up the existing set of easy issues where the > issues was tagged as easy initially followed by discussion about how the > though easy has other concerns like backwards compatibility due to which it > can't be merg

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-22 Thread Karthikeyan
I would also suggest cleaning up the existing set of easy issues where the issues was tagged as easy initially followed by discussion about how the though easy has other concerns like backwards compatibility due to which it can't be merged. It's getting hard to get more easy issues and what could s

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-22 Thread Victor Stinner
Hi, Let me share with you (this mailing list) my experience with mentoring and what we call "easy issue". First of all, almost all "easy issues" are very hard issues: issues open for longer than one year, with many comments, and nobody succeeded to come up with a solution (well, otherwise the issu

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Guido van Rossum
In the mypy project we've definitely experienced the problem with "beginner" issues that they would be fixed by disinterested folks who just wanted to score some GitHub points, and we stopped doing that. While we've not kept track carefully, my impression is that we've not seen the quantity of cont

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Stephen J. Turnbull
Steve Dower writes: > I'm sympathetic to wanting to have tasks for the PyCon sprints, but at > the same time it feels exclusionary to "save" them from people who want > to volunteer at other times. It's already possible to do this sub rosa. Just get a mentor to "claim" the issue, and have a

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Cheryl Sabella
> I'm 100% in favor of discouraging regular contributors from fixing them > This would be nice too. Speaking from my experience, it's hard to leave the comfort of what looks to be a quick win (by submitting a PR on an easy issue) and moving on to something where you're more unsure. But... > -

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Mariatta
Cheryl, thanks for starting this thread and for helping to find easy issues to be worked on. I'm sympathetic to wanting to have tasks for the PyCon sprints, but at > the same time it feels exclusionary to "save" them from people who want > to volunteer at other times. Having paid to attend PyCon s

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Steve Dower
On 21Feb2019 1258, Cheryl Sabella wrote: I agree completely. We normally add the "Easy" or "Easy (C)" keywords to mark these (the latter for issues that involve C code), and these are collected under the "Easy issues" link at the left hand side of the tracker. Any reason

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Lysandros Nikolaou
On Thu, Feb 21, 2019 at 9:59 PM Cheryl Sabella wrote: > I agree completely. We normally add the "Easy" or "Easy (C)" keywords to >> mark these (the latter for issues that involve C code), and these are >> collected under the "Easy issues" link at the left hand side of the >> tracker. >> >> Any re

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Cheryl Sabella
> > I agree completely. We normally add the "Easy" or "Easy (C)" keywords to > mark these (the latter for issues that involve C code), and these are > collected under the "Easy issues" link at the left hand side of the > tracker. > > Any reason to change from this process? > > Thanks for asking abo

Re: [Python-Dev] "Good first issues" on the bug tracker

2019-02-21 Thread Steve Dower
On 21Feb2019 0557, Cheryl Sabella wrote: If you find anything you think is suitable, please add a comment with 'good first issue' and nosy me or Mariatta on it.  If you're unsure, then nosy us anyway.  It would be awesome to have too many issues to choose from than not enough.  If an issue isn'