From: Jerin Jacob <jerinj@marvell.com>
To: dev <dev@dpdk.org>
Cc: dpdk-techboard <techboard@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Minutes of Technical Board Meeting, 2024-November-12
Date: Thu, 8 Jan 2026 11:35:19 +0000 [thread overview]
Message-ID: <PH7PR18MB50788B9A9F939CC41AFACE71C885A@PH7PR18MB5078.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2024-November-12
Members Attending
*****************
- Hemant
- Wathsala
- Kevin
- Bruce
- Thomas
- Morten
- Stephen
- Konstantin
- Shani
- Jerin (Chair)
NOTE: The technical board meetings every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2024- Nov - 26th @3pm UTC, and will be chaired by Honnappa
# LTS Maintainer Update
- Xiaoming resigned as LTS maintainer for DPDK 23.11.
- A call for volunteers was posted on the tech board mailing list.
- Shani Peretz volunteered and was unanimously approved as the new LTS maintainer for 23.11.
- Kevin and Luca will support Shani during the onboarding process.
# Driver Maintenance Discussion
A general discussion was held regarding the current state of maintenance for the BNXT driver and
how the community can better support long-term sustainability across all drivers.
- Community Discussion
* Emphasis on maintaining a consistent quality baseline across all DPDK drivers.
* Importance of clear maintainer expectations and sufficient resources.
* Acknowledgement that hardware diversity limits full validation by subsystem maintainers.
* Alignment between vendors and community contributors viewed as essential for driver reliability.
* All core components (drivers and libraries) should follow similar quality and maintenance guidelines.
- Discussion was collaborative and focused on improving processes, not restricting or removing drivers.
- Potential improvements considered:
* Adding support-level tags in the maintainers file to increase clarity on driver support status for users.
* Updating documentation to better communicate expectations for new or evolving drivers.
# Follow-up / Action Items
- Await update from Ajit regarding the new Broadcom maintainer.
- Await Broadcom's plan for ongoing BNXT branch maintenance.
- Discuss adding support-level flags to the maintainers file.
- Consider updates to documentation or policy for driver quality expectations.
reply other threads:[~2026-01-08 11:35 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=PH7PR18MB50788B9A9F939CC41AFACE71C885A@PH7PR18MB5078.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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).