Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp653767ioo; Thu, 26 May 2022 11:24:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwVqhkzwaARxQsgr6axMjz9hrlNt7RBeP9vzWNmvpJfzf01hpH5dadTNmUxpSFpwLPY9T7w X-Received: by 2002:a17:907:381:b0:6fe:9ca8:c4b4 with SMTP id ss1-20020a170907038100b006fe9ca8c4b4mr32750636ejb.147.1653589452426; Thu, 26 May 2022 11:24:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653589452; cv=none; d=google.com; s=arc-20160816; b=gSLKamwPicX0O2MndH+GrxrXn+fkJW1VkzzCZl2hMhe5VlhA0CqMsaBlIkH6VFCQjd Jfw2Jt3CBu+ii7AvooDmoMgeCsyO+h5o6BEQbSp8nExyt8fgT6q+OVCwVjSTYR4DD2B4 oPqmFbgbkLc9kVRFM+BRkFdQiVeXSbSuM/TqAPOMR/rs2J98W+N05TLuT2GkD3Lg6/ZD 5MRLKTYRaK26ePUgj66ZGn/LGCrJMKxJemotYzbeX60rxvQJ/ceBtLY7sPVs37ZT3COa rv2qSjyZ9ffzC7ZkHIV2JJsU7c3uDcZdKUbkGmRHFXiv7BL7uRoDudFj6IIeS0g63C33 iphw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:message-id:in-reply-to:date:face:references:organization :subject:cc:to:from; bh=Rxxpl8wi5udwDtAZfHj759QhWUP6o2UOqgAnzptT0z8=; b=w899PPzr58oaAZGKrf3lyFN+3i9+j7HcR9ohMnUm9FBzfDuCqIZQRf34qtScOug/px 4piNtPYjw4DMlGfIfsmIgM755eKZw8Sckj4lUyh2Va7fKjaQ3uIjIA2pct60J0aKK46K +4khbjdfuoQFzObHv/ctTPujxYTduPOVCbY24t7+kmzsIze7OkKZtq3Fg2XtQwbQhb7g iAh/c5ss7XjUN0S+cHfFogxuZ//LNu/7P+vu6zd2Rm6z0fE9eI4iq2X6rNfgbRQxm2z8 rEgoQ/3LYmmAiGOxBtTs+2d7HQVFIJ9DKreM1vmIRYZNyH3CUGiUQAL4uTnhqmPCIP3w tJNQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ga26-20020a1709070c1a00b006f39bdc4dfesi2338775ejc.545.2022.05.26.11.23.44; Thu, 26 May 2022 11:24:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236096AbiEYTw1 convert rfc822-to-8bit (ORCPT + 99 others); Wed, 25 May 2022 15:52:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241221AbiEYTwX (ORCPT ); Wed, 25 May 2022 15:52:23 -0400 X-Greylist: delayed 1200 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Wed, 25 May 2022 12:52:22 PDT Received: from protestant.ebb.org (protestant.ebb.org [50.56.179.12]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0D08D630B; Wed, 25 May 2022 12:52:22 -0700 (PDT) Received: from localhost (unknown [216.161.86.18]) (Authenticated sender: bkuhn) by protestant.ebb.org (Postfix) with ESMTPSA id 9D99C820B4; Wed, 25 May 2022 12:14:38 -0700 (PDT) From: "Bradley M. Kuhn" To: Thomas Gleixner , copyleft-next@lists.fedorahosted.org Cc: Luis Chamberlain , tj@kernel.org, gregkh@linuxfoundation.org, akpm@linux-foundation.org, jeyu@kernel.org, shuah@kernel.org, bvanassche@acm.org, dan.j.williams@intel.com, joe@perches.com, keescook@chromium.org, rostedt@goodmis.org, minchan@kernel.org, linux-spdx@vger.kernel.org, linux-doc@vger.kernel.org, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, Goldwyn Rodrigues , Kuno Woudt , Richard Fontana , Ciaran Farrell , Christopher De Nicolo , Christoph Hellwig , Jonathan Corbet , Thorsten Leemhuis Subject: Re: [PATCH v9 1/6] LICENSES: Add the copyleft-next-0.3.1 license Organization: Opinions expressed in this email are my own and are not necessarily those of any organization with which I have an affiliation. References: <20211029184500.2821444-1-mcgrof@kernel.org> <20211029184500.2821444-2-mcgrof@kernel.org> <87h75g0xbm.ffs@tglx> Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAABVQ TFRFAAAAWjotvpiH/PHt27Sj7sq8lXFeBchlBgAAAAFiS0dEAIgFHUgAAAAJcEhZcwAACxMAAAsT AQCanBgAAAAHdElNRQfiCx4VFw6omMmeAAACAklEQVQ4y43UPZPbIBAGYGdu0puzQ51bI+qMdXId r0F1RoLrwfb+/5+QF307VVR4PDxiF14h7Xa7t3q8LJGjavj7a1euCYiZnaPnv9DF4FyMLKdXOPs4 XM7KKzzKaF83gem+hUuF8QYUg7Fb4LEQAK1OG3hu4bbC3LpUC87+B9AMfQOg0yv0owEOK4x1+gnu M3yaV3jOMGxvKoXEKC9gAoabJtZYlXO8wJcb1hMHQClZgSj7cbzsY4a2vSqltIlz8nMpZnMkEmVw N4DtcYJo3AMPXFIMRMax/BjhOxZi2CpKKpWSZCd4C8aZ4CpzjR+Cint9WEp5H12IbbySEpHdaYVh OY9onf0Qq9//zDCFEW0MbFjUz7mHD1UdO4B3iErk9whdKdWVRuW5YLl5KnU2rjTBDyPmQImm5mec WQx7X3fBNwAzQ9kvBTKR0BwR3Bewhisn2mpkhea3BZwBcdorRlQk9QKecyZukRPeHTmuEL1FdjlJ tmTlvoAJPnRaMnKinNICn4QthNaKlNAlLae9sc5UODaelVh+l345u7ZMIY89GNdmWV8cIaTFlLGm QKLrzQykh/Aw02WsdoE2l1g7JIPdyWGFL6Hy1uJZsEjavLUXkVyeIdrbpPoXQHxDG0l68wEoW8vG BLI6qc2XoUEWCUI26aQfK1wypuwV7v6mtMhtgL8avOP/pBCiigAAAABJRU5ErkJggg== X-Disclaimer: Opinions expressed in this email are my own and are not necessarily those of any organization with which I have an affiliation. Date: Wed, 25 May 2022 12:13:45 -0700 In-Reply-To: <87h75g0xbm.ffs@tglx> (Thomas Gleixner's message of "Mon, 23 May 2022 23:10:37 +0200") Message-ID: <87y1yph1cm.fsf@ebb.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In answering Thomas' question … Thomas Gleixner wrote at 14:10 (PDT) on Monday: > If I want to remove this option, then how do I express this with a SPDX > license identifier? … some licensing/SPDX background is in order. (I apologize in advance for a few paragraphs of license-splaining, as I know that many on this thread know these points already, but I suspect most only have only vague familiarity with this issue.) copyleft-next 0.3.1 reads: >> +11. Later License Versions >> + The Copyleft-Next Project may release new versions of copyleft-next, >> + designated by a distinguishing version number ("Later Versions"). Many don't realize that GPL is (or was, pre-copyleft-next) unique in structure among copyleft licenses in that the -or-later clause of all licenses in the GPL family is configurable. That yields the complex forms of: GPLv1-only, GPLv1-or-later, GPLv2-only, GPLv2-or-later, etc. GPLv3 even added the proxy upgrade clause (— a formulation SPDX can't handle at all). Other non-trivial FOSS licenses — such as Mozilla Public License (MPL), Common Development and Distribution License (CDDL), and Eclipse Public License (EPL) (as just three examples) — all have “automatic -or-later”. Thus, “MPLv2.0” *always* means “MPLv2.0-or-later”, so if you use the SPDX moniker for that (“MPL-2.0”), it really is akin to using “GPLv2-or-later”. Meanwhile, there is no *actual* way to license code under “MPLv2-only” — the license text itself prohibits it. All that's to say: the GPL has (historically) always been a huge FOSS licensing special-case because of the complex configurability of its “-or-later” clause. One of the last activities I did with SPDX (in late 2017) was to help negotiate a solution on reworking the GPL identifiers to deal with this special case. The solution was a classic political compromise — where *everyone* left unhappy — but that's what led to the deprecation of SPDX's “GPL-2.0” identifier in favor of “GPL-2.0-or-later” and “GPL-2.0-only”. I wasn't involved with SPDX anymore when they (much later) created the identifier “copyleft-next-0.3.1” — but it appears it was a case of “those who forget the past is condemned to repeat it” — because copyleft-next's SPDX identifier indeed has a similarly confusing ambiguity to “GPL-2.0”: copyleft-next 0.3.1 text reads further: >> + Unless I explicitly remove the option of Distributing Covered Works >> + under Later Versions, You may Distribute Covered Works under any Later >> + Version. Thomas Gleixner noted about it at 14:10 (PDT) on Monday: > If I want to remove this option, then how do I express this with a SPDX > license identifier? Sigh! So, this problem that Thomas notes above is definitely an error by the SPDX project, *just like* the one that exists for the deprecated “GPL-2.0” identifier. But, that isn't copyleft-next's fault [0], nor Luis's fault. IMO, Luis shouldn't be punished (i.e., by being prohibited by the Linux project from licensing under the GPLv2-compatible terms of his choosing) simply because the SPDX project erred. Fortunately, the problem *is* hypothetical here because Luis has *not* indicated that he's licensing under “copyleft-next-0.3.1 REVOKING new-version-upgrade”, so it's not a problem for Luis' patch that SPDX offers no way to represent that licensing sub-option in copyleft-next. [0] Nevertheless, I am wondering, given that (a) opting-out-of-auto-upgrade is *so* GPL-specific, and (b) the auto-upgrade opt out has caused decades of pain and woe throughout the GPL-using community (and for SPDX!), maybe copyleft-next should, in fact, drop that clause entirely in future versions. Discussion of that is likely not of interest to most folks on this wide thread, so I'll pick up that conversation more narrowly just on the copyleft-next list from here … -- bkuhn