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 C055A2A5D; Fri, 17 Feb 2017 11:22:12 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Feb 2017 02:22:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,171,1484035200"; d="scan'208";a="1110700422" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by fmsmga001.fm.intel.com with ESMTP; 17 Feb 2017 02:22:10 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.77]) by IRSMSX151.ger.corp.intel.com ([169.254.4.20]) with mapi id 14.03.0248.002; Fri, 17 Feb 2017 10:22:10 +0000 From: "Richardson, Bruce" To: "dev@dpdk.org" CC: "techboard@dpdk.org" Thread-Topic: DPDK Technical Board Meeting, 2017-02-15 Thread-Index: AdKJB42XSYgvIdRfTX63CY1CbPC8eg== Date: Fri, 17 Feb 2017 10:22:09 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B035B99794@IRSMSX103.ger.corp.intel.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWYzYTBlMWYtMWRkNS00ZTY5LWE5OWQtMWUxYzNkNDYwMDdhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJtZHUxWEtEenMrejVDd1pGT2tcL2o2UlRnQXFleDhWMXNxMVhNekV0dk1PUT0ifQ== 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-dev] DPDK Technical Board Meeting, 2017-02-15 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: Fri, 17 Feb 2017 10:22:13 -0000 A meeting of the DPDK technical board was held last Wednesday, 2017-02-15. = Below are the meeting minutes. =20 Please note that future meetings will be open to all to attend, as describe= d below. The next meeting is planned for March 1st, and any topics to be re= ferred to the tech board for discussion at that meeting should be emailed t= o techboard@dpdk.org by February 26th at the latest. Regards, /Bruce ------------------------------------------------------------------ Attendees: Hemant Agrawal, Konstantin Ananyev, Jan Blunck, Stephen Hemminger, Jerin Ja= cob, Yuanhan Liu, Olivier Matz, Thomas Monjalon, Bruce Richardson Agenda and Notes: 0. General Meeting Admin * Bruce Richardson volunteered to chair this meeting (Meeting chair was pr= eviously agreed to be a rotating role.) * Olivier Matz volunteered to chair the next meeting * At each future meetings, the chair for the next meeting will be decided = and that person also has the responsibility of preparing the meeting agenda= ahead of time. * Next meeting was agreed to be at the same time in two weeks - 1st March = @ 3pm UTC (4pm France, 11pm PRC, 7am US Pacific).=20 - Olivier to send a reminder with agenda a few days in advance. 1. Welcome new members to the board, and answer any questions they had abou= t technical board operations. * Hemant, Jan and Yuanhan were welcomed, but had no questions on tech boar= d at this point. 2. Making meetings public * LF charter for DPDK specifies that meetings of the techboard should be p= ublic * Decision made to continue to hold meetings on #dpdk-board channel on IRC * Meetings will be announced ahead of time: - In minutes of previous meeting - Via separate email a couple of days before the meeting * Anyone interested in the board meeting can join the IRC channel and make= their contribution. * Only items on the agreed agenda to be discussed. Any topics to be covere= d must be sent in advance to techboard@dpdk.org 3. Update board charter on website * The website details of the Tech board is out of date, both membership an= d its mode of operation and scope * Thomas has already sent one proposed update out via email, in the form o= f patch to the website, and Hemant has already provided one comment * Thomas to send out a new draft, and all tech board members to comment or= ack it to signal agreement. * Update won't be applied until all members ack.=20 * If not agreed before next meeting, should be discussed at that meeting 4. Issue of review and timely feedback * Discussion focused on review of patches for existing DPDK components/lib= raries * Agreed that patch maintainers are primarily responsible for accepting pa= tches in their area, and need to ensure sufficient reviews are done * Once patch has been sufficiently reviewed, the maintainer should ack the= patch * Any patches which have been acked by the maintainer, and which have no s= ubsequent issues raised with them, should be automatically merged to the re= levant tree after 2 weeks. - in case where the ack is received less than 2 weeks before a merge d= eadline, the point at which it can be automatically merged is 2 days before= the deadline - To make a release, a patch must be acked by the maintainer at least = 2 days before the merge deadline. * If not merged at the automatic-merge deadline itself, e.g. unavoidable d= elay by committer, any subsequent feedback received should be considered "t= oo late", and must be addressed by a follow-on patch, rather than via a rev= ision of the original submission. * Trivial patches may be merged sooner, or without maintainer ack, at the = tree committers discretion. 5. Accept and review new libraries * Discussion begun on this topic, but no consensus reached before time ran= out * Most members felt this topic was closely tied to the "scope" of DPDK as = a project * Discussion to continue over email, and to be discussed at the next meeti= ng if not resolved before then. Agenda Topics Not Covered: * Community questions/issues * Any action for some old patches/threads? Action Summary: * Olivier to prepare agenda for next meeting, and send out reminders * Thomas to send revised draft of website update for tech board membership = etc. NEXT MEETING: * 2017 - 03 - 01 @ 3pm UTC