From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: DPDK Techboard <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of July 31
Date: Wed, 11 Sep 2019 17:04:26 +0200 [thread overview]
Message-ID: <5c226d6b-f97a-a56b-0c61-44cc1898eb98@redhat.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-07-31
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Maxime Coquelin
- Stephen Hemminger
- Thomas Monjalon
1) Security process updates
- The governing board acknowledges the security process
- Last governing board meeting didn't covered the technical board
request for LF to become a CNA
- Stephen to do the request at the next governing board meeting
2) SPDX licences
- Still some subsystems not compliant with SPDK, target is still v19.11
- Hemant sent a reminder on DPDK dev mailing-list
- Hemant will give a status update at next meeting
3) DPDK community survey follow-up
- 39% of the respondents said they do not get enough reviews
* Situation has improved since we have more sub-trees
* Could further be improved if maintainers asked trusted contributors
to help reviewing patches
* In case the contributor feels the review process does not work, he
should e-mail the techboard
* Thomas and Honnappa to update the contribution documentation and
send a pointer to that doc on the dev mailing-list
4) DPDK API/ABI Stability discussions
- Ray prepared a v2 of the policy patch, main changes:
* Change to 1 year initial ABI stability period, with a review
afterward to elongate the stability period
* Changes to the handling of experimental and depreciation process
- Open question is from where to start the major ABI version numbering.
* Should it be the year of the declaration of stable ABI version?
* Or start at v3.0 and continue from there?
* Bruce mentioned that we already have libraries at version > 10, so
using 3 would not work
* Techboard voted to use the year of stabilization as starting point.
5) Next meeting
- On 2019-08-14, Stephen will chair it.
reply other threads:[~2019-09-11 15:04 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=5c226d6b-f97a-a56b-0c61-44cc1898eb98@redhat.com \
--to=maxime.coquelin@redhat.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).