linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Add SPDX identifiers
Date: Mon, 24 Jun 2019 12:36:32 +0200	[thread overview]
Message-ID: <693753473768100f07de573dd74bf4033618aed8.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGm1_ksic4xcVdaPAObwwNdaQ19E3ZiK97SkmVmp8kz6H2KpOw@mail.gmail.com> (sfid-20190624_120805_586448_B9232B91)


> > 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


  reply	other threads:[~2019-06-24 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 13:01 [PATCH] Add SPDX identifiers yegorslists
2019-06-24  9:01 ` Kalle Valo
2019-06-24  9:45 ` Johannes Berg
2019-06-24 10:07   ` Yegor Yefremov
2019-06-24 10:36     ` Johannes Berg [this message]
2019-06-24 20:32       ` Yegor Yefremov
2019-06-28 13:58         ` Johannes Berg
2019-07-17  9:22           ` Yegor Yefremov
2019-07-17  9:28             ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=693753473768100f07de573dd74bf4033618aed8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yegorslists@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).