From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of DPDK Technical Board Meeting, 2025-03-05
Date: Thu, 13 Mar 2025 15:51:38 +0100 [thread overview]
Message-ID: <5321615.eFTFzoEnKi@thomas> (raw)
Members Attending: 10/11
- Aaron Conole
- Bruce Richardson
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Morten Brørup
- 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
1/ DPDK Summit in Prague
The CFP has been extended by a week.
A good amount of proposals were submitted.
The techboard meeting will be in Prague at 4pm, May 7.
A joint meeting both boardswill happen at 7pm the same day.
2/ Board Initiatives
The 3 initiatives about cloud, security and AI need more efforts.
We may try to work on them with some students mentored by their professors.
The next step is to find some universities to work with.
3/ Governing Board
The techboard can propose topics to be discussed for the next govboard meetings.
4/ Code Challenge
The topics are chosen but the format is not decided yet.
It is proposed to progress on the format and organization
with the help of a spreadsheet, including votes and decisions.
We should require at least one mentor per topic.
5/ Contribution Policy
Aaron proposed a policy to improve participation on the mailing-list,
reduce the noise, and help the CI workload.
The RFC is sent:
https://patches.dpdk.org/project/dpdk/patch/20250305013351.2209789-1-aconole@redhat.com/
6/ Grout Testing
Patrick (UNH) will check with Robin what is needed to start testing Grout in the lab.
It is suggested that a weekly testing may be reasonnable.
We'll decide how much to invest (effort and machine time) in it during the next meeting.
reply other threads:[~2025-03-13 14:51 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=5321615.eFTFzoEnKi@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;
as well as URLs for NNTP newsgroup(s).