From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 4265558CE for ; Fri, 2 Dec 2016 17:41:17 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 02 Dec 2016 08:41:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,287,1477983600"; d="scan'208";a="793521681" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by FMSMGA003.fm.intel.com with ESMTP; 02 Dec 2016 08:41:16 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.91]) by IRSMSX101.ger.corp.intel.com ([163.33.3.153]) with mapi id 14.03.0248.002; Fri, 2 Dec 2016 16:41:15 +0000 From: "Mcnamara, John" To: "Mcnamara, John" , Neil Horman CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] Proposal for a new Committer model Thread-Index: AdJAs7riGyOWXzb1RBWkYul07VgIhwBEzAqAAitju4AAHsOC0ABy0ZZw Date: Fri, 2 Dec 2016 16:41:14 +0000 Message-ID: References: <20161118161025.GC29049@hmsreliant.think-freely.org> <20161129191207.GA17132@hmsreliant.think-freely.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjYwZTFiOWYtNDI3Yy00ZjI4LWJmMzEtOGM5ZDFhYTcwMjNkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlZ1N0FLRnNwd2pjSkFUN1VWaTFIS2tSUHhIUmpYSnNFSUU2REVVU1wvSjlvPSJ9 x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Proposal for a new Committer model X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 16:41:18 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John > Sent: Wednesday, November 30, 2016 9:59 AM > To: Neil Horman > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] Proposal for a new Committer model >=20 > > -----Original Message----- > > From: Neil Horman [mailto:nhorman@tuxdriver.com] > > Sent: Tuesday, November 29, 2016 7:12 PM > > To: Mcnamara, John > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > > > > ... > > > > > > B) Designate alternates to serve as backups for the maintainer when > > > they are unavailable. This provides high-availablility, and sounds > > > very much like your proposal, but in the interests of clarity, there > > > is still a single maintainer at any one time, it just may change to > > > ensure the continued merging of patches, if the primary maintainer > > > isn't > > available. > > > Ideally however, those backup alternates arent needed, because most > > > of the primary maintainers work in merging pull requests, which are > > > done based on the trust of the submaintainer, and done during a very > > > limited window of time. This also partially addreses multi-vendor > > > fairness if your subtree maintainers come from multiple > > > participating > > companies. > > > > > > Regards > > > Neil > > > > > > > > > > > > > Soo, I feel like we're wandering away from this thread. Are you going > > to make a change to the comitter model? >=20 > Hi, >=20 > Yes. I think we have consensus on the main parts. I'll re-draft a proposa= l > that we can discuss and then add to the contributors guide. >=20 > John >=20 I'll submit a draft update to the DPDK Code Contributors guide shortly. John