From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.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 17:05:52 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F351322@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <AM2PR04MB0753E8A88D1D4FCC419A9EB1896D0@AM2PR04MB0753.eurprd04.prod.outlook.com>
> -----Original Message-----
> From: Hemant Agrawal [mailto:hemant.agrawal@nxp.com]
> Sent: Tuesday, May 29, 2018 4:25 AM
> 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
> Subject: RE: [dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files
>
>...
>
> [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.
Hi Hemant,
Thanks for the clarification. In that case I'd suggest we use "The DPDK contributors"
since that is a recognizable entity.
And if there are no objections, or other recommendations, let's use that for
similar cases in the future.
Marko, can you respin the patchset to include that.
John
--
next prev parent reply other threads:[~2018-05-29 17:05 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
2018-05-29 17:05 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE23F351322@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.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).