From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files
Date: Tue, 29 May 2018 03:25:08 +0000 [thread overview]
Message-ID: <AM2PR04MB0753E8A88D1D4FCC419A9EB1896D0@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F347F1F@IRSMSX103.ger.corp.intel.com>
HI John,
>
> -----Original Message-----
> From: Kovacevic, Marko [mailto:marko.kovacevic@intel.com]
> Sent: Friday, May 25, 2018 9:00 PM
> To: Thomas Monjalon <thomas@monjalon.net>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files
>
> >
> >
> > It has been recommended to add SPDX tags to release notes, with a
> > global copyright on behalf of all contributors, or community.
> >
> > We need a v2 of this patch, thanks.
> >
> >
>
> Hi Thomas,
>
> What exactly is the global copyright ?
>
> [Hemant] We discussed with LF foundation lawyers. It was suggested to
> use "Copyright 2018 The DPDK Community"
Hi Hemant,
Is that valid? "The DPDK Community" isn't a single, clear entity.
If that is what has been agreed then we are okay with it but I wanted to make 100% sure.
[Hemant] I got following recommendation from the Linux Foundation legal:
"For files that are e.g. release scripts and documentation, these are typically understood to consist of contributions that are copyrighted by their contributors. So even if there isn't a notice in the file, it would still generally be understood to be subject to its contributors' copyrights and to be licensed out under an open source license.
As you suggested, adding copyright and license notices can help clarify these specifics for downstream uses. We have recommended as best practices that projects add something like "Copyright The _________ Project" or "Copyright The __________ contributors". I think your suggestion of "Copyright The DPDK Community" is fine. And yes, I'd recommend including the appropriate license notice and/or SPDX identifier in these files as well.
Just to be clear, also, we _don't_ recommend removing pre-existing copyright notices unless you are the copyright holder in question. It's generally understood that it's fine to add general copyright notices where accurate, but only the copyright holder should remove or modify their own notices. "
[Hemant] So, "The DPDK Project" or "The DPDK contributors" or "The DPDK community" - anything is fine, we have to use just one of these consistently.
Regards,
Hemant
next prev parent reply other threads:[~2018-05-29 3:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 13:11 Marko Kovacevic
2018-04-09 13:54 ` Ferruh Yigit
2018-04-10 4:38 ` Hemant Agrawal
2018-05-25 10:39 ` Thomas Monjalon
2018-05-25 15:30 ` Kovacevic, Marko
2018-05-26 12:58 ` Hemant Agrawal
2018-05-28 16:08 ` Mcnamara, John
2018-05-29 3:25 ` Hemant Agrawal [this message]
2018-05-29 17:05 ` Mcnamara, John
2018-05-30 15:18 ` Kovacevic, Marko
2018-05-30 15:26 ` Ferruh Yigit
2018-05-31 6:39 ` Hemant Agrawal
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=AM2PR04MB0753E8A88D1D4FCC419A9EB1896D0@AM2PR04MB0753.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).