I tried to start looking at the newdev label a few months ago and pick a couple of issues up. My feeling was that tagged issues were old and typically of very little relevance - still David was very nice helping me get my commits through (and I learned a huge lot).
I think having a newdev label that's kept in use would be great! At the same time, this also requires that some committers actively take part in the typically tedious discussions happening around issues that beginners approach. Michele On Thu, Aug 6, 2020 at 6:13 AM Anshum Gupta <ans...@anshumgupta.net> wrote: > There used to be a 'newdev' label in the past that fell through the > cracks. https://cwiki.apache.org/confluence/display/LUCENE/HowToContribute > mentions > the label, but of course, not a ton of JIRAs exist with that label for new > devs to pick up and run with. > > We could start using the label. I personally tagged a bunch of JIRAs once > upon a time with that label and also remember that as something we did at > one of the committer meetings, but then the lower hanging JIRAs were really > created and resolved without much delay, not leaving much on the table for > new developers. > We can certainly get back to using the label again. > > -Anshum > > On Wed, Aug 5, 2020 at 8:04 PM Marcus Eagan <marcusea...@gmail.com> wrote: > >> Community, >> >> In the vane of more developer friendly, I think we should create a first >> issue label. In my experience, that label has been a great way to get >> newcomers involved in projects new to them. >> >> I've seen it in a number of Apache projects that I have contributed to, >> proprietary projects, and in CNCF projects. >> >> Please let me know what you think about a first issue label to make it >> easier for people not necessarily in the community looking to join to do so >> in the future. >> >> Thanks, >> -- >> Marcus Eagan >> >> > > -- > Anshum Gupta >
