From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "dts@dpdk.org" <dts@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: DTS WG Meeting Minutes 1/26/22
Date: Wed, 26 Jan 2022 15:57:10 +0000 [thread overview]
Message-ID: <edbc18fa2e2b432892324b400ea79f99@pantheon.tech> (raw)
[-- Attachment #1: Type: text/plain, Size: 3252 bytes --]
Hello folks,
The meeting minutes can be found here: https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs
And here are the meeting minutes from Jan 26th:
Attendees
* Owen Hilyard
* Juraj Linkes
* Honnappa Nagarahalli
* Lincoln Lavoie
* Lijuan Tu
* Ganapati
Agenda
* Additions to the agenda
* Review/Carry forward pending action items
* Merging DTS into DPDK
* Review additional work items
Minutes
Review/Carry forward pending action items
* Honnappa - Propose changes to DPDK to address changing the constants and printfs, refer to Lijuan's email.
* Patches in internal review, to be pushed next week.
* More exploration (of printfs) is needed.
* All - Review Owen's DTS contributions guide.
* Juraj provided comments, Owen to review, then publish the final version.
* Owen, Lijuan - Look for merging the makefile removal patch (http://patchwork.dpdk.org/project/dts/list/?series=20610)
* Honnappa - Understand how the SPDX change was done for the DPDK repo
* We understand this now, closing.
* Honnappa - Talk to techboard about files with the GPL2 license in DTS.
* Techboard notified, Hemant is fine with having the GPL2 license in DTS, but discussion is still continuing.
* Juraj - Convert the makefile build for documentation to use meson build.
* Deferred to the future, when repositories are merged.
* Owen - RFC for making the python version 3.6
* Python 3.6 is EOL. Which version to use is informed by Python version EOL, UNH lab's (and other lab's) software update policy and which version is shipped with Ubuntu stable. Going with 3.8 for now. For the future, go with a flexible approach where we won't use EOL Python versions and consider how labs update their software.
* Owen - Look at making DTS build using the common DPDK repo in addition to the existing tarball option.
* No progress.
Merging DTS into DPDK
* Are we going to integrate DTS with the DPDK build system? No resolution yet.
* Try for 22.07
* Focus on framework and test cases used in CI
* Do a deep dive on Feb 9th - identify what needs to be done and estimate the work.
Action Items
* Honnappa - Patches to DPDK to address changing the constants and printfs under development.
* All - Review Owen's DTS contributions guide, Owen to review.
* Owen, Lijuan - Look for merging the makefile removal patch (http://patchwork.dpdk.org/project/dts/list/?series=20610) in the next release.
* Owen, Lijuan - Create release notes, capture the makefile deprecation in them. Also add a notification/log to DTS runs.
* Honnappa - Continue the techboard discussion about files with the GPL2 license in DTS.
* Juraj - Postponed: Convert the makefile build for documentation to use meson build after merging the repositories or the directory structure is known.
* Owen - RFC for making the python version 3.6 done, update with version 3.8.
* Owen - Look at making DTS build using the common DPDK repo in addition to the existing tarball option.
Any other business
* Next Meeting: February 02, 2022
Regards,
Juraj
[-- Attachment #2: Type: text/html, Size: 30265 bytes --]
reply other threads:[~2022-01-26 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=edbc18fa2e2b432892324b400ea79f99@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).