From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of tech-board meeting: 2022-01-26
Date: Tue, 1 Feb 2022 09:18:48 +0000 [thread overview]
Message-ID: <9998301dbd444c17ad3893dd1ccfa53b@intel.com> (raw)
Tech Board Attendees:
Bruce, Aaron, Ferruh, Jerin, Maxime, Thomas, Kevin, Konstantin, Olivier, Stephen, Honnappa, Hemant
Agenda Items
--------------
* Tech writer
* No updates on this
* Getting new program manager from LF - may need to remind on hiring Tech writer.
* UNH Statement of Work
* Needs to be closed out for 2022
* Final call for items list for UNH for coming weeks
* After this week, going to gov board
* For suggested items, either email to Aaron or add directly to doc.
* There will be review - Techboard to review once doc is cleaned up a bit.
* Current version: https://docs.google.com/document/d/1l38GZwaMuIu8hq3kMjoAHDU_LanXXTt-LYS4y7Sv4t8/edit
* GPL license files in DTS
* Working on changing license headers for files in DTS (to SPDX tags)
* Some files missing headers - will be added
* 4 - 5 files missing GPL license. These files will not be linked into applications
* Files should be reviewed and checked /approved for exceptions
* Action: Create license directory/files in DTS which will be merged into main DPDK license files once merge of DTS and DPDK is done.
* Action: For GPL scripts, refer through gov board for advice re python scripts included in other scripts.
* L3fwd in testpmd
* Reviewed previous decision.
* Confirmed nothing to be done, not to be considered for this release. Patches deferred in patchwork.
* Events
- decisions on events no longer being planned by separate marketing committe
- Tech board input is required in event planning from now on.
- in-person event is planned for Europe (Userspace 2022).
- provisionnally planned for Bordeaux, most likely in mid-September (2nd week)
* Traffic Gen
- previous discussion incomplete
- consider revisiting next time if Harry can attend
Items Noted for Reference:
--------------------------
FYI: perf thread example is now removed from repository.
FYI: ICC support is broken on next-net. May need to drop support completely. Ferruh tracking.
FYI: Discussion on ABI versioning of structs passed from libs to drivers, e.g. ethdev to net drivers
Ref: http://inbox.dpdk.org/dev/CALBAE1Po3-7KUN+WecJRDjbbYDi40mPRmVf8YTaFDyDPj-WnGQ@mail.gmail.com/T/#m2371800d0b6848b76c8666dd771de66544ebdd3a
reply other threads:[~2022-02-01 9:18 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=9998301dbd444c17ad3893dd1ccfa53b@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@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).