DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yliu@fridaylinux.org>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of November 22
Date: Thu, 30 Nov 2017 20:02:02 +0800	[thread overview]
Message-ID: <20171130120202.GC5968@yliu-dev> (raw)

Hi,

Here are the minutes of the latest DPDK technical board meeting held on
2017-11-22.

Attendees:
- Bruce Richardson
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu

1) update on license: start using SPDX tags

DPDK techboard approved to replace existing file header license text with
SPDX tags. Hemant will make a demo patch, maintainers (and volunteers) then
could follow it to finish the transition. For all new contributions, there
should be only SPDX tags. The replacement could also be done in unit of
companies. Say, Bruce volunteered himself for replacing all contributions
from Intel.

Such transition patches will not be backported to stable and LTS releases.

And a private request will be sent to few maintainers to fix some license
issues.


2) next chair

Bruce will lead the next meeting.

             reply	other threads:[~2017-11-30 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 12:02 Yuanhan Liu [this message]
2017-11-30 13:53 ` Bruce Richardson

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=20171130120202.GC5968@yliu-dev \
    --to=yliu@fridaylinux.org \
    --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).