From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 1955F4CC9; Tue, 27 Feb 2018 09:59:18 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2018 00:59:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,400,1515484800"; d="scan'208";a="20502553" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga007.fm.intel.com with ESMTP; 27 Feb 2018 00:59:17 -0800 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX108.ger.corp.intel.com (163.33.3.3) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 27 Feb 2018 08:59:16 +0000 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.9]) by irsmsx111.ger.corp.intel.com ([169.254.2.246]) with mapi id 14.03.0319.002; Tue, 27 Feb 2018 08:59:16 +0000 From: "De Lara Guarch, Pablo" To: "De Lara Guarch, Pablo" , "dev@dpdk.org" CC: "techboard@dpdk.org" Thread-Topic: Back-up committers for subtrees Thread-Index: AdOrA6sud8bhLPUJQJKXWZNVpkQZDwEpT1ew Date: Tue, 27 Feb 2018 08:59:15 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjg0N2EzNTYtZWI3Yi00MGRiLWEwYWEtOGZmNGFjMmI0Nzg5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InQ1bGZJQlwvQ3BGb252Z0dQK2luTDFyVXdMRHRsR3UyQThWUHBtMG91VzAwPSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Back-up committers for subtrees 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: Tue, 27 Feb 2018 08:59:19 -0000 Hi, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch, > Pablo > Sent: Wednesday, February 21, 2018 11:05 AM > To: dev@dpdk.org > Subject: [dpdk-dev] Back-up committers for subtrees >=20 > Hi everyone, >=20 > In the last few releases, the DPDK community has experienced a significan= t > growth, specifically in patches submitted and integrated. > Therefore, the number of subtrees has increased, to help maintain the > scalability. >=20 > Section 5.3 of the Contributor's guide > (http://dpdk.org/doc/guides/contributing/patches.html), Maintainers and > Sub-trees, states that there should be a backup maintainer per subtree: >=20 > "Ensure that there is a designated back-up maintainer and coordinate a > handover for periods where the tree maintainer can't perform their roles.= " >=20 > However, this is not the case for some of the subtrees. This could lead t= o > patch integration delays in case of unavailability (short or long term) o= f the > subtree committer, especially on busy times, which could lead to a delay = in > an RC release. >=20 > My suggestion is that every primary subtree committer proposes a back-up > committer for their subtree. > Once the proposed person agrees on taking this role, they should follow t= he > procedure explained in the documentation: >=20 >=20 > "Tree maintainers can be added or removed by submitting a patch to the > MAINTAINERS file. >=20 > The proposer should justify the need for a new sub-tree and should have > demonstrated a sufficient level of contributions in the area or to a simi= lar > area. >=20 > The maintainer should be confirmed by an ack from an existing tree > maintainer. Disagreements on trees or maintainers can be brought to the > Technical Board. >=20 >=20 >=20 > The backup maintainer for the master tree should be selected from the > existing sub-tree maintainers from the project. >=20 > The backup maintainer for a sub-tree should be selected from among the > component maintainers within that sub-tree." >=20 > The patches will be merged mainly by the primary committer, except when > this is unavailable, in which case, the back-up committer will take over, > after this unavailability is communicated between the two committers. > This implies that there will be no co-maintainership, to maintain a singl= e > point of contact with the mainline tree maintainer. >=20 > Any objections? CC'ing Tech board. Could this be discussed in the next meeting? Thanks, Pablo >=20 > Thanks, > Pablo >=20