From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"moving@dpdk.org" <moving@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"yuanhan.liu@linux.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
Date: Thu, 17 Nov 2016 09:27:09 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202661F3E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20161116194251.GA7874@svelivela-lt.caveonetworks.com>
> -----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
next prev parent reply other threads:[~2016-11-17 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 23:35 Mcnamara, John
2016-11-16 10:45 ` Thomas Monjalon
2016-11-16 15:13 ` Bruce Richardson
2016-11-16 16:23 ` Wiles, Keith
2016-11-16 19:42 ` Jerin Jacob
2016-11-17 9:27 ` Mcnamara, John [this message]
2016-11-17 13:43 ` Thomas Monjalon
2016-11-17 14:05 ` Wiles, Keith
2016-11-18 10:45 ` Hemant Agrawal
2016-11-18 17:14 ` Stephen Hemminger
2016-11-17 22:57 ` Ed Warnicke
2016-11-18 10:45 ` Hemant Agrawal
2016-11-16 20:16 ` Dave Neary
2016-11-17 8:14 ` Mcnamara, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B27915DBBA3421428155699D51E4CFE202661F3E@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=moving@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).