Hi David I think this is a good idea. The contributing guide says to look for easy pickings tickets as a good way to get started, but there are hardy any, so there’s a bit of a disconnect there.
I don’t think there’s any harm in a false positive, so don’t be shy. 😃 Thanks! C. On Wed, 10 Feb 2021 at 21:41, smi...@gmail.com <smit...@gmail.com> wrote: > Hi all, > > tl;dr - I'm proposing we make more use of the 'easy pickings' flag on trac > and should aim to have 20-30 tickets with this flag. More options here will > hopefully help new contributors. If there is support, I'm happy to help > review tickets to push the number up. > > > I've been thinking about the 'easy pickings' filter and it feels to me > like a bit of a missed opportunity. As a new contributor, I think filtering > Trac by this tag is one of the first things I'd do in the hope for an > 'easy' ticket that is available. Without this we expect folk to pick a > component and then judge which is 'easy'. I think having somewhat of a > curated list under this flag could help folk find "easier" tickers. Side > note: as discussed elsewhere "easy" isn't a great word here, "easier" or > maybe "ideal first issue" could be better, but is a slightly separate > topic. > > Currently, we have only 8 out of c1,100 tickets marked in this category. I > think a reasonable target would be for say 20-30 tickets (c.2.0%-2.5%) to > be in this category. A slightly higher number than now means that there > would be more chance for folk to pick up an available ticket. > > While "easy" is subjective, I think as well as the very rare but obviously > "easy" tickets (such as re-ordering a list of items in the docs) those > tickets which are "almost" there (had a prior patch and feedback, and > "just" need a few tweaks) could fall into this category, as could those > "just" needing docs. Tickets that have had some thought and work put into > them, are likely to be far easier than those without. > > Appreciate thoughts. I'm more than happy to review some tickets to bump up > the number. > > Thanks > > David > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/3d87b568-053a-4472-8b93-5d1d377c3820n%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/3d87b568-053a-4472-8b93-5d1d377c3820n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyQ7U6tjdg1dQd0Q-jcxCPNoPBCanjDPhYwfuiLxrdgLcg%40mail.gmail.com.
