From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-05-05
Date: Thu, 13 May 2021 11:40:13 +0100 [thread overview]
Message-ID: <451e2dfb-8422-136d-c29e-71e3626b5471@redhat.com> (raw)
Minutes of Technical Board Meeting, 2021-05-05
Members Attending
-----------------
-Aaron
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin
-Kevin (chair)
-Konstantin
-Maxime
-Olivier
-Stephen
-Thomas
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 2021-05-19 @3pm UTC, and will be
chaired by Olivier.
1) New LTS maintainer
~~~~~~~~~~~~~~~~~~~~~
Xueming(Steven) Li <xuemingl@nvidia.com> is voted to be a new LTS
maintainer. He will initially help Luca with 20.11 LTS.
2) Gov board meeting updates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DPDK NA event is planned.
DPDK Userspace is tbd on format and/or location.
3) Tech Board Membership Policies
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gov board wants tech board to better document the current policies for
membership.
Long discussion on many aspects of the makeup of the tech board.
Discussed about the historical growth, role based membership, elected
membership, coverage for multiple architectures and OSs, technical
governance in other projects etc. NOTE: the tech board meeting is open
for all to join and give input on all agenda items.
As a first step Hemant will better document the current procedures for
review. Bruce suggested in the short term to tighten up on some areas
such as as max tech board size. These can be further identified after
Hemant's write up.
Stephen has been looking at aspects of governance models from other
projects which could be adopted in the medium term.
4) next-net maintainership feedback
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ferruh would like to get some feedback on next-net maintainership and if
there are any improvements he can make. He may send out a short survey.
5) LTS backports
~~~~~~~~~~~~~~~~
New drivers/features should be merged into main repo. They should not be
targeted only for LTS branches only. There are some patches to improve
the documentation of what can be backported in progress.
6) Crypto maintainership
~~~~~~~~~~~~~~~~~~~~~~~~
There is no backup maintainer for the crypto tree for Akhil since he
took the leading role. Requesting companies involved in crypto to
nominate someone.
reply other threads:[~2021-05-13 10:40 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=451e2dfb-8422-136d-c29e-71e3626b5471@redhat.com \
--to=ktraynor@redhat.com \
--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).