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 A7447A057A; Wed, 18 Mar 2020 10:21:04 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C683A1AFF; Wed, 18 Mar 2020 10:21:03 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 72DCE3B5; Wed, 18 Mar 2020 10:21:01 +0100 (CET) IronPort-SDR: mfcoAxi8UcaNXRasFFdHGsuFvIRzi4E+l0KmnDU3B1p+OBG6aRaRuhmGisMypHgGe5GF2kI/AU M0UkLFfniJEQ== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Mar 2020 02:21:00 -0700 IronPort-SDR: 0+2ZHu4CjoyyYSG1cLM387T+XXpkT86pBLOkch7huCNXkCvvoccduZN3yW8u800qpuHsR1GUW0 /waTxi9PgbbA== X-IronPort-AV: E=Sophos;i="5.70,566,1574150400"; d="scan'208";a="417879462" Received: from bricha3-mobl.ger.corp.intel.com ([10.251.165.47]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 18 Mar 2020 02:20:58 -0700 Date: Wed, 18 Mar 2020 09:20:53 +0000 From: Bruce Richardson To: dev@dpdk.org Cc: techboard@dpdk.org Message-ID: <20200318092053.GA1491@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dpdk-dev] Minutes of Techboard meeting 2020-03-11 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" Attendees: all tech-board members attended DPDK Scope & rte_graph Proposal -------------------------------- * As previously discussed at the last meeting rte_graph will be accepted into DPDK, but the question of what repository it is to be put into was not agreed * Concern was raised as to the amount of content in the DPDK repository, specifically: * non-hardware related functionality, i.e. pure software libs for packet processing * unused or abandoned code/libraries in DPDK * Suggestion was made that perhaps some libraries, such as rte_graph and others, should be split into a separate repo * brings back the idea of the core vs non-core DPDK * distro's want to be able to optionally not include some DPDK libraries, and this may aid that * key difficulty remains how to determine what remains in main repo and what gets split out * No consensus was reached on splitting out libraries from main repo * Decision was made that, lacking that consensus, rte_graph should not be blocked from merge to the main repo * Consensus also reached that we should always endeavour to remove any dead code from DPDK, be it unused examples, libraries or drivers. Userspace Conference and Call for Papers ----------------------------------------- * Only one DPDK event currently planned for this year: * DPDK Userspace, Bordeaux, Sept 24-25 * Draft CfP was already circulated for discussion among technical board with some discussion taking place via email * Discussion was held on the format of the conference: * Suggestion was to separate one day for user talks about how DPDK was used by applications - both OSS and proprietary * Other day (assuming 2 day conference) was to cover DPDK internals and additions * Agreement that time for an in-person technical board meeting should be built into the agenda * Thomas, on behalf of Techboard, will enquire whether event can be stretched to more than two days, e.g. 2 1/2 to account for additional user content * Techboard is happy to take on the task of reviewing and accepting/rejecting the proposals for the conference. Other Business --------------- * Reviews are requests on web page changes for the CI, replacing the community lab page with a more general one on testing: http://mails.dpdk.org/archives/web/2020-March/001346.html