From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 3/3] doc: convert license headers to SPDX tags
Date: Wed, 24 Jan 2018 09:14:29 +0100 [thread overview]
Message-ID: <9100236.kIqJc6xL1O@xps> (raw)
In-Reply-To: <AM2PR04MB0753FD280F58343FB39B525989E20@AM2PR04MB0753.eurprd04.prod.outlook.com>
24/01/2018 06:48, Hemant Agrawal:
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > 23/01/2018 16:19, Hemant Agrawal:
> > >
> > > > -----Original Message-----
> > > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > >
> > > > 23/01/2018 14:08, Hemant Agrawal:
> > > > > This patch will be good if you only add SPDX to it and NOT remove
> > > > > the
> > > > original license text.
> > > > > i.e. only do following:
> > > > >
> > > > > > -.. BSD LICENSE
> > > > > > +.. SPDX-License-Identifier: BSD-3-Clause
> > > > >
> > > > > Around RC2 timeframe, I intend to do that. All the remaining but
> > > > > valid
> > > > license files, we will add SPDX and NOT remove the license text.
> > > >
> > > > Hemant, I don't understand why?
> > > [Hemant]
> > >
> > > Changing license for someone else copyright needs their ACK. However
> > > we can add SPDX without modifying existing license text There are large
> > number of other copyrights and not everyone is converting their license to
> > SPDX only.
> > >
> > > In case of linux kernel and uboot, as a first step they just added SPDX to
> > all files without removing the license text.
> > >
> > > I was thinking of doing the same so that all the files in DPDK should have
> > SPDX. However, we will not SPDX to files, which are not complaint to DPDK
> > policy.
> > > We will deal with them separately.
> >
> > If we don't remove the license now, it will never happen.
>
> I have the same fear. But we can not remove other's license text without their explicit approval.
>
> W.r.t DPDK project priorities: License compliance is important than cleanup.
>
> Let's target following:
> 1. 100% compliance by 18.05
> 2. 100% Cleanup by 18.08 or 18.11
Why do you assume we cannot get the author's approval quickly?
We did not try.
Let's try to do compliance and cleanup at the same time.
next prev parent reply other threads:[~2018-01-24 8:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 21:07 [dpdk-dev] [PATCH] doc: convert license headers to SPDX tags for NIC docs Ferruh Yigit
2017-12-19 5:07 ` Hemant Agrawal
2017-12-19 18:57 ` Ferruh Yigit
2018-01-09 14:56 ` [dpdk-dev] [PATCH] doc: convert license headers to SPDX tags Ferruh Yigit
2018-01-09 15:13 ` Andrew Rybchenko
2018-01-09 15:31 ` Ferruh Yigit
2018-01-09 16:35 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-01-09 19:34 ` Andrew Rybchenko
2018-01-23 12:29 ` [dpdk-dev] [PATCH v3 1/3] " Ferruh Yigit
2018-01-23 12:29 ` [dpdk-dev] [PATCH v3 2/3] " Ferruh Yigit
2018-01-23 12:58 ` Bruce Richardson
2018-01-23 12:29 ` [dpdk-dev] [PATCH v3 3/3] " Ferruh Yigit
2018-01-23 13:08 ` Hemant Agrawal
2018-01-23 14:35 ` Thomas Monjalon
2018-01-23 15:19 ` Hemant Agrawal
2018-01-23 17:25 ` Thomas Monjalon
2018-01-24 5:48 ` Hemant Agrawal
2018-01-24 8:14 ` Thomas Monjalon [this message]
2018-01-23 12:57 ` [dpdk-dev] [PATCH v3 1/3] " Bruce Richardson
2018-02-01 17:18 ` [dpdk-dev] [PATCH v4] doc: convert Intel " Ferruh Yigit
2018-02-06 22:33 ` Thomas Monjalon
2018-02-01 17:19 ` [dpdk-dev] [PATCH v4] doc: convert Intel sharing " Ferruh Yigit
2018-02-06 16:09 ` Kovacevic, Marko
2018-02-06 22:35 ` 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=9100236.kIqJc6xL1O@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
/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).