From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f65.google.com (mail-pg0-f65.google.com [74.125.83.65]) by dpdk.org (Postfix) with ESMTP id 0770B237 for ; Tue, 28 Nov 2017 18:00:07 +0100 (CET) Received: by mail-pg0-f65.google.com with SMTP id j4so189937pgp.1 for ; Tue, 28 Nov 2017 09:00:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=uyihO5+ah8K4mjv/irnJfkQgbU9S5BPXC0yyh/JOZQQ=; b=y/jbtJTtww8LwYLA/gGDHhG8/Hmkj9ONeQ0FJHq0KllSwDphHE6WIfPL4IdQJWQLGM htiB/ndDWsWMiyfdGLSjgNBceeZ1Es5F8kWemvnbBgq9YupBHCofhS9gWzpPNy8ZxiVw 4UTuf0YI/n5ePGUPIn4kCEV+ZVZLNEoZNJOLqv3kdsQBPK058OJAtnBHIAy/SVUbeob9 Nb+Thnjp3dkpf1LvBhpmcfJwrSKMnsIqIE0YmeEthCBDs7ECM6ajiG1lAKKkM2ViDSXx l+el8bJ9xxa5Wx+E8BBJzoWpr7RQCAOr5C4wx779r90w7+BrSxZKYdGbPn0JKXvUW5Gm zzHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=uyihO5+ah8K4mjv/irnJfkQgbU9S5BPXC0yyh/JOZQQ=; b=ebZHtx8L6AmIHpXKkxU7NFKHcX+fpI+18pyI24dnSNwn3G9v2Ayyk1BDp1kZfQs1Ui AhBreeZXfQtQSiKIQAuRLz37t6VXxfe/BtZJRjIfv7yk2txAkVyeRD7CC5F6OeP88mm4 KHMfQGDHH95olKdX38RWwnqFDFzPtJXhsuiRn6dmyGPsWIvfDcmdVG3vqK61s/cxuQAC vuCJhgHlz1lKwBqQXNi2C0Rvlkb97sQlSebi5V1xWsweQfFhvfp2D1KLicHoFDI79El5 tp+2+SwO6kGEVQHksi6gmcK20voO5rafFsxGr6lKfiEYYLgsEKr5G/t1a+5WQPxIaUdN pO6w== X-Gm-Message-State: AJaThX6fU2t/d3jCBfAITSjTVkZBvbQgTM4QOqrM8V5Dx2Ajfv5mjgkq 0UMk9FvRlgHyLg6h8RRNX4S3SQ== X-Google-Smtp-Source: AGs4zMaZ+rfH+T7ont2bbeQ10yZyQZLoojbPufxk5R3ZkxfRy73eK2uIEfXoP4xqZNyhrhHN/L8VdQ== X-Received: by 10.99.119.79 with SMTP id s76mr41105726pgc.192.1511888406750; Tue, 28 Nov 2017 09:00:06 -0800 (PST) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id z74sm46248379pfi.123.2017.11.28.09.00.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 28 Nov 2017 09:00:06 -0800 (PST) Date: Tue, 28 Nov 2017 08:59:58 -0800 From: Stephen Hemminger To: Hemant Agrawal Cc: , , Message-ID: <20171128085958.4ff6f6f0@xeon-e3> In-Reply-To: <1511768764-14595-1-git-send-email-hemant.agrawal@nxp.com> References: <1511768764-14595-1-git-send-email-hemant.agrawal@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 1/2] Introducing SPDX License Identifiers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 17:00:08 -0000 On Mon, 27 Nov 2017 13:16:03 +0530 Hemant Agrawal wrote: > The DPDK uses the Open Source BSD-3-Clause license for the core libraries > and drivers. The kernel components are naturally GPLv2 licensed. > > Many of the files in the DPDK source code contain the full text of the > applicable license. For example, most of the BSD-3-Clause files contain a > full copy of the BSD-3-Clause license text. > > Including big blocks of License headers in all files blows up the source > code with mostly redundant information. An additional problem is that even > the same licenses are referred to by a number of slightly varying text > blocks (full, abbreviated, different indentation, line wrapping and/or > white space, with obsolete address information, ...) which makes validation > and automatic processing a nightmare. > > To make this easier, DPDK is adpoting the use of a single line reference to > Unique License Identifiers in source files as defined by the Linux > Foundation's SPDX project [1]. > > Adding license information in this fashion, rather than adding full license > text, can be more efficient for developers; decreases errors; and improves > automated detection of licenses. The current set of valid, predefined SPDX > identifiers is set forth on the SPDX License List[2] > at https://spdx.org/licenses/. > > For example, to label a file as subject to the BSD-3-Clause license, > the following text would be used: > > Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER > SPDX-License-Identifier: BSD-3-Clause > > To label a file as GPL-2.0 (e.g., for code that runs in the kernel), the > following text would be used: > > Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER > SPDX-License-Identifier: GPL-2.0 > > To label a file as dual-licensed with BSD-3-Clause and GPL-2.0 (e.g., for > code that is shared between the kernel and userspace), the following text > would be used: > > Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER > SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0 > > To label a file as dual-licensed with BSD-3-Clause and LGPL-2.1 (e.g., for > code that is shared between the kernel and userspace), the following text > would be used: > > Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER > SPDX-License-Identifier: BSD-3-Clause OR LGPL-2.1 > > Note: Any new file contributions in DPDK shall adhere to the above scheme. > It is also being recommended to replace the existing license text in the > code with SPDX-License-Identifiers. > > Note 2: DPDK currently adhere to it's IP policies[3]. Any exception to this > shall be approved by DPDK tech board and DPDK Governing Board. Steps for > any exception approval: > 1. Mention the appropriate license identifier form SPDX. If the license is > not listed in SPDX Licenses. It is the submitters responsibiliity to get > it fist listed. ^first > 2. Get the required approval from the DPDK Technical Board. Technical board > may advise the author to check alternate means first. If no other > alternatives are found and the merit of the contributions are important > for DPDK's mission, it may decide on such exception with two-thirds vote > of the members. > 3. Technical board then approach Governing board for such limited approval > for the given contribution only. > > Any approvals shall be documented in "Licenses/exceptions.txt" with record > dates. > > Note 3: Projects like U-boot have been been using SPDX License Idenfiers > successfully [2]. They have been referered in implementing SPDX based > guidelines in DPDK. > > Note 4: From the legal point of view, this patch is supposed to be only a > change to the textual representation of the license information, but in no > way any change to the actual license terms. With this patch applied, all > files will still be licensed under the same terms they were before. > > Signed-off-by: Hemant Agrawal I like this, it adds clarity. What the kernel did was run a license scan and add SPDX tags to any file without an existing matching license text. I just did the same thing to iproute2. Also, the copyright holder is free to replace existing verbose text with SPDX tag instead, if they so desire. Acked-by: Stephen Hemminger