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=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 B624DC43613 for ; Mon, 24 Jun 2019 10:36:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 86F782089F for ; Mon, 24 Jun 2019 10:36:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727953AbfFXKgf (ORCPT ); Mon, 24 Jun 2019 06:36:35 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:53472 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726774AbfFXKge (ORCPT ); Mon, 24 Jun 2019 06:36:34 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hfMKv-0007P1-2f; Mon, 24 Jun 2019 12:36:33 +0200 Message-ID: <693753473768100f07de573dd74bf4033618aed8.camel@sipsolutions.net> Subject: Re: [PATCH] Add SPDX identifiers From: Johannes Berg To: Yegor Yefremov Cc: linux-wireless@vger.kernel.org Date: Mon, 24 Jun 2019 12:36:32 +0200 In-Reply-To: (sfid-20190624_120805_586448_B9232B91) References: <20190620130148.1674-1-yegorslists@googlemail.com> <90ccc515bb26b212b537fc1b0287afaa0f86fdf8.camel@sipsolutions.net> (sfid-20190624_120805_586448_B9232B91) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-3.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org > > You haven't included any documentation that says what the SPDX > > identifier, and specifically the "ISC" tag means in the context of the > > project, and it's not even the same license text as on spdx.org. > > What about such definition? > > SPDX short-form identifiers provide information about licenses that > apply to the source file. It just bothers me that this isn't self-contained - you always have to go to spdx.org to really figure out what it means. > As for the exact license I wasn't sure myself. Buildroot identifies it > as ISC [1]. How do you define its license in SPDX terms? Not sure. Maybe you cannot? spdx.org says "ISC" is the license that says: [...] THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS [...] while the license here says: [...] THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS [...] (and the same in one other place) This might just be an oversight on spdx.org, since the license with "THE AUTHOR" *is* typically referred to as "ISC" (e.g. https://opensource.org/licenses/ISC), but it still means it's not actually identical? Maybe spdx.org should switch, but then it changing the license text ... what if anyone refers to it already? It's all not very obvious to me. The kernel side-stepped it and said "let's make it all self-contained", which seems saner to me. johannes