From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170])
 by dpdk.org (Postfix) with ESMTP id 2E037558B;
 Fri, 18 Nov 2016 07:00:28 +0100 (CET)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 8422F1E7; Thu, 17 Nov 2016 22:00:27 -0800 (PST)
Date: Thu, 17 Nov 2016 22:00:27 -0800
From: Matthew Hall <mhall@mhcomputing.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "moving@dpdk.org" <moving@dpdk.org>
Message-ID: <20161118060027.GA17595@mhcomputing.net>
References: <B27915DBBA3421428155699D51E4CFE202661F22@IRSMSX103.ger.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202661F22@IRSMSX103.ger.corp.intel.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Subject: Re: [dpdk-moving] [dpdk-dev] Proposal for a new Committer model
X-BeenThere: moving@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK community structure changes <moving.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/moving>,
 <mailto:moving-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/moving/>
List-Post: <mailto:moving@dpdk.org>
List-Help: <mailto:moving-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/moving>,
 <mailto:moving-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 06:00:28 -0000

On Thu, Nov 17, 2016 at 09:20:50AM +0000, Mcnamara, John wrote:
> One committer to master represents a single point of failure and at times can be inefficient.

I have a lot more issues because of slow or inconclusive review of patches 
than I do because of committers. Often times they just get rejected in 
Patchwork with no feedback. Or it takes forever to get reviews.

I don't think the committer is the right place to point to the single point of 
failure.

Matthew.