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=-6.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS 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 E9F86C04AB3 for ; Mon, 27 May 2019 21:54:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 97AC32075E for ; Mon, 27 May 2019 21:54:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="K4eyWQ+F"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=lohutok.net header.i=@lohutok.net header.b="MPLHLJsh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726979AbfE0VyN (ORCPT ); Mon, 27 May 2019 17:54:13 -0400 Received: from pb-smtp20.pobox.com ([173.228.157.52]:56288 "EHLO pb-smtp20.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726905AbfE0VyN (ORCPT ); Mon, 27 May 2019 17:54:13 -0400 Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 013E66884A; Mon, 27 May 2019 17:54:11 -0400 (EDT) (envelope-from allison@lohutok.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to:cc :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=5OkaRoiI08e+ lvqj89QBDXaJsjQ=; b=K4eyWQ+FmQxoZAadPOhwr5iosFbWtbVIC4V20Lrp7NlL +EhlSz000wH+BDDHD1EiR8CQimUV06nF7fR5BtmORM3KbkagfsGn1KKIS0ooaat4 /vDw1IuQ9ffzmIv2Si8qI570rQOdzZrpcdR2XX/xb3RobfJCDFjCZO0rS5dQVoM= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id E155A68849; Mon, 27 May 2019 17:54:10 -0400 (EDT) (envelope-from allison@lohutok.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lohutok.net; h=subject:to:cc:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=2018-11.pbsmtp; bh=zuglSzl99MfeFOCSVvBHqH94dvfWkDytJEwe4gRR/Xg=; b=MPLHLJshMdUSZYOvLP6ZQJ6iPKnAltyJaMEKKQeY/MYZ4hLyOgDiR9V32QsPat1AfyBctBz5Pzzq+S2LbJsTxtZPafzeaNy9foHtZjzkLn8oYYSKXKPo/xSr8RKNwrDQgCOGK5I04Z9jkijaf7zFwZ0lnolWuvR7ZxQpo+mUO+A= Received: from [10.0.0.75] (unknown [24.47.52.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id 7DD0E68848; Mon, 27 May 2019 17:54:07 -0400 (EDT) (envelope-from allison@lohutok.net) Subject: Re: Meta-question on GPL compliance of this activity To: Greg KH Cc: linux-spdx@vger.kernel.org References: <20190521210833.veltn74dcgic5zmw@ebb.org> <0995848C-11BE-47B1-86F9-F56D43541246@jilayne.com> <20190524052026.GA28229@kroah.com> <20190525165643.GA13394@kroah.com> From: Allison Randal Message-ID: Date: Mon, 27 May 2019 17:54:05 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <20190525165643.GA13394@kroah.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: F3B21AC8-80C9-11E9-90EA-B0405B776F7B-44123303!pb-smtp20.pobox.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org On 5/25/19 12:56 PM, Greg KH wrote: > > Again, remember we have over 65 thousand files in the kernel source > tree. Any single file that tries to reference them all, in any form, is > going to be unworkable. Yeah, we wouldn't be looking to track every single license notice change throughout history, that wouldn't be reasonable. We want to narrow it down to specific sets of changes that removed license notices and replaced them with SPDX identifiers. And, ideally, display those with the most minimal amount of information possible. It might even be reasonable to generate the page as a list of links to the pretty diff displays of the relevant commits, like: https://github.com/torvalds/linux/commit/fd534e9b5fdcf9bab33c03cb3ade1a1ae5b23c20 That's the most faithful capture of the removed license notices we could possibly provide, and is more accessible than simply saying that they're in the git history. But, it might not satisfy the most conservative definitions of "keep intact". It seems like we're weighing effort against effectiveness here, but without a clear definition of what effective means, other than our best guess at how "keep intact" might be interpreted by someone, somewhere, sometime. Allison