From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-techboard <techboard@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Kevin Traynor <ktraynor@redhat.com>, dpdk-dev <dev@dpdk.org>,
"Kadam, Pallavi" <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>
Subject: [dpdk-dev] DPDK techboard minutes of October 9
Date: Thu, 10 Oct 2019 08:35:08 +0100 [thread overview]
Message-ID: <05d4a464-6372-d8f7-639d-165c09785621@intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-10-09
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) extend techboard membership
- "Honnappa Nagarahalli" and "Kevin Traynor" has been accepted to the
DPDK technical board membership, welcome both!
- Technical board now has 11 members, quorum is 8, voting pass is 6.
- Decided to limit the technical board size to 11 members.
2) security pre-release disclosure list subscription
- Both requested companies are accepted to the list.
3) license exception for Windows DPDK
- Ranjit and Pallavi will prepare more detailed report and will share offline
via email about which files (with different license) are required, where any
why they are required.
- Topic will be discussed again in next technical board meeting with the help of
the provided data.
4) ABI change without depreciation notice in advance
- Specific to 19.11, because of the new ABI/API policy, reasonable ABI/API
breakage will be accepted without deprecation notice, but they will have
to be documented in release notes.
5) Next meeting will be on October 23 and Hemant will chair it
Thanks,
ferruh
reply other threads:[~2019-10-10 7:35 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=05d4a464-6372-d8f7-639d-165c09785621@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--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).