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, 2022-Oct-5
Date: Tue, 18 Oct 2022 17:14:51 +0100 [thread overview]
Message-ID: <1d79ee60-ec2e-d91f-1900-c9bacd428ad4@yandex.ru> (raw)
In-Reply-To: <565c8cc8-ebfa-5e6b-3e42-e450e1b1ba67@yandex.ru>
Members Attending
----------------------
-Aaron
-Bruce
-Konstantin (chair)
-Kevin
-Maxime
-Stephen
-Thomas
NOTE: The technical board meetings are on 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-Oct-19 @3pm UTC, and will
be chaired by Jerin.
1) GB representative rotation:
Stephen Hemminger will be TB rep to GB for next 3 months.
2) Meeting management tool suggestion from Nathan.
Followed by more broad discussion about current DPDK project tools
and how convenient the are to the different parts of the community.
In particular:
- how end-users (not developers) can provide their input for new
features, existing functionality?
- bug-tacking tool improvement
- new contributors - what are the best options for them?
No specific decisions were made.
3) Meson version update for 22.11
- Decision is - let's try to go ahead with it.
AR to Bruce to ping Intel Labs team to confirm that they
will be able to deal with that.
4) License exception for GVE code from kernel (under MIT license)
- Looks ok, to follow the procedure need to apply for exception
approval from GB.
parent reply other threads:[~2022-10-18 16:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <565c8cc8-ebfa-5e6b-3e42-e450e1b1ba67@yandex.ru>]
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=1d79ee60-ec2e-d91f-1900-c9bacd428ad4@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).