From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by dpdk.org (Postfix) with ESMTP id 6CB975F72 for ; Thu, 17 May 2018 16:25:42 +0200 (CEST) Received: by mail-it0-f49.google.com with SMTP id q72-v6so9122430itc.0 for ; Thu, 17 May 2018 07:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=w3v0HVKGsG1jUsu0ddUYSsLhMK4e5S9iiSsrM4XQRYw=; b=QyYvtUE6+WAX5GKJ0PyrPRWQ8rmYVwPOq2bFPZMK0+hado2V7tJ/Zi/RcQ4Lc5tSds hX0BfN/Bf+1ER9ww6d0LlEqoL3NRD8ofq7V59F952IlRIrnTKvsbltNGJeGMaJxw5FEO jYwfIZRtm5PpJB02Bq5gQ7HpP6eCoj56xYNRM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=w3v0HVKGsG1jUsu0ddUYSsLhMK4e5S9iiSsrM4XQRYw=; b=qt2hGylNDq34MMLLQRTKi/9LuMQip6ahFhjImueA5Uamw0lqmxXt1teXe/ZkeRsTCy vzw8obylRcu8rWDnmG9wtU1i89ZHFDqW3kohTUCex4OG+uVjocIGly4Ga+wLuUN4L71w 6KIKNZBeKd1mk5d/Uu0upxV1oFu8v40oFP25b4J57krTUPLUqHZF7RJ7iSlYxo2TQNbL QqcjXmIRc/oEmjv1+JwMAfX/cxck+31mvnXX2byB2dpwcz5u1SxZAjx/1oSYEerb7yDr 57gpr/X8hnE1UZ6KaZU351cvwdRGifJWuxliTjoJ1yMii9RDVng5kflUvnSGM24CznLa ta7g== X-Gm-Message-State: ALKqPwcFr9PzuA2Dv5JNgTLpOKv9GgCZ/pDrufFAQCE+EFtclEBBrLnU k3dGDC1xb7kfoRtCP5vDFGEEu19dA/d+qmwS8fNd7A== X-Google-Smtp-Source: AB8JxZorXMm9hj7tWVV8yGgHoGfTII6cbYJDzdTR1lyYwWS3Ld4V7g+LxjOtrUCberWaZzG0toUGmaca142n3TUHiRM= X-Received: by 2002:a24:82c3:: with SMTP id t186-v6mr2890135itd.13.1526567141737; Thu, 17 May 2018 07:25:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.164.225 with HTTP; Thu, 17 May 2018 07:25:41 -0700 (PDT) In-Reply-To: <2e4c744f-9b8c-0a08-5b32-47c69ea70c75@lab.ntt.co.jp> References: <20180423055414.7049-1-ogawa.yasufumi@lab.ntt.co.jp> <20180423055414.7049-3-ogawa.yasufumi@lab.ntt.co.jp> <1db65b50-f7e0-748c-e21a-652eb9c3905a@intel.com> <122b687e-aa95-5728-8318-5c7213f4d2fc@intel.com> <94952894-e5e5-6ba4-f027-3499d197bbc5@lab.ntt.co.jp> <2e4c744f-9b8c-0a08-5b32-47c69ea70c75@lab.ntt.co.jp> From: Trishan de Lanerolle Date: Thu, 17 May 2018 10:25:41 -0400 Message-ID: To: Yasufumi Ogawa Cc: Ferruh Yigit , "Tim O'Driscoll" , "St Leger, Jim" , spp@dpdk.org X-Mailman-Approved-At: Thu, 17 May 2018 18:40:28 +0200 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [spp] [PATCH 2/7] spp_primary: convert license to SPDX tag X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 14:25:42 -0000 Can you provide additional details on what you need clarification on? Regards, Trishan On Thu, May 17, 2018 at 3:09 AM, Yasufumi Ogawa < ogawa.yasufumi@lab.ntt.co.jp> wrote: > On 2018/05/16 23:06, Trishan de Lanerolle wrote: > >> 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 >> > Hi Trishan, > > Thank you for your reply. I understand that I should not replace existing > license info. I would like to have a talk to and confirm that it is > acceptable. > > Regards, > Yasufumi > >> >> >> 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 > 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 > dation.org> >> > > > -- > 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