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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A336BC433FE for ; Wed, 25 May 2022 23:54:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242657AbiEYXyR (ORCPT ); Wed, 25 May 2022 19:54:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33884 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229824AbiEYXyP (ORCPT ); Wed, 25 May 2022 19:54:15 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 147B69D070; Wed, 25 May 2022 16:54:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=l4fKDERpiICSOVgCQ8QwCarZ+nXg0XUnq0ATowURuHc=; b=dzwK7kFgMsM4dtgzFXJxmWXZFa u+Q7RFwB4jvwWWz8PwBDLQpHj4ZK0YGZiyHU+lI4x2bdXw5XdPK1jJ4rxeSbi0iM9LtMiUjwiCMGK sk07Lf4YOWErKZDftjL5EUS6bSB+I4To98jq/cbHVJYzq336XwpuNwFstUEWVUW911uW9NiZh86Dl glQIo5lGtlpAyKujL6jZzNtS5izUCyWSs8RcUticJXAxL0UBNTsem/IXOFrXk02tosz4FEzKSD99r HjN3iYpVp6vLptw5OEzyRio/9aMzIA5bMm9QOG5QhrN7Gz3D7nlgWgRVNkbVz4ahCkN4/pjws9RbT LUmv21/A==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nu0pC-00CynK-Py; Wed, 25 May 2022 23:53:58 +0000 Date: Wed, 25 May 2022 16:53:58 -0700 From: Luis Chamberlain To: Thomas Gleixner Cc: Richard Fontana , 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 , copyleft-next@lists.fedorahosted.org, 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 Message-ID: References: <20211029184500.2821444-1-mcgrof@kernel.org> <20211029184500.2821444-2-mcgrof@kernel.org> <87ee0k0wrn.ffs@tglx> <874k1dz674.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874k1dz674.ffs@tglx> Sender: Luis Chamberlain Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Wed, May 25, 2022 at 10:51:43PM +0200, Thomas Gleixner wrote: > On Wed, May 25 2022 at 09:57, Luis Chamberlain wrote: > > On Mon, May 23, 2022 at 11:22:36PM +0200, Thomas Gleixner wrote: > >> This paragraph is not really understandable for Joe Developer. > >> > >> copyleft-next-0.3.1 is explicitly compatible with GPLv2 (or later) and > >> can therefore be used for kernel code. Though the best and recommended > >> practice is to express this in the SPDX license identifier by > >> licensing the code under both licenses expressed by the OR operator. > >> > >> Hmm? > > > > Let me try clarifying this further, how about: > > > > copyleft-next-0.3.1 is explicitly compatible with GPLv2 (or later) and > > can therefore be used for kernel code. Despite this, if you use > > copyleft-next-0.3.1 on Linux, the recommended practice is to express > > dual licensing with GPL using in the SPDX license identifiers by > > using by the OR operator. > > 'using in the ..' ? > > and > > 'by using by' is off by one 'by' :) > > I'm not seeing how that clarifies stuff further. I might be biased, but > the version I suggested is crystal clear. Oh sorry, I didn't realize the paragraph you posted was a suggestion, I thought it was the one you were indicating needed further enhancement! I'll just take yours then. > >> > + To use the copyleft-next-0.3.1 license put the following SPDX tag/value > >> > + pair into a comment according to the placement guidelines in the > >> > + licensing rules documentation: > >> > + SPDX-License-Identifier: GPL-2.0 OR copyleft-next-0.3.1 > >> > + SPDX-License-Identifier: GPL-2.0-only OR copyleft-next 0.3.1 > >> > + SPDX-License-Identifier: GPL-2.0+ OR copyleft-next-0.3.1 > >> > + SPDX-License-Identifier: GPL-2.0-or-later OR copyleft-next-0.3.1 > >> > >> Please don't propagate the GPL-2.0 and GPL-2.0+ tags. They are > >> outdated (still valid) in the SPDX spec, which reminds me that I should > >> update the relevant documentation... > > > > OK thanks for the recommendation, I'll leave it at: > > > > + SPDX-License-Identifier: GPL-2.0 OR copyleft-next-0.3.1 > > SPDX-License-Identifier: GPL-2.0-only OR copyleft-next-0.3.1 > > please. See my previous reply quoted above. > > > + SPDX-License-Identifier: GPL-2.0-or-later OR copyleft-next-0.3.1 Sorry I hadn't had my coffee yet so I should only list: SPDX-License-Identifier: GPL-2.0-only OR copyleft-next 0.3.1 SPDX-License-Identifier: GPL-2.0-or-later OR copyleft-next-0.3.1 Will do this on the next spin. Luis