From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2049510C90 for ; Wed, 21 Dec 2016 16:55:39 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP; 21 Dec 2016 07:55:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,384,1477983600"; d="scan'208";a="1074872050" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga001.jf.intel.com with ESMTP; 21 Dec 2016 07:55:36 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by IRSMSX103.ger.corp.intel.com ([169.254.3.124]) with mapi id 14.03.0248.002; Wed, 21 Dec 2016 15:55:35 +0000 From: "O'Driscoll, Tim" To: "moving@dpdk.org" Thread-Topic: Minutes from "Moving DPDK to Linux Foundation" call, December 20th Thread-Index: AdJbolF5UXefy2MsSWCd3XgAk6TdOQ== Date: Wed, 21 Dec 2016 15:55:34 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA72299670@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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDk3NGE3YzYtNDA2OC00ODYxLThkOWYtNDcxZmY1MzQwZmU4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJtbVdobTBiamRObTFvYkdFRG90K2VOOElYTW5seG5ZSmJsWjEyOCtVVXhvPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] 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, December 20th 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, 21 Dec 2016 15:55:40 -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), Hemant Agrawal (NXP), Jan Blunck (Brocade),= Jaswinder Singh (NXP), John McNamara (Intel), Keith Wiles (Intel), Kevin T= raynor (Red Hat), Olga Shern (Mellanox), Stephen Hemminger (Microsoft), Tho= mas Monjalon (6WIND), Tim O'Driscoll (Intel), Vincent Jardin (6WIND), Yoni = Luzon (Mellanox). Note that there may have been others, but as people joine= d at different times it was difficult to keep track. 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 Technical governance, including info on Maintainers and sub-trees: http://d= pdk.org/doc/guides/contributing/index.html & http://dpdk.org/dev. 1. Status of charter doc: - The only remaining comment on the doc is Matt's suggestion for a Contribu= tor member level. We need both Mike Dolan (who opposes this) and Matt prese= nt on the same call to disposition this. - People should conduct a final review of the charter before the next meeti= ng (Tuesday 10th Jan). Issues can either be raised as comments in the doc o= r raised on the moving@dpdk.org mailing list. Please refer to the previous = discussion/resolution if you're raising an issue that's been covered before= so that we don't simply repeat previous discussions 2. Technical Governance: - John and Thomas described the recent changes to the Contributor's Guideli= nes which now includes a section on Maintainers and Sub-Trees. See http://d= pdk.org/doc/guides/contributing/patches.html#maintainers-and-sub-trees. Aga= in, people should review and raise any additional comments/concerns on the = dev@dpdk.org mailing list. 3. Technical Board: - Ed asked what happens if the Technical Board make a decision on a dispute= d patch set but a Maintainer/Committer refuses to comply with that decision= . In reality, it's not expected that this situation will occur, but I've ad= ded text to section 3.2.1 point iv to clarify that the Tech Board has the r= ight to make any changes necessary to enforce its decision in this situatio= n. - We discussed the need to review membership of the Tech Board. Proposals f= or how to do this included: a) ask the Tech Board to review and update its = own membership; b) define some membership criteria and hold a vote. We didn= 't reach a definite conclusion on this. I'd suggest that we ask the current= Tech Board to determine the most efficient process to update its membershi= p. I'll submit a request to techboard@dpdk.org to ask that they do this and= that they provide an update at a future meeting. 4. Membership: - Ed's guidance from FD.io was that the process of recruiting members could= take up to 6 months. We have done a lot of prep work during these meetings= so we hope to do it faster than this and will target 3 months. This would = allow for a project launch in Q2. We'll use our first meeting in Jan to wor= k out the next steps on this. - Potential member companies should make sure that their decision-makers fo= r joining and funding DPDK are aware of these discussions and of the status= of the charter doc. Next Meeting: We'll resume again on Tuesday January 10th at 3pm GMT, 4pm CET, 10am EST, 7= am PST. We'll cover any additional (and hopefully final) comments on the ch= arter, and discuss next steps for determining project members.