Re: First Issue Label
Awesome Tomoko. Thanks to everyone who is helping here. On Tue, Aug 11, 2020 at 10:29 PM Tomoko Uchida wrote: > JFYI: I opened an issue with the "newdev" label. It's mainly about > documentation and requires a bit of knowledge about our build system > (gradle). > https://issues.apache.org/jira/browse/LUCENE-9459 > > Thanks, > Tomoko > > > 2020年8月9日(日) 5:00 Eric Pugh : > >> I’d be interested in shepherding “newdev” style contributions to being >> commits. I’m not comfortable making any deeper changes in Solr, but if >> it’s a “newdev” labeled featured, well then it’s probably “newcommitter” >> friendly as well ;-). >> >> Feel free to tag me on any issues that have patches etc…. >> >> On Aug 8, 2020, at 8:19 AM, Ishan Chattopadhyaya < >> ichattopadhy...@gmail.com> wrote: >> >> Thanks for the reminder, Marcus. I just added a "newdev" label to this: >> https://issues.apache.org/jira/browse/SOLR-13438. >> >> On Fri, Aug 7, 2020 at 4:55 AM Jan Høydahl wrote: >> >>> I have tagged some of the issues I have filed but not had bandwidth to >>> tackle immediately as ’newdev’, but could probably have done it far more >>> often. >>> If all of us browse through the issues we have created and tag those we >>> think are simple and important, then there would suddenly be a bunch! >>> Great reminder, Marcus! Having a clear focus on new devs is important! >>> >>> Jan >>> >>> 6. aug. 2020 kl. 06:12 skrev Anshum Gupta : >>> >>> 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 >>> 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 >>> >>> >>> >> ___ >> *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 >> | http://www.opensourceconnections.com | My Free/Busy >> <http://tinyurl.com/eric-cal> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed >> <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> >> This e-mail and all contents, including attachments, is considered to be >> Company Confidential unless explicitly stated otherwise, regardless >> of whether attachments are marked as such. >> >> -- Marcus Eagan
Re: First Issue Label
JFYI: I opened an issue with the "newdev" label. It's mainly about documentation and requires a bit of knowledge about our build system (gradle). https://issues.apache.org/jira/browse/LUCENE-9459 Thanks, Tomoko 2020年8月9日(日) 5:00 Eric Pugh : > I’d be interested in shepherding “newdev” style contributions to being > commits. I’m not comfortable making any deeper changes in Solr, but if > it’s a “newdev” labeled featured, well then it’s probably “newcommitter” > friendly as well ;-). > > Feel free to tag me on any issues that have patches etc…. > > On Aug 8, 2020, at 8:19 AM, Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> wrote: > > Thanks for the reminder, Marcus. I just added a "newdev" label to this: > https://issues.apache.org/jira/browse/SOLR-13438. > > On Fri, Aug 7, 2020 at 4:55 AM Jan Høydahl wrote: > >> I have tagged some of the issues I have filed but not had bandwidth to >> tackle immediately as ’newdev’, but could probably have done it far more >> often. >> If all of us browse through the issues we have created and tag those we >> think are simple and important, then there would suddenly be a bunch! >> Great reminder, Marcus! Having a clear focus on new devs is important! >> >> Jan >> >> 6. aug. 2020 kl. 06:12 skrev Anshum Gupta : >> >> 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 >> 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 >> >> >> > ___ > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 > | http://www.opensourceconnections.com | My Free/Busy > <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless > of whether attachments are marked as such. > >
Re: First Issue Label
I’d be interested in shepherding “newdev” style contributions to being commits. I’m not comfortable making any deeper changes in Solr, but if it’s a “newdev” labeled featured, well then it’s probably “newcommitter” friendly as well ;-). Feel free to tag me on any issues that have patches etc…. > On Aug 8, 2020, at 8:19 AM, Ishan Chattopadhyaya > wrote: > > Thanks for the reminder, Marcus. I just added a "newdev" label to this: > https://issues.apache.org/jira/browse/SOLR-13438 > <https://issues.apache.org/jira/browse/SOLR-13438>. > > On Fri, Aug 7, 2020 at 4:55 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > I have tagged some of the issues I have filed but not had bandwidth to tackle > immediately as ’newdev’, but could probably have done it far more often. > If all of us browse through the issues we have created and tag those we think > are simple and important, then there would suddenly be a bunch! > Great reminder, Marcus! Having a clear focus on new devs is important! > > Jan > >> 6. aug. 2020 kl. 06:12 skrev Anshum Gupta > <mailto:ans...@anshumgupta.net>>: >> >> There used to be a 'newdev' label in the past that fell through the cracks. >> https://cwiki.apache.org/confluence/display/LUCENE/HowToContribute >> <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 > <mailto: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 > ___ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
Re: First Issue Label
Thanks for the reminder, Marcus. I just added a "newdev" label to this: https://issues.apache.org/jira/browse/SOLR-13438. On Fri, Aug 7, 2020 at 4:55 AM Jan Høydahl wrote: > I have tagged some of the issues I have filed but not had bandwidth to > tackle immediately as ’newdev’, but could probably have done it far more > often. > If all of us browse through the issues we have created and tag those we > think are simple and important, then there would suddenly be a bunch! > Great reminder, Marcus! Having a clear focus on new devs is important! > > Jan > > 6. aug. 2020 kl. 06:12 skrev Anshum Gupta : > > 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 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 > > >
Re: First Issue Label
I have tagged some of the issues I have filed but not had bandwidth to tackle immediately as ’newdev’, but could probably have done it far more often. If all of us browse through the issues we have created and tag those we think are simple and important, then there would suddenly be a bunch! Great reminder, Marcus! Having a clear focus on new devs is important! Jan > 6. aug. 2020 kl. 06:12 skrev Anshum Gupta : > > There used to be a 'newdev' label in the past that fell through the cracks. > https://cwiki.apache.org/confluence/display/LUCENE/HowToContribute > <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 <mailto: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
Re: First Issue Label
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 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 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 >
Re: First Issue Label
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 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
Re: First Issue Label
I think we already had some. But nobody really jumped on it. Still, if somebody wants to monitor it, it can be restarted. Regards, Alex On Wed., Aug. 5, 2020, 11:04 p.m. Marcus Eagan, 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 > >
First Issue Label
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
