I like that flow.
I'm very much against not letting contributors assign tickets. If you have a
problem with old contributors stealing tickets from new contributors, then
that needs to be handled with best practices documentation and/or explicit
coaching. Locking down who can assign tickets is
As a contributor, I like this approach. I'm able to through and assign an
issue to myself without pestering anyone else.
I like the incentive-based approach for prospective contributors: have a
committer assign an issue to a user after they express interest in working
it, then give them
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,
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
+1 for restoring old behavior.Why wouldn't we allow contributors to help
themselves help the community?
On Thu, May 15, 2014 at 11:13 AM, John Vines vi...@apache.org wrote:
Yes, restore the old behavior
On Wed, May 14, 2014 at 4:38 PM, Sean Busbey bus...@cloudera.com wrote:
We don't have
What was the reasoning behind the change?
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
Yes, restore the old behavior
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
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
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
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
10 matches
Mail list logo
