That looks like an accurate representation of the informal process. +1 for letting them assign themselves
Aside about #7: If this process gets documented in a contributor section of the website (which, maybe it should?) or a wiki, or whatever, I'd want to just add note that when looking for tickets to work on, they do not have to shy away from something, just because it is currently assigned to somebody else. Rather, they could seek out a collaboration, or check on the status and see if it's actively being worked on. This comment might be helpful to such a document, because we all know the JIRA is not always up-to-date, and that tickets may be assigned for other reasons. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, May 14, 2014 at 4:38 PM, Sean Busbey <bus...@cloudera.com> 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
