From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4A56BA00C3; Thu, 20 Jan 2022 10:11:10 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BEB5C426D8; Thu, 20 Jan 2022 10:11:09 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id A671440042; Thu, 20 Jan 2022 10:11:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1642669868; x=1674205868; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Z6MKzzsch1iF+1acRilOw/x6hJsT8/ef4oOQ+tnBwHM=; b=LDPyPPeiWPURymFsoTL4ZyzVJga8dOEYrmiYKSHClIfUBk1tVJrVVewG eWmcxQuT8IyfFTlC91ipFIXqGNZg5+inkC+fQhODXN6Dlpt8eIVxyemRJ rPtug/QJBlAaP5EcDy4r6JZKdG40wHJreiZFqrYtcVif+iHkLrcSL72fu I5aShTqLl1UzpvX+RKjfWAsimTFqI6+B7MWHAfzfgq+DZB0Edc7EDiJBh el/3Q55kvJPbUGD2Xv/4TGBbF7F0mpQIKFL2cXAtVAoRSlo+6wNkORjPM 6XpXaEjkj/ZygjtFOHOZOh/mM2Z0DxPRn27YUSUSQPRzyilcsn5bECO6M Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10232"; a="232670928" X-IronPort-AV: E=Sophos;i="5.88,302,1635231600"; d="scan'208";a="232670928" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jan 2022 01:11:06 -0800 X-IronPort-AV: E=Sophos;i="5.88,302,1635231600"; d="scan'208";a="694129035" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.29.19]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 20 Jan 2022 01:11:04 -0800 Date: Thu, 20 Jan 2022 09:11:01 +0000 From: Bruce Richardson To: Honnappa Nagarahalli Cc: "dev@dpdk.org" , "dts@dpdk.org" , Lijuan Tu , Lincoln Lavoie , Juraj =?utf-8?Q?Linke=C5=A1?= , Owen Hilyard , nd Subject: Re: DTS WG meeting minutes - 1/12/22 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, Jan 19, 2022 at 09:25:50PM +0000, Honnappa Nagarahalli wrote: > Hello, Please find the minutes below. The history of minutes is at [1]. > > Thanks, Honnappa > > [1] > https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit?usp=sharing > > Attendees: -------------- Honnappa Nagarahalli Owen Hilyard Lijuan Tu Ali > Alnubani Vladislav Grishenko > > Agenda: ---------- 1) Review/Carry forward pending action items 2) > Rotating the chairperson for hosting the meeting 3) Makefile build > removal from DTS 4) DTS files license to change to SPDX license 5) How do > we merge the DTS into DPDK - directory structure, compilation time, > documentation (tooling and directory structure for online documentation) > 6) Build DTS documentation using Meson > > Minutes: ----------- 1) The chairperson hosting the meeting will be > rotated going forward. As of now it will be shared between Honnappa, > Juraj, Lijuan, Lincoln (?), Owen. The rotation will be done in the > alphabetical order of the first name. However, as agreed, the meeting on > 1/18 would be hosted by Owen. 2) All the stable releases use Meson > build. So the makefile build support from DTS can be removed. Makefile > removal patch is in the DTS community review 3) A quick scan reveals that > DTS has some files with GPL2 license. A deeper look is required. Is there > any process we need to follow to change to SPDX? Decided to follow up > with the DPDK community. 4) Merging DTS into DPDK - Is a bigger > discussion. Need to agree and fix the python version to use. Differed the > discussion to future time as it needs more progress in DTS. Will be > discussed when Lincoln and Juraj are available 5) The DTS user guide and > DTS test plans are being built using makefile. This needs to be changed > to using meson build. > For this point #5, not knowing the details here, but at a high level, I wonder if that really needs to be done, if the existing make build of the doc works ok. As the plan is to move DTS into DPDK repo, presumably the documentation would also move, and at that point it can just reuse the DPDK meson build infrastructure for documentation. Is there a compelling reason to invest in doing this change earlier? For docs rather than code, moving to meson doesn't generally give much benefit - the only reason we did so in main DPDK repo was consistency with everything else. /Bruce