From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: DPDK Techboard <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2022-Nov-16
Date: Mon, 16 Jan 2023 15:32:54 +0100 [thread overview]
Message-ID: <effa6156-d2df-85a4-eb4b-49adcb6d5378@redhat.com> (raw)
Minutes of Technical Board Meeting, 2022-Nov-16
Members Attending
-----------------
∘ Maxime Coquelin
∘ Thomas Monjalon
∘ Kevin Traynor
∘ Hemant Agrawal
∘ Bruce Richardson
∘ Konstantin Ananyev
∘ Jerin Jacob
∘ Honnappa Nagarahalli
∘ Aaron Conole
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 2022-Nov-30 @3pm UTC, and will
be chaired by Stephen
1) Governing Board updates
- Nathan provided an update about the Governing board chair election.
Rashid Khan (Red Hat) has been voted in as the new chair.
- A vice-chair role creation is being drafted.
2) Techwritter hiring updates
- One candidate has been identified, compensation discussions to be
engaged.
3) DPDK blog update
- Governing boards minutes are now placed in a dedicated section.
4) MIT license exception
- Exception for GVE base driver has been approved
- Generic approval process under discussions at the Governing board
level, waiting for legal advice.
5) BBDEV tree maintainership
- Crypto tree will no more pull BBDEV patches.
- Techboard voted in for a dedicated repo creation, with Maxime
Coquelin maintaining it.
6) LTS maintenance for 2023
- Kevin Traynor sent a mail to LTS maintainers and Techboard members to
collect feedback for 2023 LTS maintenance.
reply other threads:[~2023-01-16 14:33 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=effa6156-d2df-85a4-eb4b-49adcb6d5378@redhat.com \
--to=maxime.coquelin@redhat.com \
--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).