From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id F22F3A00E6 for ; Thu, 18 Apr 2019 22:41:23 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 76DB31B920; Thu, 18 Apr 2019 22:41:22 +0200 (CEST) Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id C16D81B908; Thu, 18 Apr 2019 22:41:21 +0200 (CEST) Received: from lfbn-lil-1-768-100.w81-254.abo.wanadoo.fr ([81.254.99.100] helo=droids-corp.org) by mail.droids-corp.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hHDsx-0005Cg-4k; Thu, 18 Apr 2019 22:43:56 +0200 Received: by droids-corp.org (sSMTP sendmail emulation); Thu, 18 Apr 2019 22:41:17 +0200 Date: Thu, 18 Apr 2019 22:41:17 +0200 From: Olivier Matz To: dev@dpdk.org Cc: DPDK Techboard Message-ID: <20190418204117.5mdmn2xjrt6tjn5n@platinum> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) Subject: [dpdk-dev] DPDK techboard minutes (2019-04-10) 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" Message-ID: <20190418204117.58y1fDyqoxMji0sI-wjmjfqrTF-nWLpAHx68OBvj8xU@z> Hi, Here are the meeting notes of the DPDK technical board meeting held on 2019-04-10. Attendees: - Bruce Richardson - Ferruh Yigit - Hemant Agrawal - Jerin Jacob - Konstantin Ananyev - Olivier Matz - Stephen Hemminger - Thomas Monjalon 1) DPDK development process and tools survey ============================================ Reference: https://mails.dpdk.org/archives/dev/2019-March/126114.html The objective of the survey is to detect problems (if any) in our current process. - The survey is now closed. - Unfortunately the number of received responses is low compared to the number of active DPDK developers. - The answers and feedback will be gathered and summarized by mail. - There will be a Q&A session on this topic at next Europe DPDK summit. 2) DPDK API Stability discussion ================================ Reference: https://mails.dpdk.org/archives/dev/2019-April/128969.html - Following the discussion on the ML, there is a consensus that API/ABI stability is a direction where the DPDK project should head for. - Adding automated tools to check API/ABI stability is a good first step. Here is a list of ABI checker tools: - ABI Laboratory: https://abi-laboratory.pro/index.php?view=timeline&l=dpdk - https://sourceware.org/libabigail - https://lvc.github.io/abi-compliance-checker - The current dpdk tool, validate-abi.sh, is based on abi-compliance-checker. - Patches like this one proposed by Stephen Hemminger should be generalized to other parts of DPDK (everything that is not rx/tx path): http://patches.dpdk.org/project/dpdk/list/?series=4248 - An "ABI/API stability" item will be added to techboard recurring topics. - The documentation (guides/contributing/versioning, guides/contributing/design) and website (including roadmap) should be updated to highlight and explain the intent (Ray proposed himself). - No calendar/deadlines was decided, let's discuss it again at next techboard meeting. 3) SPDX licenses ================ There are still some old license headers in Intel driver base code, they will be replaced by new shared code drops.