DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes (2019-07-17)
Date: Wed, 11 Sep 2019 17:05:35 +0200	[thread overview]
Message-ID: <20190911150535.pajfybqrzxhept4g@platinum> (raw)

Hi,

Here are the meeting notes for the DPDK technical board meeting held on
2019-07-17.

Attendees:

- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Olivier Matz
- Thomas Monjalon

1) New next-net tree co-maintainer
==================================

Andrew Rybchenko <arybchenko@solarflare.com> is accepted as new
co-maintainer for next-net sub-tree.

2) DPDK API/ABI Stability
=========================

Good progresses and discussions.

Some points should be clarified before the userspace summit:

- Splitting DPDK into core, non-core and experimental libraries
- OS Packaging of DPDK
- UNH Testing of DPDK

3) Some examples are suggested to be removed in 19.11
=====================================================

Bruce to kick off the discussion on the ML.
(done: https://mails.dpdk.org/archives/dev/2019-July/138676.html )

4) Security process update
==========================

Request has been done to Trishan at last governing board that LF becomes
a CNA (CVE Numbering Authority).

Stephen (techboard representative at govboard) to pass the request via
email.

5) Proposal for regexdev subsystem
===================================

RFC proposal from Jerin Jacob <jerinj@marvell.com>:
https://patchwork.dpdk.org/patch/55505/

Several vendors seems interested by this feature. Concerned people
are encouraged to reply to this thread.

6) SPDX licenses
================

Hemant + Bruce to check if we can achieve SPDX compliance for 19.11.

7) Next meeting
===============

On 2019-07-31, Maxime will chair it.

                 reply	other threads:[~2019-09-11 15:05 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=20190911150535.pajfybqrzxhept4g@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@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).