David Reiss wrote:
I'd be fine with adding more committers, but I'm not convinced that too few committers is the problem.
More committers is better since it can spread the binding review load around. While anyone can review a patch, the ability to act on reviews does motivate folks. Put alternately, if someone's a committer then they can no longer complain about a slow review process!
The way the Apache Pyramid Scheme works is that, if committers review enough of a contributors patches to find that they're committer material, then they can make them a committer, to help with reviewing.
The best practice in Jira is to, as soon as someone contributes a patch, give them the "Contributor" role in Jira on the project and assign them that issue and any others where they contribute patches. Then you can use Jira to see how many patches someone has contributed (since nice reports are available by assignee, but not by attacher-of-patches) and what percentage of those patches got committed, and whether the dialog around them was civil, etc.
I see Dave Engberg has contributed a bunch of patches, but he's not been assigned any issues nor is he yet a contributor in Jira so that he can be assigned issues...
Doug
