From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Techboard Meeting Minutes 2025-Feb-05
Date: Thu, 13 Mar 2025 16:46:06 -0700 [thread overview]
Message-ID: <20250313164606.3716e5e2@hermes.local> (raw)
Members Attending
-------------------------
Aaron Conole
Bruce Richardson
Hemant Agrawal
Jerin Jacob
Kevin Traynor
Konstantin Ananyev
Maxime Coquelin
Stephen Hemminger (chair)
Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3pm UTC.
Meetings are public, and DPDK community members are welcome to
attend. Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
Next meeting will be on Wednesday 2025-Feb-19 @ 3pm UTC, and will be
chaired by Morten.
Agenda Items
1. Video platform for up coming summit in Prague.
General consensus was that Youtube was easiest and most accessible to remote
participants. With possible backups of Slack and Discord. There is a problem
in that many of these platforms are not accessible in China.
2. Code Challenge
The survey showed that were 5 items that would be worth pursing.
- WiFi support
- Code coverage
- review and bug triaging (using AI?)
- document best practices with DPDK
- L2 learning bridge
But in order to make progress, need more involvement.
Stephen is willing to help but doesn't want to be the sole person trying
to make it happen.
3. Process issues
Aaron raised the issue that patches come to often and overload the CI
infrastructure (as well as reviewers). Will work on a draft policy
to give contributors on guidelines (once per day) and more feedback.
See "doc: Document frequency and volume limits on patches."
reply other threads:[~2025-03-13 23:46 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=20250313164606.3716e5e2@hermes.local \
--to=stephen@networkplumber.org \
--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).