Alexios: good catch, though even printable may be too generous. A colon is printable and not a supported in a Windows file name for instance. Jilayne: We could/should more simply list the allowed

My only comment would be to change “ASCII characters” to “ASCII printable characters”. Looking at the Overview page, it needs a little care: It documents “Is OSI approved?” but not

Hi all, As discussed on the call today (related to Issue https://github.com/spdx/license-list-XML/pull/651 ), we will add an explicit statement regarding not duplicating identifiers in the explanation

meeting minutes posted: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-06-14 Jilayne SPDX Legal Team co-lead opensource@...

Thanks both - this and the changes/deprecation of the existing exception will be in the soon-to-be-released v3.2 of the SPDX License List Jilayne SPDX Legal Team co-lead opensource@...

We’ll pick up where we left off last meeting! Cheers, Jilayne SPDX Legal Team co-lead opensource@...

All, The conversion to the new email system is complete. Best regards, Jack Manbeck

All, Hopefully you have seen the email from the Linux Foundation on the our mailing list migration which will occur tomorrow, June 13th.You can get an overview of the new feature’s here. I have

Hello everyone, I wanted to share the information of the work done on the XML editor which is my GSoC'18 project. Till now a stable version of text-based XML editor has been pushed to the xml-editor

So, is there anything I can do that would help move this topic forward? If so, I'm happy to do so. A few of us talked about this at LibrePlanet (IIRC). Since it's essentially the only mechanism

Thanks Andy, We have received your request and will review with the SPDX legal team. Progress and comments will be available here. Best, Brad -- Brad Edmondson, Esq. 512-673-8782 | brad.edmondson@...

Hi all, Not having heard a response re: versioning, we discussed on the SPDX legal call today and agreed to version by date. This will be included in the 3.2 release of the SPDX License List, slated

Hi; OK, I see the reasoning. On one hand the license does seem identical, on the other hand we are already using the *-FreeBSD tag extensively and I am too lazy to change it ;).

I apologize; I wasn’t clear enough. I meant to say that, since the last line is not part of the license text, then your license is identical to “BSD-2-Clause” and you should be using this SPDX

Full Name: OCaml linking exception Short Identifier: OCaml-linking-exception Reference to exception text: https://github.com/ocaml/opam/blob/master/LICENSE Exception text is attached as

Hi Alexios; In all honesty, I don't understand how BSD-2-Clause and BSD-2-Clause-FreeBSD (or -NetBSD) are supposed to differ. FreeBSD is not being "creative" with the license: it is

Thank you for this info. If the last line is not part of the license, do you see any difference between your license and the pure BSD-2-Clause one (https://spdx.org/licenses/BSD-2-Clause.html)?

Hello guys; After internal discussion FreeBSD has decided to further simplify the license by dropping the "All Rights Reserved." line from the license used in FreeBSD. IANAL but it

Thanks John! It was a reason like that which I think led to the initial decision. But given that was a number of years ago, we were wondering if such an issue was still relevant today. You have

J Lovejoy <opensource@...> writes: Swear words also cause web pages to get blocked by filters/proxies, especially in US public schools. -john -- John Sullivan | Executive Director, Free