Luckily, I believe we are not affected by the change because we are using the Hadoop Permissions scheme in JIRA and not the ASF defaults. For a first-time contributor, I don't think it makes much difference whether we assign the ticket or they do. But it seems better for existing contributors to be allowed to assign additional tickets to themselves without having to ask someone to do it for them. I don't think we've seen any abuse of ticket-assigning privileges (and in fact it's hard to imagine what that would look like).
On Wed, May 14, 2014 at 1:38 PM, Sean Busbey <[email protected]> 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 > > -- > Sean >
