From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>
Subject: Minutes of Technical Board Meeting, 2023-August-23
Date: Thu, 12 Oct 2023 00:54:09 +0000 [thread overview]
Message-ID: <DBAPR08MB5814FDAB1B74D3D646BFAEE198D3A@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2023-August-23
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Honnappa (Chair)
-Jerin
-Kevin
-Maxime
-Stephen
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 2023-September-6 @3pm UTC, and will be chaired by Konstantin
Dublin DPDK submit
---------------------------
1) Tentative TB Agenda for Sep. 11th
a. General discussion from all tech board members about more efficient ways to split the work up and assign it in the future.
b. Discussion led by Aaron on the possible automation of patches in the future - pros? Cons? Worth implementing? Best process if this route is pursued.
c. Thomas: Possible change in the number of tech board members overall. Do we want more people? Less? Grow the TB or expand it? Specific individuals who wish to join or leave the TB within the next year?
d. Jerin: Internal review process: how to accelerate and/or improve this - more comments, addressing/responding to these comments, etc.
e. Aaron: improvements in use of lab resources by maintainers and committers - additional branches, etc.
Action Item: Nathan and Aaron to revisit the wording of #2 and #5.
2) In person registrations at 70 and virtual registrations at 65.
3) AV ownership assigned to an external firm. Nathan will have a meeting to discuss the details further.
4) The community dinner (scheduled for Sept 12th) venue changed to Brewdog restaurant.
Ring library optimizations
----------------------------------
1) rte_ring data is not ready yet as more changes are being tried out at Arm
UNH lab testing discussions
------------------------------------
1) The community has not received updates from Intel lab for the last 2 weeks.
2) Update from John McNamara. The lab had some attritions. The tests are still happening but the reports are not being sent out. Current projection is to get back to sending the reports in another week.
3) UNH lab might not be covering all the test cases Intel lab covers. There was a general consensus (no voting done) on bridging this gap.
a. The gap seems to be HW platforms, compilation flags and test suites
Action Item: Patrick Robb to study the gap and bring it up for a discussion at Dublin (Does this need to be on Techboard agenda for Dublin?). Aaron to reach out to John McNamara to understand more details about Intel Lab.
reply other threads:[~2023-10-12 0:54 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=DBAPR08MB5814FDAB1B74D3D646BFAEE198D3A@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
/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).