From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 7F4F85694 for ; Tue, 19 May 2015 22:21:55 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 19 May 2015 13:21:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,459,1427785200"; d="scan'208";a="495700689" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by FMSMGA003.fm.intel.com with ESMTP; 19 May 2015 13:21:54 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.36]) by IRSMSX101.ger.corp.intel.com ([169.254.1.217]) with mapi id 14.03.0224.002; Tue, 19 May 2015 21:21:52 +0100 From: "O'Driscoll, Tim" To: Neil Horman , Thomas Monjalon Thread-Topic: [dpdk-dev] Technical Steering Committee (TSC) Thread-Index: AdCOhfiHYCdsiQY0Tuup0INCIVIARwDs8hQAAAHK9QAAAF4GgAAD0RIAAAelp4A= Date: Tue, 19 May 2015 20:21:52 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D46A8D@IRSMSX102.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D43080@IRSMSX102.ger.corp.intel.com> <20150519153434.GA29078@hmsreliant.think-freely.org> <6422303.qpQUJvDa9r@xps13> <20150519173421.GB29078@hmsreliant.think-freely.org> In-Reply-To: <20150519173421.GB29078@hmsreliant.think-freely.org> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Technical Steering Committee (TSC) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 20:21:55 -0000 > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman >=20 > On Tue, May 19, 2015 at 05:45:05PM +0200, Thomas Monjalon wrote: > > 2015-05-19 11:34, Neil Horman: > > > On Tue, May 19, 2015 at 07:43:14AM -0700, Stephen Hemminger wrote: > > > > > Composition of the TSC should reflect contributions to the > project, but be > > > > > balanced so that no single party has an undue influence. It > should also be > > > > > kept to a manageable size(maybe 7?). > > > > > > > > > > The TSC should elect its own chair, who would have the deciding > vote in > > > > > the event that the TSC was deadlocked. Once in place, the TSC > should > > > > > approve any new members. > > > > > > > > > > Specific details on membership can be discussed and agreed > later, if we > > > > > agree on the creation of a TSC. > > > > > > > > TSC should be limited to those individuals and companies that have > > > > contributed in a non-trivial way to the DPDK distributed code > base. > > > > It should not be a users group, or place for network vendors who > take but > > > > never give back. > > > > > > > +1 > > > > > > It should also endavour to only act as a fallback body for any > issues commonly > > > handled by the development communtiy (patch acceptance/review, etc) > > > > I agree that it should be a fallback. > > And I'm wondering how useful it would be: have we ever known such > discussion or > > conflict without finding a solution or a consensus? > Well, I suppose the jury is still out on that, since there are ongoing > problems, > in the form of patch latency, and such. But for the most part, no, > problems > tend to reach consensus resolution IMO It's true that there aren't many obvious examples, although as Neil points = out there are still some things that are ongoing. One issue that springs to= mind where we didn't reach consensus was inclusion of ABI Versioning in 1.= 8. It was subsequently included in 2.0, but there were people who believed = it should have been in 1.8. The other issue with having to reach consensus on everything is that it ten= ds to a lowest common denominator approach, and can slow things down. There= are times where a clear decision and then everybody moving forward is pref= erable. > > By the way, is there a TSC in Linux netdev? > > > No, but there are TSC for many projects, including Openshift, > freedesktop.org, > etc. >=20 > Neil