From: Aaron Conole <aconole@redhat.com>
To: techboard@dpdk.org, dev@dpdk.org
Subject: Meeting Minutes, March 04, 2026
Date: Tue, 14 Apr 2026 14:31:27 -0400 [thread overview]
Message-ID: <f7to6jl9yww.fsf@redhat.com> (raw)
* TB Attendees
** Aaron Conole
** Thomas Monjalon
** Stephen Hemminger
** Jerin Jacob Kollanukkaran
** Bruce Richardson
** Kevin Traynor
** Maxime Coquelin
Agenda
* regexdev
** The discussion concluded that using a software solution is more
efficient than using hardware, because hardware is quite limited for
this work and CPUs are now outperforming dedicated hardware.
** Question about dropping support
*** We discussed what happens with vendors, noting that vendors are not
currently providing support.
*** We considered the appropriate timing to drop support, questioning
whether September would be an acceptable date.
*** The decision to drop support is reversible if needed.
** It was decided that a deprecation notice must be sent out, well
publicized via mailing lists, release notes, and other channels.
*** Thomas will ask Ori to send out the deprecation materials.
* gpudev
** Maintenance appears to be lagging and requires attention, which
includes adding examples.
** The current recommendation is to leave everything unchanged for the
time being.
* Conference Update(s)
** The Call for Papers (CFP) review is scheduled for the 10th of March
at 11am EST.
*** The submissions received thus far look good.
** Nathan gave timing and logistics updates for the tech board and gov
board discussions.
** We requested a spreadsheet containing the abstracts and scores.
* Project Updates
** Nathan will be on leave; the interim contact is Yarille Ortiz
(yortiz@linuxfoundation.org).
** Slack Pro
*** Feature: The archives are searchable.
* Bugzilla triage
** Stephen is writing Python scripts to gather information.
** Thomas has begun work on a dashboard (https://issues.dpdk.org) that
ties together CI, Bugzilla, minutes, and development.
** We plan to discuss this with the government board and tech board.
** Features like:
*** A "wishlist" filtering option.
*** A to-do list.
*** The possibility of adding milestones to Bugzilla and filtering them here.
*** The use of an API key to assign bugs to maintainers.
** Considerations for the next meeting
*** Workflow for wishes.
*** Workflow for beginner tasks.
* AI Review status
** Current items:
*** Checkpatch should not serve as a gating step because it often
generates false positives.
*** Build failures should remain a gating step.
** AGENTS.md
*** The file still contains a large number of tokens, but we are working
on trimming it down.
*** Stephen is identifying more targeted prompt adjustments.
** UNH needs a final gating policy and a process for submission.
* Followups (things like checkpatch, maintainer list, etc.)
** Thomas scrubbed the maintainers list for inactive individuals.
reply other threads:[~2026-04-14 18:31 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=f7to6jl9yww.fsf@redhat.com \
--to=aconole@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.