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 AD9BD2BF0 for ; Wed, 26 Oct 2016 12:21:56 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 26 Oct 2016 03:21:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,550,1473145200"; d="scan'208";a="777881360" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by FMSMGA003.fm.intel.com with ESMTP; 26 Oct 2016 03:21:55 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.210]) by IRSMSX153.ger.corp.intel.com ([169.254.9.226]) with mapi id 14.03.0248.002; Wed, 26 Oct 2016 11:21:54 +0100 From: "O'Driscoll, Tim" To: Thomas Monjalon , "moving@dpdk.org" Thread-Topic: [dpdk-moving] description of technical governance Thread-Index: AQHSLsgspqsrwFQmYEaV+coOh/7zraC6hH4w Date: Wed, 26 Oct 2016 10:21:53 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67607DDE@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com> <4939831.0LCNYxqha0@xps13> In-Reply-To: <4939831.0LCNYxqha0@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiN2I4YzM3NTQtNGU1Zi00YTE3LWEyZmEtNmM4MjNlY2IzMjU0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IklxcUVyWW1KQ0lCc1haeXFUcDJYWGRGakZFRnJaanNab2ZcL01HZmM4U3lJPSJ9 x-ctpclassification: CTP_IC 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-moving] description of technical governance X-BeenThere: moving@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK community structure changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 10:21:57 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, October 25, 2016 3:00 PM > To: moving@dpdk.org > Cc: O'Driscoll, Tim > Subject: Re: [dpdk-moving] description of technical governance >=20 > 2016-10-25 11:27, O'Driscoll, Tim: > > We also have a gap in terms of documenting technical governance. > > Even ignoring the move to LF, Matt in particular was looking for > > more clarity on this. > > Thomas: would you be willing to create and post a proposal on this? >=20 > The technical governance is consensus-based. > The board was built in case a consensus is not found. >=20 > There are several projects with their own git trees. > DPDK and the web site are two of them. >=20 > The DPDK project is organized around some git subtrees > and the mainline gathers every contributions accepted in the subtrees. > The component maintainers are quality responsibles for the code and > the git history. They coordinate how improvements and fixes are done. > The git tree committers are responsibles of the pace, giving time for > reviews and tests while releasing in time. They also do the last checks > or call for help when there is no progress on a patch. >=20 > Is it the kind of information you are looking for? > I think the technical governance must be described on the web site > in the "development" page. > It is already partly described but it may requires more details and > updates. Yes, it's the additional detail that I was asking about. If you look at wha= t we have at the moment (http://dpdk.org/dev), it's quite brief. Other proj= ects typically have more detail, for example: - FD.io Technical Community Charter: https://fd.io/governance/technical-com= munity-charter - OvS technical governance including committer responsibilities and process= for adding and removing committers: http://openvswitch.github.io/contribut= ors/ - ODL TSC Charter: https://www.opendaylight.org/tsc-charter We don't necessarily need as much detail as they have, but I think we do ne= ed a bit more than we have at the moment. From a brief discussion with Mike= Dolan during our previous engagement with the LF earlier in the year, the = LF would simply be looking for DPDK technical governance to be properly doc= umented, and for it to be meritocratic (e.g. committers chosen based on his= tory of contributions rather than the company they work for). Matt also had some thoughts during our discussion in Dublin on things he'd = like to see added to the technical governance. Perhaps he can comment furth= er on what he'd like to see. In terms of where this is documented, I don't think that matters, and addin= g some additional detail to the existing Development page seems like a good= solution to me.