Standard ASF practice is that there are Committers, who have the commit bit, and Contributors, who contribute code but do not have the commit bit. Contributors rely on committers to review and commit their code, and it's the committers' responsibility to do so in a reasonably timely manner.
In other projects I'm involved in, the JIRA workflow is that, the first time a new person uploads a patch, one of the committers will add them to the contributors group in JIRA and assign that JIRA to them. In the future, they are free to assign themselves any JIRAs they plan to work on. Of course if someone assigns a JIRA to themself and doesn't appear to be making any progress, someone else can always ping them and ask to take it over. The above workflow is helpful when evaluating whether to make an existing contributor into a committer - it's trivial to search JIRA for tickets assigned to this person and resolved to see what they've contributed so far. -Todd On Wed, Oct 12, 2011 at 9:25 AM, Alan D. Cabrera <[email protected]> wrote: > > On Oct 12, 2011, at 8:37 AM, Billie J Rinaldi wrote: > >> I propose adding Jesse Yates (jesse_yates) to the accumulo-developers group >> on JIRA so that he can assign tickets to himself. :) > > Sounds like an interesting idea. What do we hope to accomplish by letting a > non-committer assign tickets to themselves? > > > Regards, > Alan > > -- Todd Lipcon Software Engineer, Cloudera
