Soft Patch Panel
 help / color / mirror / Atom feed
From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	"Tim O'Driscoll" <tim.odriscoll@intel.com>,
	 "St Leger, Jim" <jim.st.leger@intel.com>,
	spp@dpdk.org
Subject: Re: [spp] [PATCH 2/7] spp_primary: convert license to SPDX tag
Date: Wed, 16 May 2018 10:06:47 -0400	[thread overview]
Message-ID: <CAFXL6f8cM3rw5a2pHsG9YiYcGNj5rV2VVQZb+5wDU+CUM=Z3-A@mail.gmail.com> (raw)
In-Reply-To: <94952894-e5e5-6ba4-f027-3499d197bbc5@lab.ntt.co.jp>

Hi,
Thanks for bringing up the question. Generally, we recommend that SPDX
license identifiers -- for existing files be thought as supplemental
information to add. Don't replace the existing license information, add the
tags on.  Suggest reviewing the patch against that criteria.  Remember to
maintain the attribution information. You may want to speak to your
in-house counsel with respect to any changes you would like to make to
files over which you hold copyright.

Regards,
Trishan


On Wed, May 16, 2018 at 5:08 AM, Yasufumi Ogawa <
ogawa.yasufumi@lab.ntt.co.jp> wrote:

> On 2018/05/16 1:55, Ferruh Yigit wrote:
>
>> On 5/3/2018 5:08 PM, Ferruh Yigit wrote:
>>
>>> On 4/23/2018 7:28 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
>>>
>>>> @@ -1,34 +1,6 @@
>>>> -/*-
>>>> - *   BSD LICENSE
>>>> - *
>>>> - *   Copyright(c) 2015-2016 Intel Corporation. All rights reserved.
>>>> - *   All rights reserved.
>>>> - *
>>>> - *   Redistribution and use in source and binary forms, with or without
>>>> - *   modification, are permitted provided that the following conditions
>>>> - *   are met:
>>>> - *
>>>> - *     * Redistributions of source code must retain the above copyright
>>>> - *       notice, this list of conditions and the following disclaimer.
>>>> - *     * Redistributions in binary form must reproduce the above
>>>> copyright
>>>> - *       notice, this list of conditions and the following disclaimer
>>>> in
>>>> - *       the documentation and/or other materials provided with the
>>>> - *       distribution.
>>>> - *     * Neither the name of Intel Corporation nor the names of its
>>>> - *       contributors may be used to endorse or promote products
>>>> derived
>>>> - *       from this software without specific prior written permission.
>>>> - *
>>>> - *   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
>>>> CONTRIBUTORS
>>>> - *   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>>> - *   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
>>>> FOR
>>>> - *   A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
>>>> COPYRIGHT
>>>> - *   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
>>>> INCIDENTAL,
>>>> - *   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>>>> - *   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
>>>> USE,
>>>> - *   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
>>>> ANY
>>>> - *   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
>>>> TORT
>>>> - *   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
>>>> USE
>>>> - *   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
>>>> DAMAGE.
>>>> +/* SPDX-License-Identifier: BSD-3-Clause
>>>> + * Copyright(c) 2015-2016 Intel Corporation
>>>> + * Copyright(c) 2017-2018 Nippon Telegraph and Telephone Corporation
>>>>    */
>>>>
>>>
>>> Hi Ogawa-san,
>>>
>>> Thanks for taking initiative to switch spp to SPDX, appreciated.
>>>
>>> First Trishan from Linux foundation and Jim from DPDK governance board
>>> are cc'ed
>>> for input if there is any concern or more process to follow from
>>> governance
>>> point of view.
>>>
>>
>> The is no response, which I am taking as there is no concern and will move
>> forward on getting patches. Please shout if there are concerns.
>>
> Hi Trishan, Jim,
>
> SPP was provided originally from Intel, but currently is maintained by NTT
> and planed to change license to SPDX. We have made many changes on SPP and
> I would like to add NTT to the license only for considerably modified or
> newly created files by NTT. Could you give us advice if there are any
> concern?
>
> Thanks,
> Yasufumi
>
>
>>
>>> Second these patches are both converts licensing to SPDX tag and adds
>>> ntt as
>>> copyright holder. Can we separate these two please? A patchset to convert
>>> existing licensing to SPDX as it is, and another set to add ntt.
>>>
>>>
>>> Thanks,
>>> ferruh
>>>
>>>
>>
>>
>>
>
> --
> Yasufumi Ogawa
> NTT Network Service Systems Labs
>
>


