I vote yes, let's use Deron's suggestion. It's simple, and assigning a JIRA issue when the user requests to start working on it avoids the issue of duplicated work.
- Mike On Wed, Jan 20, 2016 at 1:49 AM Frederick R Reiss <[email protected]> wrote: > Shall we use Deron's suggestion below as our process for the time being? > > Fred > > [image: Inactive hide details for Luciano Resende ---01/18/2016 03:08:58 > PM---On Mon, Jan 18, 2016 at 1:54 PM, Deron Eriksson <deroneri]Luciano > Resende ---01/18/2016 03:08:58 PM---On Mon, Jan 18, 2016 at 1:54 PM, Deron > Eriksson <[email protected]> wrote: > > From: Luciano Resende <[email protected]> > To: [email protected] > Date: 01/18/2016 03:08 PM > Subject: Re: Workflow for assigning issues to users > ------------------------------ > > > > > On Mon, Jan 18, 2016 at 1:54 PM, Deron Eriksson <[email protected]> > wrote: > > > What is our workflow for assigning JIRA issues to users? > > > > For instance, Nakul Jindal asked in the comments to work on > > https://issues.apache.org/jira/browse/SYSTEMML-456. What's our workflow? > > > > For instance, one possible workflow: > > > > 1) User asks to work on issue. > > 2) If new user, we add user as project contributor (Contributor role). > > 3) We set user as Assignee for the issue. > > 4) User submits pull request. > > 5) Resolve and close issue. > > > > It would be good to settle on such a workflow now that our JIRA server is > > up to avoid confusion. > > > > Luciano, is there an Apache standard that we should be following? > > > > Deron > > > > > There is no Apache standard, each project can discuss their preference. > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > > > -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone.
