From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Tech Board Meeting Minutes - 2024-Nov-27
Date: Mon, 23 Dec 2024 08:38:05 +0000 [thread overview]
Message-ID: <PAXPR04MB9328B0FFE7B6FDB8C6C49DD389022@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <PAXPR04MB93289EA59C00B0C6EF8210BC893E2@PAXPR04MB9328.eurprd04.prod.outlook.com>
Members Attending
-------------------------
Bruce Richardson
Hemant Agrawal
Jerin Jacob
Kevin Traynor
Maxime Coquelin
Morten Brørup
Stephen Hemminger
Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3pm UTC. Meetings are public, and DPDK community members are welcome to attend. Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
Next meeting will be on Wednesday 2024-Dec-12 @ 3pm UTC, and will be chaired by Kevin Traynor
Agenda Items
1. PVS Studio reported errors.
- Trial license is available.
- Post GB approval, we can list them as one of the tools for DPDK code sanity check.
- DPDK want them to be available as CI
2. License exception for UAPI files
-This is not limited to one file but a list of files.
-Need to discuss it via mailing list. Maxime will share the document.
3. Code Challenge
- Stephen prepared a excel sheet for the list of topics. He will share it.
- We can have award per stage kind of model.
- He will also work with LF/Nathan to announce the event.
- Mentors/owners need to be assigned for each topic and priorities.
4. 2025 Priorities
- Nathan requested the TB members to share their priorities.
5. Driver crc flag.
- Very poorly documented. Need volunteer to rework it.
6. New member in security-prerelease mailing list
- It was discussed and voted to add Huawei member to the list.
parent reply other threads:[~2024-12-23 8:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <PAXPR04MB93289EA59C00B0C6EF8210BC893E2@PAXPR04MB9328.eurprd04.prod.outlook.com>]
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=PAXPR04MB9328B0FFE7B6FDB8C6C49DD389022@PAXPR04MB9328.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@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).