[...] Jilayne: Thank you for the detailed write up and hard work you are pouring into this! John and all: I find this whole discussion quixotic: noble but pointless! This ship has sailed IMHO long ago

The MODULE_LICENSE macro used in the kernel is a clear license statement. And better than a terse "Copyright (c) John Doe, GPL" that is seen in the kernel since there is a clear documentation of its m

FYI: In case you missed it: SPDX identifiers have landed in kernel land... Read the whole thread at https://patchwork.kernel.org/patch/10016189/ And as a side effect, some new patches elsewhere are co

<wayne.beaton@...> wrote: Wayne: This helps a lot to better understand the EPL terms. My understanding: I cannot use EPL 2.0-licensed code under a Secondary license unless I combine

Jilayne: Here are my 2 cents: - the text of the “assembly exception” is specific to the OpenJDK and derivatives: this code is used widely but there are very few projects that can use this licensing be

Trevor: Is this a joke or are you seriously suggesting that you want to track the license of licenses? Would there not be a risk of infinite recursion!? e.g. your GNUVerbatim license license should be

<wayne.beaton@...> wrote: [...] Hi Wayne! This syntax is not supported but I do not think this is what you want nor need exactly. Reading the EPL 2.0 I see: Licenses,.... So what th

The scancode-toolkit reports exact and approximate matches for all SPDX licenses (and a few more licenses). It also can collects the matched texts and report the scans either as SPDX or JSON. See http

Gary: I tried to paste the verbatim text of https://www.gnu.org/licenses/agpl.txt and its is not matched Do you think this a code or a matching guidelines issue?

Josh: you are getting this entirely backwards. Instead, for a license to be on the SPDX list it must have received adoption first. The purpose of the list is not to bless new licenses but to provide a

Thank you. Out of curiosity would you have a pointer to actual usage of this license in the wild?

Jilayne: What about tracking and keeping the original text too? Having only one text that is systematically marked up is not a great solution IMHO. For instance it makes the reuse of the text as-is im

Great catch! Just curious, how did you find this out?

Dear legal eagles [1]: I think that the text for the Sleepycat license [2] is not correct. The text is rather historical version of the BerkeleyDB aggregated licensing (which is now AGPL-licensed FWIW

A good news came in yesterday: SPDX has been accepted as a mentoring organization for the Google Summer of Code 2017 thanks to Gary's hard work. I look forward to contribute as an admin and mentor! Se

This all make sense. The only point is that the licenses are not the same, but are similar: the HPND has an additional warranty disclaimer. So I am not sure why this would ever be an issue matching-wi

On Tue, Sep 27, 2016 at 4:14 PM, Sam Ellis <Sam.Ellis@...> wrote: Sam: I have several issues with this "notice": 1- this is not a license: the way I read this text in contrast with its English cou

Jilayne: We have a license expression builder in DejaCode, but this not open source. There are two parts to it: a front end in JavaScript and a back end that validates expressions and provides the lic

I have a lot of respect for what you are embarking in: I would not dare editing by hand 100 of such XML files: I find this rather confusing and error prone. And I am a programmer... But I think I lost

+1