From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 1A9247D30 for ; Thu, 4 Jan 2018 19:32:41 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 91A9B20CA7; Thu, 4 Jan 2018 13:32:40 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 04 Jan 2018 13:32:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=iXxCq1QVa/X1Gm+xCz5pqLy2+A F26NshrbT0p1Z3JR4=; b=LM1gdI4Kt2lVf8DCZEe0GaG8T2ftK3AQb6aL0qpaym woFFPS7TK6YgZXkgaYQIuOoVsISc+ZXNsx3iyl/zMf9zeaX+2gavH1xRWhArHXdJ tcW6NqDfDqkzxa3WEE2gy4gt6I8D1PPoZRcS3b0ZUkYgmxamYTxmcF8deIh3auqA c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=iXxCq1 QVa/X1Gm+xCz5pqLy2+AF26NshrbT0p1Z3JR4=; b=Yj1/rzA0D/nAfVaNNFCK7e YEgs9JQduWO8tLtaMXEvkFNgZo5JFJlZZSPDLDzuER/HttBj13M8CSMtwUPUa8Vw 3kcE1/qOkx+vWD9UCwAaII3hKGHRy1YR46tJj6INJnfD235e9D8MMkQF/Pm90w4A iwOTOD6seIOR7lV2TE8h+gk9kBrafHO4yJGZZ9GpP7I7oQxUtwvQSB8Bis/L/BtH IxYooOcVkE+d84VlrCOuzIGEIiMAPjABnf7pDcJa34hJKIsKWclmtouIPvPQkU+t Ley3tIKaUHQWu+vtvzpmfCmpoovF4Xa5lFv7WNEDz0LYHnDb6mSRIjZTa7NCzzww == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 30377246D8; Thu, 4 Jan 2018 13:32:40 -0500 (EST) From: Thomas Monjalon To: Hemant Agrawal Cc: dev@dpdk.org, stephen@networkplumber.org, bruce.richardson@intel.com Date: Thu, 04 Jan 2018 19:32:20 +0100 Message-ID: <3307824.7b7B2xNfMZ@xps> In-Reply-To: <1513678481-30653-1-git-send-email-hemant.agrawal@nxp.com> References: <1513600744-13749-1-git-send-email-hemant.agrawal@nxp.com> <1513678481-30653-1-git-send-email-hemant.agrawal@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v5 1/4] 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: Thu, 04 Jan 2018 18:32:41 -0000 19/12/2017 11:14, Hemant Agrawal: > 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 uses of a single line reference to > Unique License Identifiers in source files as defined by the Linux > Foundation's SPDX project https://spdk.org. > > 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 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 as the top line of the file. > > SPDX-License-Identifier: BSD-3-Clause > > Note: Any new file contributions in DPDK shall adhere to the above scheme. > It is also recommended to replace or at least amend the existing license > text in the code with SPDX-License-Identifiers. > > Any exception to DPDK IP policies 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 first listed. > 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: 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 > Acked-by: Stephen Hemminger Acked-by: Thomas Monjalon Applied, thanks