Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of josh.elser@gmail.com
 designates 209.85.216.181 as permitted sender)
Message-ID: <53755FAF.9080108@gmail.com>
Date: Thu, 15 May 2014 20:45:35 -0400
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev@accumulo.apache.org
Subject: Re: [DISCUSS] Do we want contributors assigning to themselves?
References: 
 <CAGHyZ6KmaB8znDZtw9Ujjw6Nypq3bZHq+s9CKtzzZ0o-WckqBw@mail.gmail.com>
In-Reply-To: 
 <CAGHyZ6KmaB8znDZtw9Ujjw6Nypq3bZHq+s9CKtzzZ0o-WckqBw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Until we have problems with it, I would prefer that contributors could 
continue to assign things as they see fit.

Their contributor status implies that they are at least somewhat 
acclimated with our processes and that they have a positive opinion of 
the project.

On 5/14/14, 4:38 PM, Sean Busbey wrote:
> We don't have a formal onboarding process for drawing in new contributors,
> but a recent ASF Infra change impacts what I've observed historically.
>
> Here's what I've seen historically, more or less:
>
> 1) Someone expresses interest in a ticket
>
> 2) PMC/committers add them to the list of contributors in jira
>
> 3) respond to interest informing person of this change and encouraging them
> to assign the ticket to themselves
>
> 4) work happens on ticket
>
> 5) review/commit happens eventually
>
> 6) If contributor wants, added to website
>
> 7) contributor thanked and encouraged to find more tickets to assign to
> themselves.
>
> Due to a request from Spark, the ASF Jira got changed to default to not
> allow contributors to assign tickets[1].
>
> Before I speak for the PMC and file a follow on to change things back, I
> just wanted a gut check that we like the above as a general approach.
>
>
> [1]: https://issues.apache.org/jira/browse/INFRA-7675
>