From: Ferruh Yigit <ferruh.yigit@intel.com>
To: DPDK Techboard <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-02-10
Date: Mon, 22 Feb 2021 08:57:05 +0000 [thread overview]
Message-ID: <34a49e2a-0154-1578-8b91-37d02549e099@intel.com> (raw)
In-Reply-To: <ee2cc636-8b87-4cce-d459-d19b5dc234d3@intel.com>
Minutes of Technical Board Meeting, 2021-02-10
Members Attending: 12/12
- Aaron Conole
- Bruce Richardson
- Ferruh Yigit (Chair)
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
NOTE: The Technical Board meetings take place every second Wednesday
on https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
NOTE: Next meeting will be on Wednesday 2021-02-24 @3pm UTC,
and will be chaired by Hemant.
#1 Asia DPDK Event (www.dpdk.org/event/dpdk-summit-apac-2021/) status
* CFP notifications are sent to speakers
* Waiting for review/approval from the technical board for the schedule
#2 Documenting criteria on adding/removing members to technical board
* Thomas will prepare a draft to be reviewed by technical board
#3 Community lab
* There is a request from technical board to have a daily coverage. This
coverage is mainly to be able to get a response to lab issues within a
week day, instead of waiting a few days before someone looks to it. Request
is not full time work for every day
* Testing lead, and other users that testing lead thinks necessary, must have
some level of permissions and control in the lab infrastructure to be able
to response to the issues
* Aaron will document the testing leader role details
#4 Testing requirement for new PMDs
* New PMDs need to send test report at least for the first release that the
driver is added
* Ferruh will send a process update patch
#5 DMARC on mailing list
* This is impacting email delivery from dpdk.org, Ali already sent a follow
up email describing the problem and with some possible solutions
* Ali/Thomas will share the proposals with more detail to vote on them
offline
parent reply other threads:[~2021-02-22 8:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ee2cc636-8b87-4cce-d459-d19b5dc234d3@intel.com>]
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=34a49e2a-0154-1578-8b91-37d02549e099@intel.com \
--to=ferruh.yigit@intel.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).