From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: dpdk-techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of May 22
Date: Wed, 5 Jun 2019 16:03:29 +0100 [thread overview]
Message-ID: <62162df8-e82e-7fc9-6fda-553bbc1e9a32@intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-05-22
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) DPDK API Stability discussion
- A sub-group will work on how to improve ABI/API stability and will come with a
proposal as update to versioning.html and stable.html.
- Sub-group consist of Ray, Bruce, Stephen and Kevin. Ray will drive the effort.
- There will be a status update in next meeting (June 5) and target date is June 19.
2) Userspace summit CFP deadline
- Techboard need to synchronize on major topics to cover in the summit.
- If you think a topic must be covered in the userspace summit, but you don't
want to submit it yourself, please ask to techboard@dpdk.org.
3) DPDK development process and tools survey
- Honnappa put out the report
- Thomas and Maxime will review the report
- After review techboard approval will be get via email
- When approved, outcome will be shared in the mail list by Honnappa
- Outcome will be presented in the userspace summit by Honnappa
- Maxime and Honnapa will propose list of actions/improvements based on survey
to the techboard on June 19 techboard meeting.
4) Next meeting will be on June 5 and Hemant will chair it
Thanks,
ferruh
next reply other threads:[~2019-06-05 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:03 Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-05 12:04 Hemant Agrawal
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=62162df8-e82e-7fc9-6fda-553bbc1e9a32@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).