From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of DPDK Technical Board Meeting, 2026-02-18
Date: Wed, 04 Mar 2026 16:17:01 +0100 [thread overview]
Message-ID: <4728809.Us1k9K0G1Y@thomas> (raw)
Members Attending: 8/10
- Aaron Conole
- Bruce Richardson
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Morten Brørup
- Stephen Hemminger
- Thomas Monjalon (Chair)
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 March 4 and will be chaired by Aaron Conole.
1/ Summit CFP status
Decided to extend for one more week (until March 1).
2/ Reviewer / Contributor campaign
Ben Thomas is launching a new marketing campaign to encourage code contributions and reviews.
The website shows how quickly it is possible to be involved.
There is also an AI chat to assist in the process.
3/ AI review of existing code
The AI tools (especially Claude) can produce interesting bug reports.
The main challenge is how/where to report hundreds of issues from these tools?
Bugzilla does not fit well as it is more dedicated to issues found by humans.
Stephen proposed to publish AI reports on a static web page.
It raised the question of Bugzilla triage and maintenance.
We can send more reminders about open bugs.
A new tool could help for this maintenance work.
reply other threads:[~2026-03-04 15:17 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=4728809.Us1k9K0G1Y@thomas \
--to=thomas@monjalon.net \
--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