[dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files

[Mcnamara, John]

> -----Original Message-----
> From: Hemant Agrawal [mailto:hemant.agrawal at nxp.com]
> Sent: Tuesday, May 29, 2018 4:25 AM
> To: Mcnamara, John <john.mcnamara at intel.com>; Kovacevic, Marko
> <marko.kovacevic at intel.com>; Thomas Monjalon <thomas at monjalon.net>; Yigit,
> Ferruh <ferruh.yigit at intel.com>
> Cc: dev at 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
--