From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2024-July-24
Date: Tue, 30 Jul 2024 23:36:59 +0100 [thread overview]
Message-ID: <f414130a-af72-4c35-a6c1-32ea8f31c118@yandex.ru> (raw)
In-Reply-To: <acd4be5163244f729acd61b8ddc2e1ab@huawei.com>
Minutes of Technical Board Meeting, 2024-July-24
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Jerin
-Konstantin
-Maxime
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday at:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2023- Aug - 7th @3pm UTC, and
will be chaired by Maxime
# Approved introducing git tree next-dts with Juraj Linkes
(juraj.linkes@pantheon.tech)
as a maintainer for it.
# DPDK Summit (Montreal) CFP timeline update:
- CFP Close: Wednesday, July 31 at 11:59 pm EDT (UTC-4)
- CFP Notifications: Tuesday, August 6
- Schedule to be announced: Wednesday, August 7
# DPDK Summit APAC (Bangkok)
- videos are available on DPDK YouTube channel:
https://www.youtube.com/channel/UCNdmaRMwOBu0H8a7DdXAT9A
# Pending Process on Robin's Grout Router
(https://github.com/rjarry/grout/tree/main) as DPDK hosted project
- Previous Approval: Hosting the Grout on dpdk.org was approved in a
previous TB meeting.
- Next Steps:
1) The final approval process requires GB approval.
2) As the next GB representative from TB, Konstantin Ananyev presented
this information to GB.
3) GB to vote over email and come back with final approval.
next parent reply other threads:[~2024-07-30 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <acd4be5163244f729acd61b8ddc2e1ab@huawei.com>
2024-07-30 22:36 ` Konstantin Ananyev [this message]
2024-07-30 23:03 ` Stephen Hemminger
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=f414130a-af72-4c35-a6c1-32ea8f31c118@yandex.ru \
--to=konstantin.v.ananyev@yandex.ru \
--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 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).