From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of June 20
Date: Tue, 26 Jun 2018 07:23:35 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258C0C41A1B@irsmsx105.ger.corp.intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-06-20
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) next-net-intel maintainer:
Qi Zhang will be the new maintainer instead of Helin Zhang.
Beilei Xing will be the backup maintainer of the subtree.
2) maintainer of 17.11 LTS
Yuanhan Liu is stepping away from LTS maintainer role.
Yongseok Koh will be new maintainer for 17.11 LTS
3) A new design for dpdk.org website.
www.dpdk.org is now managed by LF.
New site core.dpdk.org is the technical part for DPDK itself (not the side projects)
core.dpdk.org will now use Hugo instead of plain HTML as before.
git repository for core.dpdk.org will still remain at http://git.dpdk.org/tools/dpdk-web/
and old HTML-based version will still be available as a branch.
4) LF proposal to move to GitHub with pull requests for managing content of core.dpdk.org.
The decision was made to stay with existing mail-based patch process.
5) Hyper-V series status update
v11 was sent last week, Thomas plan to apply them soon.
6) Discussion about minimal supported kernel version
No final decision made.
Agreed to continue discussion on ML and return to that subject at next TB meeting.
Next meeting will be on July 4th and Olivier will chair it
reply other threads:[~2018-06-26 7:23 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=2601191342CEEE43887BDE71AB977258C0C41A1B@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@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).