DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
	tdelanerolle@linuxfoundation.org
Cc: web@dpdk.org, govboard@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-web] [dpdk-govboard] [PATCH v2 3/4] update license policy wording
Date: Wed, 29 Nov 2017 10:25:03 +0100	[thread overview]
Message-ID: <2829012.FIq2iLLcM0@xps> (raw)
In-Reply-To: <AM2PR04MB0753865653892DCAAA70FB23893B0@AM2PR04MB0753.eurprd04.prod.outlook.com>

29/11/2017 06:34, Hemant Agrawal:
> From: Thomas Monjalon
> > -			<a
> > href="https://www.gnu.org%2Flicenses%2Fold-licenses%2Flgpl-
> > 2.0.en.html" LGPLv2</a> license
> 
> LGPLv2.0 is an obsolete license.  We shall be using LGPLv2.1.  As per "https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html"
> "Please note that the GNU Library General Public License has been superseded by the GNU Lesser General Public License. We urge everyone to use the GNU Lesser General Public License instead of this GNU Library GPL. We leave the Library GPL available here for historical reference."
> Please note that DPDK repository include LICENSE.LGPL for version 2.1 

I agree, it should be LGPL-2.1.
The files are already declaring LPGL-2.1 in their headers:
	- drivers/net/avp/rte_avp_common.h
	- drivers/net/avp/rte_avp_fifo.h
	- lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h

> In your patch you are just changing the links etc. so this may be an incremental change as well.

I suggest to send a v3 to update it.

Trishan, do you agree?

  reply	other threads:[~2017-11-29  9:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 19:16 [dpdk-web] Updated charter for upload Trishan de Lanerolle
2017-10-17 20:24 ` Thomas Monjalon
2017-10-17 22:23   ` Trishan de Lanerolle
2017-10-18 15:04     ` [dpdk-web] [PATCH 0/3] update charter Thomas Monjalon
2017-10-18 15:04       ` [dpdk-web] [PATCH 1/3] update Governing Board responsibilities Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:04       ` [dpdk-web] [PATCH 2/3] update Technical Board responsibility wording Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:40         ` Dave Neary
2017-10-18 15:41           ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:04       ` [dpdk-web] [PATCH 3/3] update license policy wording Thomas Monjalon
2017-10-18 15:43         ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:47         ` [dpdk-web] " Thomas Monjalon
2017-11-28 18:39       ` [dpdk-web] [PATCH v2 0/4] update charter Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 1/4] update Governing Board responsibilities Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 2/4] update Technical " Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 3/4] update license policy wording Thomas Monjalon
2017-11-29  5:34           ` [dpdk-web] [dpdk-govboard] " Hemant Agrawal
2017-11-29  9:25             ` Thomas Monjalon [this message]
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 4/4] remove references to Xen dom0 files Thomas Monjalon
2017-12-11 22:09         ` [dpdk-web] [dpdk-techboard] [PATCH v2 0/4] update charter Thomas Monjalon

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=2829012.FIq2iLLcM0@xps \
    --to=thomas@monjalon.net \
    --cc=govboard@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=techboard@dpdk.org \
    --cc=web@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).