> It seems like a simple solution to that> is some documentation on our web
> site encouraging people to contact > the person a ticket is assigned to if > they are interested in working on it. +1 -- Joey Echeverria Chief Architect Cloudera Government Solutions On Fri, May 16, 2014 at 9:46 AM, Keith Turner <[email protected]> wrote: > Looking at the ticket you linked it seems it easy for infra to make this > change. As long as its not a hassle for infra I would be in favor of > changing it back. > The problem w/ issues being assigned to people who are not working on them > (it seems this is sparks concern) applies to commiters and contributors. > It seems like a simple solution to that is some documentation on our web > site encouraging people to contact the person a ticket is assigned to if > they are interested in working on it. > On Wed, May 14, 2014 at 4: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 >>
