We have this on our “long” list of exceptions and noted to be added to the SPDX License List after the initial 2.0 release. As noted on the last call (and barring any objections from the Tech

Given the use in Virtualbox, this appears to be a good candidate for addition. Tom Tom Incorvia; tom.incorvia@...; O: (512) 340-1336; M: (215) 500 8838; Shoretel (Internal): X27015

Hi, I would like to propose the addition of LGPL with FLTK exception license to the SPDX license list, as follows: Short name: LGPL-2.0-with-FLTK-exception Long name: GNU Library General Public

Hi, Intel microcode files have a license similar to Intel's Open Source license (https://spdx.org/licenses/Intel), but it includes a term about reverse engineering. Intel

Hi, I would like to propose the addition of SGI’s GLX license to the SPDX license list, as follows: Short name: SGI-GLX-1.0 Long name: SGI GLX Public License v1.0 URL:

I would like to announce an upcoming SPDX webinar on Tuesday November 11th @ 12pm PST - it will include a commercial case study on how SPDX data was used in the license compliance review process

Hi Legal Team, A colleague of mine pointed out a couple possible issues on the SPDX License List, see full email below. Regarding Apache-1.1 and Entessa – I think those were probably treated

I personally like this plan. For the SPDX tools, I can update the license expression parser and test it out prior to the rest of the SPDX 2.0 changes. This would make the changes more incremental and

Are now posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2014-10-30 Note, we’ll continue to use this format for the next couple meetings and remove items completely once those items are

Hi Tech Team, For the pre-release of 2.0, the legal team will have the license exceptions added to the SPDX License List. The current plan is to be conservative on the initial release, only adding

http://wiki.spdx.org/view/Legal_Team/Minutes/2014-10-16 Meeting minutes from today’s call, which mostly followed up on remaining items from the 16th, will be posted shortly. Thanks, Jilayne &

Sorry for short notice. We’ll pick up where we left off from last call. Call this number: (United States): +1-857-216-2871 User PIN: 38633 International: visit the URL at

Agenda 1) Revised schedule for 2.0 update - SPDX Core Team met and discussed the schedule for 2.0: proposed idea is to do a release candidate of 2.0 by mid-November with the idea of getting people

Hi, I'd like to request that libtool's GPL exception be added to the SPDX license list, just like the autoconf exception, bison exception, and GCC exception already are. 1. Provide a proposed

Hi All, It was only Alan and I on the call today. We didn’t feel this was enough people to make decisions. However, we have work to do and a limited amount of time to do it in. “minutes” for

Hi, all. I'm on vacation and will not be on today's call. Look forward to being back in action for the next one. Have a good meeting. * * * * * * * * * * * * Thomas H. Vidal, Esq. Abrams Garfinkel

Hi All, For today’s call, please refer to the agenda and relevant links below. Chat soon! Jilayne & Paul SPDX Legal Team co-leads 1) Revised schedule for 2.0 update 2) License Matching Guidelines -

Hi Jilayne, I don't think that I have the authority to request a license for "The Linux Foundation"... What I am really asking is whether "The Linux Foundation" thinks this is the "BSD-3-Clause" or

Hi Steve, To clarify then, are you requesting this be added to the SPDX License List (officially)? If so, would you mind sending an email, using this format (or list of items) and then the SPDX

Hi All, It’s come to my attention that we have another license “version” issue… Zimbra 1.3 is on SPDX list - http://spdx.org/licenses/Zimbra-1.3 This license uses “VMWare” throughout and