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
On Mon, Oct 17, 2016 at 10:27 PM, Marcel Kornacker <mar...@cloudera.com> 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 <jbap...@cloudera.com> 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?