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 204FAD592 for ; Wed, 11 Jan 2017 23:16:59 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP; 11 Jan 2017 14:16:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,347,1477983600"; d="scan'208";a="52199926" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga005.fm.intel.com with ESMTP; 11 Jan 2017 14:16:58 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by IRSMSX153.ger.corp.intel.com ([169.254.9.160]) with mapi id 14.03.0248.002; Wed, 11 Jan 2017 22:16:57 +0000 From: "O'Driscoll, Tim" To: "moving@dpdk.org" Thread-Topic: Minutes from "Moving DPDK to Linux Foundation" call, January 10th Thread-Index: AdJsVmDY9ZdQ5TGbSTyiN75wfeTMSQ== Date: Wed, 11 Jan 2017 22:16:56 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722A66A1@IRSMSX108.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMWZlOTU0Y2EtNDNhZS00NThmLThhMTMtZDZmZWVkY2RjMWI3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJma0E3TVNFOGwzOUhhSEdwckxlVFk5XC9nQ244NDErYmZBdUdmVTd0U1Fkdz0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, January 10th 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, 11 Jan 2017 22:17:00 -0000 Here are my notes from Tuesday's call. Please feel free to correct any erro= rs or to add additional details. Attendees: Ed Warnicke (Cisco), Elsie Wahlig (Qualcomm), Erez Scop (Mellano= x), Francois-Frederic Ozog (Linaro), Hemant Agrawal (NXP), Jan Blunck (Broc= ade), Jaswinder Singh (NXP), John Bromhead (Cavium), John McNamara (Intel),= Keith Wiles (Intel), Kevin Traynor (Red Hat), Mike Dolan (Linux Foundation= ), Olga Shern (Mellanox), Stephen Hemminger (Microsoft), Thomas Monjalon (6= WIND), Tim O'Driscoll (Intel), Vincent Jardin (6WIND). Firstly, here are some links to help keep track of things: Project Charter: https://docs.google.com/document/d/1x43ycfW3arJNX-e6NQt3OV= zAuNXtD7dppIhrY48FoGs Summary of discussion at Userspace event in Dublin: http://dpdk.org/ml/arch= ives/dev/2016-October/049259.html Minutes of October 31st call: http://dpdk.org/ml/archives/moving/2016-Novem= ber/000031.html Minutes of November 8th call: http://dpdk.org/ml/archives/moving/2016-Novem= ber/000058.html Minutes of November 15th call: http://dpdk.org/ml/archives/moving/2016-Nove= mber/000061.html Minutes of November 22nd call: http://dpdk.org/ml/archives/moving/2016-Nove= mber/000085.html Minutes of November 29th call: http://dpdk.org/ml/archives/moving/2016-Nove= mber/000099.html Minutes of December 6th call: http://dpdk.org/ml/archives/moving/2016-Decem= ber/000121.html Minutes of December 13th call: http://dpdk.org/ml/archives/moving/2016-Dece= mber/000124.html Minutes of December 20th call: http://dpdk.org/ml/archives/moving/2016-Dece= mber/000127.html Technical governance, including info on Maintainers and sub-trees: http://d= pdk.org/doc/guides/contributing/index.html & http://dpdk.org/dev. Reviewed the latest comments on the project charter. These were the signifi= cant discussion points: Do we need a clause to prevent gold members being outnumbered by silver mem= bers on the board? - There's already a cap on the number of Silver members on the board = in clause 3.1.2 ii, so this is already covered. We will need to decide on t= he value during membership discussions. Should the Governing Board meetings be public? The reasons given (primarily= by Mike and Ed) for not doing this were: - Legal issues. The GB may need to discuss legal issues which should be kep= t confidential. Attorneys will also not be willing to give opinions in publ= ic meetings. For some companies, their legal counsel will not allow them to= participate in public board meetings. - Potential new members. The GB may need to discuss potential new members w= ho may not have been contacted yet, or who may not want their interest in D= PDK made public until their membership is finalized. - Confidential budget info. Budgets may contain confidential info such as s= alaries which should not be discussed/disclosed in public. We agreed to consider this again and agree at the next meeting. If there's = no consensus then we'll need to vote. Should Tech Board meetings should be public? - Agreed that they should. The charter has been updated to reflect this. Should we have a Contributor membership level? Mike elaborated on his previ= ous guidance not to do this: - It doesn't serve any purpose. Contributors can be recognized in other way= s (on a web page, in an AUTHORS file in the git repo etc.). - Membership has a legal meaning for the LF and contributors may not meet c= omply (e.g. a member of an LF project needs to be a member of the LF, but a= contributor does not). - Others felt that this would just add overhead and cause confusion. Agreed that we don't see a need for this. Do DPDK project members need to be LF members? - The answer is yes. LF membership rates are documented in the LF bylaws (h= ttps://www.linuxfoundation.org/about/bylaws). I've added a link to the char= ter doc. Mike has clarified further in a separate email (http://dpdk.org/ml= /archives/moving/2017-January/000135.html). Should Gold and Silver members pay the same rate for lab resources? - Vincent proposed that Gold and Silver members pay the same rate for lab r= esources. I disagreed with this as it means that Gold members are paying tw= ice - they provide more funding for the project through a higher membership= fee, but would then be expected to also pay the same rate as Silver member= s who've contributed less. - We agreed that we would leave details of costs for different membership l= evels to be determined by the Governing Board. I'll update the charter to r= eflect this. Are there, or do there need to be, any DPDK trademarks? - This discussion was prompted by Vincent's question on who can use the ter= m DPDK in announcements etc. Nobody on the call was aware of any DPDK trade= marks, but that's not a definitive answer. Agreed that Mike Dolan will cons= ider trademarks in his discussions with legal representatives. If anybody w= ants to be represented in these discussions and hasn't already done so, the= y should provide the name of their legal counsel to Mike. Next Meeting: Tuesday January 17th at 3pm GMT, 4pm CET, 10am EST, 7am PST. We need to agr= ee on whether or not Governing Board meetings should be public, resolve any= remaining comments on the charter, and then discuss next steps for identif= ying membership rates, project members etc.