From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B5595A0613 for ; Fri, 27 Sep 2019 16:03:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 77B701BE9C; Fri, 27 Sep 2019 16:03:02 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id E31801BE9B; Fri, 27 Sep 2019 16:03:00 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Sep 2019 07:02:59 -0700 X-IronPort-AV: E=Sophos;i="5.64,555,1559545200"; d="scan'208";a="202020438" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.2.75]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Sep 2019 07:02:58 -0700 Date: Fri, 27 Sep 2019 15:02:56 +0100 From: Bruce Richardson To: dev@dpdk.org Cc: techboard@dpdk.org Message-ID: <20190927140255.GA1865@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2019-09-25 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Members Attending ----------------- Bruce (chair) Ferruh Hemant Jerin Konstantin Maxime Stephen Thomas NOTE: The technical board meetings every second Wednesday on IRC channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend. NOTE: Next meeting will be on Wednesday 2019-10-09 @3pm UTC, and will be chaired by Ferruh. Summary of meeting: ------------------- 1. Removal of examples (standing agenda item): Bruce reported that he is working on this, with a patchset in progress for submission upstream shortly 2. SPDX licenses (standing agenda item): Hemant provided an update on the gaps to be closed for achieving use of SPDX tags alone (i.e. no license text in files) in 19.11. Key gaps: * Issue identified with pmdinfogen using GPL derived code, meaning it needs a license exception. Tech board has approved the exception and the request will now be passed to the governing board for final approval. Thereafter an update will be made to the file "license/exceptions.txt" in the DPDK repo * Two drivers and various miscelaneous files are missing license header updates. Hemant and Stephen will work together to produce complete list of files needing update and will ping the maintainers of the drivers in question to see if they can get a mass update from them. 3. ABI Policy Discussion Following Userspace: Ray Kinsella has provided an update via email on the output of the discussions at userspace. Discussion followed on how ABI breaks are to be managed, including use of staging trees, as well as discussion on the releases for which the ABI policy will be new complied with. Also discussed was allowable changes for 19.11 in advance of the policy coming into effect. At the end of the discussion a number of key proposals were agreed upon: 1. New DPDK ABI policy sent and discussed previously is approved for use in a future DPDK release. [1] 2. DPDK 19.11 release will remain targetted at 19.11 and will not be postponed to a 19.12 release because of ABI changes. 3. The new ABI policy will take effect from 19.11 release, meaning that DPDK 20.02 and 20.05 releases must be ABI compatible with the 19.11 release. The decision to introduce policy from 19.11 may be reviewed at a future techboard meeting in advance of the 19.11 release, if maintainers/contributors identify a serious issue that requires additional changes to the existing ABI ahead of stabilization, and which cannot be done in the 19.11 timeframe. ** It is therefore STRONGLY RECOMMENDED by the technical board, that all maintainers, committers and contributors, assess the impact of the new ABI policy on their planned work for next year, and flag any major issues to the technical board ahead of the 19.11 release.** 4. Technical board composition. Discussion of adding new members to the technical board was not possible at the meeting due to time constraints. This will be discussed by the board over email, and any updates to the technical board membership will be sent out to the community via email once the discussion has concluded. [1] http://patches.dpdk.org/project/dpdk/list/?series=6524