dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: dpdk-techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK Techboard minutes of June 6
Date: Thu, 20 Jun 2019 08:33:56 +0000	[thread overview]
Message-ID: <VI1PR0401MB2541932FA6480F2261FE452889E40@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR0401MB2541F07E6E640ED569918E6089E40@VI1PR0401MB2541.eurprd04.prod.outlook.com>

Meeting notes for the DPDK technical board meeting held on 2018-06-06

Attendees:
	- Bruce Richardson
	- Ferruh Yigit
	- Hemant Agrawal
	- Jerin Jacob
	- Maxime Coquelin
	- Olivier Matz
	- Stephen Hemminger
	- Thomas Monjalon

1) Techboard rep in DPDK Gov Board

- Stephen will be new tech board rep succeeding Maxime. Olivier gave it a pass. 

2) DPDK API Stability discussion

- A sub-group is working 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 sent a proposal within sub-group for review. 
- There will be a status update in next TB meeting (June 19).
- Jerin suggested that API stability should not come at the cost of performance regression. 
- Ray is proposing a panel discussion on ABI Compatibility for DPDK Userspace. He will choose the panelists. 

3) discussion to extend Techboard membership
 -  proposed to discuss Techboard membership in 1 month time. 

4) Userspace summit CFP deadline over.
- Proposals are under review.

5) Next meeting will be on June 19 and Jerin will chair it

Thanks,
Hemant


           reply	other threads:[~2019-06-20  8:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <VI1PR0401MB2541F07E6E640ED569918E6089E40@VI1PR0401MB2541.eurprd04.prod.outlook.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=VI1PR0401MB2541932FA6480F2261FE452889E40@VI1PR0401MB2541.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).