[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yo5jGMMctUP7i2dI@bombadil.infradead.org>
Date: Wed, 25 May 2022 10:10:48 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>,
Richard Fontana <fontana@...rpeleven.org>
Cc: tj@...nel.org, gregkh@...uxfoundation.org,
akpm@...ux-foundation.org, jeyu@...nel.org, shuah@...nel.org,
bvanassche@....org, dan.j.williams@...el.com, joe@...ches.com,
keescook@...omium.org, rostedt@...dmis.org, minchan@...nel.org,
linux-spdx@...r.kernel.org, linux-doc@...r.kernel.org,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
Goldwyn Rodrigues <rgoldwyn@...e.com>,
Kuno Woudt <kuno@...b.nl>,
copyleft-next@...ts.fedorahosted.org,
Ciaran Farrell <Ciaran.Farrell@...e.com>,
Christopher De Nicolo <Christopher.DeNicolo@...e.com>,
Christoph Hellwig <hch@....de>,
Jonathan Corbet <corbet@....net>,
Thorsten Leemhuis <linux@...mhuis.info>
Subject: Re: [PATCH v9 1/6] LICENSES: Add the copyleft-next-0.3.1 license
On Mon, May 23, 2022 at 11:10:37PM +0200, Thomas Gleixner wrote:
> On Fri, Oct 29 2021 at 11:44, Luis Chamberlain wrote:
> > preferred. A summary of benefits why projects outside of Linux might
> > prefer to use copyleft-next >= 0.3.1 over GPLv2:
> >
> <snip>
> >
> > o copyleft-next has a 'built-in or-later' provision
>
> Not convinced that this is a benefit under all circumstances,
I'll just drop it.
> but that's
> a philosopical problem. The real problem is this:
> > +Valid-License-Identifier: copyleft-next-0.3.1
>
> and
Why is this an issue?
> > +11. Later License Versions
> > +
> > + The Copyleft-Next Project may release new versions of copyleft-next,
> > + designated by a distinguishing version number ("Later Versions").
> > + Unless I explicitly remove the option of Distributing Covered Works
> > + under Later Versions, You may Distribute Covered Works under any Later
> > + Version.
>
> If I want to remove this option, then how do I express this with a SPDX
> license identifier?
Good question, souinds like generic semantics for SPDX evolution?
Luis
Powered by blists - more mailing lists