My recommendation would be this:

1)  Start with a list of folks who've made significant contributions to the tree in question
2)  Potentially winnow it from there

For existing code bases, its important to start with folks who have a meritocratic history of contribution.
Its important to note that is not necessarily the only criteria, there are a lot of intangibles as well.  Not everybody who writes a lot of code wants to be a committer or would be good at being a committer.  But if there is code to have history with, and you don't have history of contributing to it, it probably doesn't make sense for you to be a committer.

Ed

On Thu, Nov 17, 2016 at 1:27 AM, Mcnamara, John <john.mcnamara@intel.com> wrote:


> -----Original Message-----
> From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> Sent: Wednesday, November 16, 2016 7:43 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; Mcnamara, John
> <john.mcnamara@intel.com>; moving@dpdk.org; Yigit, Ferruh
> <ferruh.yigit@intel.com>; yuanhan.liu@linux.intel.com; De Lara Guarch,
> Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-moving] Proposal a Committer model
>
> On Wed, Nov 16, 2016 at 03:13:49PM +0000, Bruce Richardson wrote:
> > On Wed, Nov 16, 2016 at 10:45:55AM +0000, Thomas Monjalon wrote:
> >
> >
> > ...
> >
> > Now, I believe multi-committer model is much more conducive to this
> > way of working (though it does not strictly require multiple
> committers).
> > So long as one trusted committer (and all committers need to be
> > trusted) is happy with a patchset it should go in - provided a
> > reasonable review period has elapsed. There is too much waiting for
> > everyone to agree right now.
>
> The main question would be who will part of committers list?

Hi,

The initial list could be made up from someone from 6Wind, Intel and an ARM based company. If it is felt that someone else could be added then that could be proposed.

The OvS community had reasonably good guidelines about adding/removing committers. I'd suggest that we use something similar:

https://github.com/openvswitch/ovs/blob/master/Documentation/committer-grant-revocation.rst


>
> I believe the multi-committers model may not fix current consensus
> slowness issue. Instead, if we are focusing on reducing the workload of
> Thomas, then I think git pull request based scheme will reduce the
> workload.

So, something like a Gerrit model?

John