From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2026-September-16
Date: Wed, 30 Sep 2026 11:06:13 +0100 [thread overview]
Message-ID: <c3590dee-d7ed-4792-9991-59570406d8da@redhat.com> (raw)
Minutes of Technical Board Meeting, 2026-September-16
Members Attending: 10/10
- Aaron Conole
- Bruce Richardson
- Hemant Agrawa
- Jerin Jacob
- Kevin Traynor (Chair)
- Konstantin Ananyev
- Maxime Coquelin
- Morten Brørup
- Stephen Hemminger
- Thomas Monjalon
NOTE: The Technical Board meetings take place every second Wednesday at
3 pm UTC
on
https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
The next meeting will happen on Septemeber 30 and will be chaired by
Konstantin Ananyev.
# DPDK Event
- 2027 event was discussed at the governing board
- Investigating having an event in Brussels on the 2 days before fosdem
# DPDK CVE
- An update on Security process and CVEs was provided by various people
# Enquiry about LF and OFAC list
- Can request LF to give guidance if there are any clarifications required
reply other threads:[~2026-09-30 10:06 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=c3590dee-d7ed-4792-9991-59570406d8da@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