From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files
Date: Thu, 31 May 2018 06:39:18 +0000 [thread overview]
Message-ID: <AM2PR04MB0753D8A6AA5E5C8E647921F789630@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <7354221f-48c7-05fc-38ae-4d09e956a408@intel.com>
Hi Ferruh,
On 5/30/2018 4:18 PM, Kovacevic, Marko wrote:
>>> [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.
>
>
> After some discussion intel would prefer to keep the license as is on the release notes.
> Other contributors/companies can add respective SPDX license for their
> contributions
Hi Hemant,
Would it matter if keep the Intel copyright in the release notes that already have it, and add "The DPDK contributors" as a new copyright holder?
And for the ones don't have any copyright, add only "The DPDK contributors".
[Hemant] agree. There is no need to remove the existing copy rights. However the new files which are generic should have the generic copyright.
It is sometimes not easy call to give a go to remove an existing copyright, even for release notes ...
Regards,
Hemant
prev parent reply other threads:[~2018-05-31 6:39 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
2018-05-30 15:18 ` Kovacevic, Marko
2018-05-30 15:26 ` Ferruh Yigit
2018-05-31 6:39 ` Hemant Agrawal [this message]
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=AM2PR04MB0753D8A6AA5E5C8E647921F789630@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).