From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2025-June-11
Date: Fri, 13 Jun 2025 10:48:28 +0100 [thread overview]
Message-ID: <8782e9dd-1df3-4a12-a24f-dc16352deced@redhat.com> (raw)
Minutes of Technical Board Meeting, 2025-June-11
Members Attending
-----------------
-Aaron
-Bruce
-Jerin
-Kevin
-Morten
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday at
https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2025- June - 25th @3pm UTC, and
will be chaired by Maxime.
1) MACB Driver Enablement (Stephen)
- Better to take pmd when the kmod is approved
- Do we still want to allow kernel modules ? perhaps if it is strictly
required for a vendor
2) AI meeting notes (Aaron)
- AI companion will be used to summarize techboard meetings
- This will be used to help minute taker compose summary to send out
- AI: Kevin contact meeting owner (Nathan) about this
3) github AI for code reviews (Aaron/Jerin)
- sourcery-ai may be able to help with code reviews
- It will require new branches being created with PRs on github
- Preference not to do that in existing dpdk github repo
- AI: Jerin will propose a workflow
4) ethdev maintainer (Thomas)
- There is need for more help with ethdev
- Other areas also require maintainers
- An email will be sent on announce to advertise
- AI: Kevin to draft email for review
5) ABI stability (Previous meeting)
- Proposal to only guarantee ABI stability on LTS minor releases
- Will need to ensure that ABI breaks are still flagged during reviews
- This will need to be discussed more. Topic for US summit.
6) US summit (Stephen)
- AI: Kevin request Nathan to give an update at next techboard
reply other threads:[~2025-06-13 9:48 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=8782e9dd-1df3-4a12-a24f-dc16352deced@redhat.com \
--to=ktraynor@redhat.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).