From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05604C04AB5 for ; Mon, 3 Jun 2019 13:00:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BCDA027FA3 for ; Mon, 3 Jun 2019 13:00:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="e6rPQSid"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="1FmoGFQ1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727822AbfFCNAf (ORCPT ); Mon, 3 Jun 2019 09:00:35 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:43287 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726336AbfFCNAf (ORCPT ); Mon, 3 Jun 2019 09:00:35 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E81C522269; Mon, 3 Jun 2019 09:00:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 03 Jun 2019 09:00:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=YM9HH3GFjpL77TKhPPfeMTD+mhO pSjtn00sKenaM28Y=; b=e6rPQSidTcDsgQXC1iUjmHprmEEP1ZqGvLPT2kcIzL9 upVUb+kzpflLGd09WVnBBcet1PKazWh/amLc2lTmv6c1Gn5nsE2QyfTN8/UrrBHK XHXdCGd7xlKxymGK3VOsD5s0HwknnO8OdoVFl4WUBNGerjvp+d3jCJp5bhKksQa7 FT5PeMINbPVZJRQLbR6VVHygWF+mRzHywAR0v6C2rgqifuG7pmFNN94yPtcWtMYd 5d9Moh4Qalm8dqCZnxK9F1ftXHqTRXREmlGY8AJ9z1Z2jTrpUGqwWSk6TYIBUalJ lzbi6MR0DmKyCMnzIW1mgcO/naK0lYngcqmgcRxT1VQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=YM9HH3 GFjpL77TKhPPfeMTD+mhOpSjtn00sKenaM28Y=; b=1FmoGFQ1tCtW7H+0Fh5jSK +9hjpWgU730DDI2w/hpB1zz7bQz404s/0LjvMUHQAQX+8QeTJo7rRVUsCtxqUyHR uQ5pp4o11jPuoZ5KDPa/jGvVQa5B9KQJKH/rCpGJKwSrZ6EPeU14Qu1BnxodOYdK 3P9dbzdf8ymFOyg6DPxO5jUpSTlxUKsdkFX+qU8i0lXWzts+QNm5RoMIBHUTE8C7 pwx7Eu1l8RYT5VamxdydBWsQAKF5Uz+HRo40D2Zl0JB3eU5RjDCho9BzOyQkHlon /8xq6kPK3IfXCVj9i721FusW2kYJx2EAM5YNqxfMPpb4VxP/qW5zmMJ14Bld7Gzg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudefjedgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecukfhppeekfedrkeeirdekledrud dtjeenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhmnecu vehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id BDB1080068; Mon, 3 Jun 2019 09:00:31 -0400 (EDT) Date: Mon, 3 Jun 2019 15:00:29 +0200 From: Greg KH To: "Enrico Weigelt, metux IT consult" Cc: Armijn Hemel - Tjaldur Software Governance Solutions , Thomas Gleixner , linux-spdx@vger.kernel.org Subject: Re: [Batch 16 patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 226 Message-ID: <20190603130029.GA30254@kroah.com> References: <20190602204441.312079455@linutronix.de> <20190602204653.087533673@linutronix.de> <1a0494fe-8925-39e0-c57d-7f19fdda98e6@metux.net> <63f9b07d-248d-c813-705c-60810b95a8c4@metux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <63f9b07d-248d-c813-705c-60810b95a8c4@metux.net> User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org On Mon, Jun 03, 2019 at 02:36:58PM +0200, Enrico Weigelt, metux IT consult wrote: > > Also, author doesn't necessarily mean copyright owner, company > > affiliation also does not necessarily mean copyright is with the company > > (it depends on the work contract) and it would require a lot more > > research to find the true copyright owner. > > > > The copyright statements also have other relevant information, such as > > years. This is relevant to find out which copyright laws were in effect > > when the code was published. > > hmm, maybe we should start w/ introducing some rules for that for all > new code ? > > Maybe: > > Rule 1: If not stated otherwise, the Signed-Off-By indicates the signer > claims copyright for the added or replaced lines of code. > This only affect any lines of code that were already present > (and unchanged) before these rules taking effect. > Rule 2: New files shall have some SPDX-Copyright: header (checkpatch > should check for that). > Rule 3: If the SPDX-Copyright header is present, all mentioned authors > claim copyright for the whole file, except for claims from other > rules. > Rule 4: For existing files, SPDX-Copyright header may be added on a per- > case basis, when actual copyright claims have been validated. > Rule 5: If the author is transferring his claims to some company, this > company shall be mentioned in the Signed-Off-By or SPDX- > Copyright headers. > > Certainly, it will take a long time, until everything is really cleared > up, but IMHO a good start, at least for all new code. That's crazy, again, if people want to talk about SPDX-Copyright or anything like that, please bring it up on the SPDX mailing list, not this one, as that's not what this list is for (it is for applying the _existing_ SPDX _LICENSE_ tags to the kernel source tree>0 thanks, greg k-h