I guess those can happen concurrently (ie, we need to review everything labelled 'ramp-up').
On Mon, Oct 24, 2016 at 9:39 AM, Jim Apple <[email protected]> wrote: > Why do we need to fix the "ramp*" bugs BEFORE we label "newbie" bugs? > > On Sat, Oct 22, 2016 at 1:12 PM, Marcel Kornacker <[email protected]> > wrote: > > Before you do that we need to sit down and reclassify what's currently > > labeled 'ramp-up', some of those tasks aren't really suitable as that > > (because they don't have an educational component). > > > > On Fri, Oct 21, 2016 at 10:53 AM, Jim Apple <[email protected]> > wrote: > >> SGTM. I will pick some of the PMC members and ask them to individually > >> classify all of the ramp* bugs in a single component by marking the > >> ones good for newbies as "newbie" and removing the "ramp*" tags from > >> "newbie" issues. > >> > >> I hope this will produce a nice set of issues for newbies to choose > >> from to help us entice new developers, testers, doc writers, and so > >> on. > >> > >> On Fri, Oct 21, 2016 at 9:32 AM, Marcel Kornacker <[email protected]> > wrote: > >>> I agree, we have enough rules regarding jira labeling already. > >>> > >>> A "newbie" label to indicate tasks that someone without any/much > >>> exposure to the codebase should be able to handle seems like a good > >>> idea. > >>> > >>> "Ramp-up" really means something else (good learning experience, but > >>> could be moderately complex and require some understanding of the > >>> codebase). > >>> > >>> On Thu, Oct 20, 2016 at 10:32 PM, Henry Robinson <[email protected]> > wrote: > >>>> I still think that adding more complexity to the JIRA state space is > only > >>>> going to increase the cognitive burden of managing JIRAs, something I > spend > >>>> quite a lot of my life doing already. It would need to be a pretty > big win > >>>> for it to be worth it to me. > >>>> > >>>> Happy to go with the consensus, but would prefer to avoid more labels > where > >>>> possible. > >>>> > >>>> On 20 October 2016 at 16:44, Jim Apple <[email protected]> wrote: > >>>> > >>>>> Ah, I was only suggesting this "non-newbie" as a tool for committers > >>>>> to use to help us find good newbie bugs, not as a tool for newbies. > >>>>> > >>>>> It will probably take a while to triage everything, and some people > >>>>> will not get their triaging work done in a timely fashion, and new > >>>>> bugs will show up and need triaging, and old bugs will (hopefully) be > >>>>> fixed by newbies, requiring us to go and find new bugs to label > >>>>> "newbie" > >>>>> > >>>>> On Thu, Oct 20, 2016 at 4:40 PM, Henry Robinson <[email protected]> > >>>>> wrote: > >>>>> > Right. Which 'newbie' is going to have that degree of JIRA nuance? > >>>>> > > >>>>> > I also feel it's better to show new contributors what they *could* > do, > >>>>> than > >>>>> > to carefully mark things that they *should not* do. > >>>>> > > >>>>> > On 20 October 2016 at 16:28, Jim Apple <[email protected]> > wrote: > >>>>> > > >>>>> >> So you're suggesting that there be no label for "this is triaged > and > >>>>> >> not suitable for newbies"? > >>>>> >> > >>>>> >> On Thu, Oct 20, 2016 at 4:14 PM, Henry Robinson < > [email protected]> > >>>>> >> wrote: > >>>>> >> > I would strongly prefer not adding "non-newbie". It seems to > have > >>>>> limited > >>>>> >> > use, and is another way to increase the state space of JIRA > labels, > >>>>> >> > components, etc, etc. > >>>>> >> > > >>>>> >> > Let's just find some good first-patch candidates and tag them. > >>>>> >> > > >>>>> >> > On 20 October 2016 at 16:03, Jim Apple <[email protected]> > wrote: > >>>>> >> > > >>>>> >> >> Since I have heard no objection to these tag names, I'm picking > >>>>> >> >> "newbie" and "non-newbie". I am going to start emailing some > PMC > >>>>> >> >> members to ask them to categorize issues. > >>>>> >> >> > >>>>> >> >> On Tue, Oct 18, 2016 at 9:57 AM, Jim Apple < > [email protected]> > >>>>> >> wrote: > >>>>> >> >> > How shall we distinguish between the following three classes > of > >>>>> >> issues: > >>>>> >> >> > > >>>>> >> >> > 1. Un-triaged ramp-up issues > >>>>> >> >> > 2. ramp-up issues that are not for newbies > >>>>> >> >> > 3. newbie issues > >>>>> >> >> > > >>>>> >> >> > We could add two tags, "newbie" and "non-newbie". We could > call the > >>>>> >> >> > second tag something other than "non-newbie", like > "second-patch" > >>>>> or > >>>>> >> >> > "sophomore". > >>>>> >> >> > > >>>>> >> >> > Thoughts? > >>>>> >> >> > > >>>>> >> >> > On Mon, Oct 17, 2016 at 10:27 PM, Marcel Kornacker < > >>>>> >> [email protected]> > >>>>> >> >> wrote: > >>>>> >> >> >> Please don't add that comment. :) > >>>>> >> >> >> > >>>>> >> >> >> What's currently labelled ramp-up is often not a good > newbie task > >>>>> >> (and > >>>>> >> >> >> maybe not even a good ramp-up task). The best way to > identify > >>>>> newbie > >>>>> >> >> >> tasks is for a few senior engineers to sift through the > ramp-up > >>>>> tasks > >>>>> >> >> >> and pick out maybe a few dozen that truly qualify as newbie > tasks. > >>>>> >> >> >> > >>>>> >> >> >> I'm happy to help out with that when I get back. > >>>>> >> >> >> > >>>>> >> >> >> On Mon, Oct 17, 2016 at 6:50 PM, Jim Apple < > [email protected]> > >>>>> >> >> wrote: > >>>>> >> >> >>> The Impala JIRA has 129 tasks that have no assignee, are > still > >>>>> open, > >>>>> >> >> >>> and are labelled ramp* (i.e. ramp-up, ramp-up-introductory, > >>>>> etc.). > >>>>> >> >> >>> > >>>>> >> >> >>> I'd like to find which of those tasks are good tasks for > someone > >>>>> who > >>>>> >> >> >>> is making their first Impala patch. I intend to promote > those on > >>>>> one > >>>>> >> >> >>> or more of : the blog, the twitter account, this list, the > user > >>>>> >> list, > >>>>> >> >> >>> helpwanted.apache.org, and so on. > >>>>> >> >> >>> > >>>>> >> >> >>> The tasks should be the kind of thing that someone won't > need too > >>>>> >> much > >>>>> >> >> >>> hand-holding on, once their have their dev environment up > and > >>>>> >> working. > >>>>> >> >> >>> > >>>>> >> >> >>> To do this, I was thinking of adding a comment to all 129 > tasks > >>>>> to > >>>>> >> ask > >>>>> >> >> >>> the watchers of each issue if it should be labelled > "newbie". > >>>>> This > >>>>> >> >> >>> will send hundreds of emails, which is a bummer, but it > seems to > >>>>> me > >>>>> >> >> >>> like the best way to track the discussions and decisions. > >>>>> >> >> >>> > >>>>> >> >> >>> What does everyone think? > >>>>> >> >> > >>>>> >> > > >>>>> >> > > >>>>> >> > > >>>>> >> > -- > >>>>> >> > Henry Robinson > >>>>> >> > Software Engineer > >>>>> >> > Cloudera > >>>>> >> > 415-994-6679 > >>>>> >> > >>>>> > > >>>>> > > >>>>> > > >>>>> > -- > >>>>> > Henry Robinson > >>>>> > Software Engineer > >>>>> > Cloudera > >>>>> > 415-994-6679 > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Henry Robinson > >>>> Software Engineer > >>>> Cloudera > >>>> 415-994-6679 >