-- 
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle
email: tdelanerolle@linuxfoundation.org

  reply	other threads:[~2018-05-16 14:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23  6:28 [spp] [PATCH 0/7] Update licence to SPDX ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 1/7] license: add bsd-3-clause text ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 2/7] spp_primary: convert license to SPDX tag ogawa.yasufumi
2018-05-03 16:08   ` Ferruh Yigit
2018-05-15 16:55     ` Ferruh Yigit
2018-05-16  9:08       ` Yasufumi Ogawa
2018-05-16 14:06         ` Trishan de Lanerolle [this message]
2018-05-17  7:09           ` Yasufumi Ogawa
2018-05-17 14:25             ` Trishan de Lanerolle
2018-05-18  8:03               ` Yasufumi Ogawa
2018-05-24 12:29                 ` Ferruh Yigit
2018-05-25 20:45                   ` Yasufumi Ogawa
2018-04-23  6:28 ` [spp] [PATCH 3/7] spp_nfv: " ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 4/7] controller: " ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 5/7] spp_vm: " ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 6/7] shared: " ogawa.yasufumi
2018-04-23  6:28 ` [spp] [PATCH 7/7] spp_vf: " ogawa.yasufumi
2018-05-10 11:10 ` [spp] [PATCH v2 00/13] Update license to SPDX ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 01/13] license: add bsd-3-clause text ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 02/13] spp_primary: convert license to SPDX tag ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 03/13] spp_primary: add NTT to license description ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 04/13] spp_nfv: convert license to SPDX tag ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 05/13] spp_nfv: add NTT to license description ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 06/13] controller: convert license of Intel to SPDX tag ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 07/13] controller: add NTT " ogawa.yasufumi
2018-05-10 11:10   ` [spp] [PATCH v2 08/13] controller: add NTT to license description ogawa.yasufumi
2018-05-23 20:05   ` [spp] [PATCH v3 0/8] Update license to SPDX ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 1/8] license: add bsd-3-clause text ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 2/8] spp_primary: convert license to SPDX tag ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 3/8] spp_nfv: " ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 4/8] controller: convert license of Intel " ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 5/8] controller: add NTT " ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 6/8] spp_vm: convert license to " ogawa.yasufumi
2018-05-23 20:05     ` [spp] [PATCH v3 7/8] shared: " ogawa.yasufumi
2018-05-23 20:06     ` [spp] [PATCH v3 8/8] spp_vf: " ogawa.yasufumi
2018-05-24 12:37     ` [spp] [PATCH v3 0/8] Update license to SPDX Ferruh Yigit
2018-05-24 12:42       ` Ferruh Yigit
2018-05-10 11:17 ` [spp] [PATCH v2 09/13] spp_vm: convert license to SPDX tag ogawa.yasufumi
2018-05-10 11:17 ` [spp] [PATCH v2 10/13] spp_vm: add NTT to license description ogawa.yasufumi
2018-05-10 11:18 ` [spp] [PATCH v2 11/13] shared: convert license to SPDX tag ogawa.yasufumi
2018-05-10 11:18 ` [spp] [PATCH v2 12/13] shared: add NTT to license description ogawa.yasufumi
2018-05-10 11:19 ` [spp] [PATCH v2 13/13] spp_vf: convert license to SPDX tag ogawa.yasufumi

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='CAFXL6f8cM3rw5a2pHsG9YiYcGNj5rV2VVQZb+5wDU+CUM=Z3-A@mail.gmail.com' \
    --to=tdelanerolle@linuxfoundation.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jim.st.leger@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@dpdk.org \
    --cc=tim.odriscoll@intel.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).