From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of tech-board meeting 2017-04-27
Date: Wed, 3 May 2017 05:57:18 +0000 [thread overview]
Message-ID: <DB3PR04MB076270425F3C5C8E7C8B649889160@DB3PR04MB0762.eurprd04.prod.outlook.com> (raw)
Hi all,
Here is the meeting notes for the last DPDK technical board meeting held on 2017-04-27.
Please note that meetings are open to all to attend. Any topics to be referred to the tech board for discussion at that meeting should be emailed to techboard@dpdk.org. Normally, it's a bi-weekly meeting.
Member attendees:
- Bruce Richardson
- Hemant Agrawal
- Jan Blunck
- Jerin Jacob
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu
1.Scope of cmdline and cfgfile libraries in DPDK
-------------------------------------------------
- DPDK will continue to keep one version of cli and cfg libs in dpdk. They can be replaced with a better version in future.
- w.r.t Keith's CLI lib proposal. It should replace the existing CLI lib. If any api changes are required, the api deprecation process should be followed.
- It is acknowledged that cli and cfg libs can also be used outside dpdk. They can be better hosted on a different git repository. However, DPDK needs a better external dep system to do this.
- The DPDK build system should be improved to work better with external dependencies. Thomas and Bruce will send a RFC on build system reqs for handling external deps.
2. DPDK Bug Tracker
-----------------
DPDK is missing a bug tracker or to-do item list. It will be discussed in next meeting.
3. Next Meeting
---------------
As per alphabetical order, Jan Blunck will chair next meeting. He will poll for the date and time of next meeting.
Regards,
Hemant
next reply other threads:[~2017-05-03 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 5:57 Hemant Agrawal [this message]
2017-05-04 11:36 ` Mcnamara, John
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=DB3PR04MB076270425F3C5C8E7C8B649889160@DB3PR04MB0762.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.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).