From: Dave Neary <dneary@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, tdelanerolle@linuxfoundation.org
Cc: web@dpdk.org, govboard@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-web] [dpdk-govboard] [PATCH 3/3] update license policy wording
Date: Wed, 18 Oct 2017 11:43:33 -0400 [thread overview]
Message-ID: <9a56b219-3bb8-e85f-5b73-4653fe51acb5@redhat.com> (raw)
In-Reply-To: <20171018150431.17200-4-thomas@monjalon.net>
Hi,
I got the same feedback ("s/shall be/is/ makes the document more legally
ambiguous - why avoid standard legal language?) on part of this change.
I have the same reservations which I also make on the govboard list when
this change was proposed.
Thanks,
Dave.
On 10/18/2017 11:04 AM, Thomas Monjalon wrote:
> Linux Foundation asks to
> - change wording of the license names
> - use spdx.org to describe licenses
> - change dual licensing wording with "OR" keyword
> - replace "shall" by "will"
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> about/charter.html | 36 ++++++++++++++++++------------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/about/charter.html b/about/charter.html
> index 235ebba..9ac8a32 100644
> --- a/about/charter.html
> +++ b/about/charter.html
> @@ -447,11 +447,11 @@
> <ol>
> <li>
> All new inbound contributions to DPDK
> - shall be made under the following licenses:
> + will be made under the following licenses:
> <ol>
> <li>
> - The <a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html"
> - >GPLv2 license</a>
> + The <a href="https://spdx.org/licenses/GPL-2.0.html"
> + >GPL-2.0 license</a>
> shall be used for code that runs in the kernel.
> Current examples of this are:
> <ol>
> @@ -465,20 +465,20 @@
> lib/librte_eal/linuxapp/kni/ethtool/ixgbe
> </ol>
> <li>
> - A dual
> - <a href="https://opensource.org/licenses/BSD-3-Clause"
> - >3-clause BSD</a> /
> - <a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html"
> - >GPLv2</a> license or
> - <a href="https://opensource.org/licenses/BSD-3-Clause"
> - >3-clause BSD</a> /
> - <a href="https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html"
> - >LGPLv2</a> license
> - shall be used for code that is shared between the kernel and userspace.
> + A disjonctive licence choice of
> + <a href="https://spdx.org/licenses/BSD-3-Clause.html"
> + >BSD-3-Clause</a> OR
> + <a href="https://spdx.org/licenses/GPL-2.0.html"
> + >GPL-2.0</a> or
> + <a href="https://spdx.org/licenses/BSD-3-Clause.html"
> + >BSD-3-Clause</a> OR
> + <a href="https://spdx.org/licenses/LGPL-2.0.html"
> + >LGPL-2.0</a>
> + will be used for code that is shared between the kernel and userspace.
> Current examples of this are:
> <ul>
> <li>
> - BSD/GPLv2:
> + BSD-3-Clause OR GPL-2.0:
> <ol>
> <li>
> All files in
> @@ -496,7 +496,7 @@
> >dom0_mm_misc.c</a>
> </ol>
> <li>
> - BSD/LGPLv2:
> + BSD-3-Clause OR LGPL-2.0:
> <ol start="4">
> <li>
> <a href="/browse/dpdk/tree/lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h"
> @@ -509,9 +509,9 @@
> </ol>
> </ul>
> <li>
> - The <a href="https://opensource.org/licenses/BSD-3-Clause"
> - >3-clause BSD license</a>
> - shall be used for all other contributions.
> + The <a href="https://spdx.org/licenses/BSD-3-Clause.html"
> + >BSD-3-Clause license</a>
> + will be used for all other contributions.
> </ol>
> <li>
> All contributions shall include a "Signed-off-by:" line
>
--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
next prev parent reply other threads:[~2017-10-18 15:43 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 ` Dave Neary [this message]
2017-10-18 15:47 ` 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
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=9a56b219-3bb8-e85f-5b73-4653fe51acb5@redhat.com \
--to=dneary@redhat.com \
--cc=govboard@dpdk.org \
--cc=tdelanerolle@linuxfoundation.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--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).