Hello all, The next SPDX legal team call will be tomorrow, June 13 at 12:00PM ET / 9:00AM PT. The agenda will be focused on identifying which of the many open issues can be finalized prior to the 3.6

A big round of applause for Karen’s well-deserved retirement, both Steve’s and Jilayne’s new positions, and, of course huge kudos for all the work all four of you have put into

+10 From: "spdx-legal@..." <Spdx-legal@...> on behalf of "mdolan@..." <mdolan@...> Date: Thursday, June 6, 2019 at 11:44 AM To: Jilayne Lovejoy <opensource@...> Cc: "spdx-legal@..."

"Michael Dolan" <mdolan@...> writes: +1! :) -john -- John Sullivan | Executive Director, Free Software Foundation GPG Key: A462 6CBA FF37 6039 D2D7 5544 97BA 9CE7 61A0

Thanks Mike!

Jilayne, congratulations on your new role! We all owe YOU a massive thank you for the countless (and mostly thankless) hours of contribution and leadership to this effort. Hopefully we won't see too

Hello SPDX legal team members, I wanted to inform you of some updates to the SPDX legal team membership. For some years now, Paul Madick, Karen Copenhaver and I have shared the SPDX legal team

Ok, thanks, Steve. I will try to help out. I have a bit of difficulty to participate in the calls due to my time zone, but I will also try to join those when possible. Cheers, Rob -- Steve

Hi Rob, anyone who is interested is welcome to participate. On the legal team biweekly calls we typically have a mix of attorneys as well as software engineers who are interested in FOSS

Hi all, Quick question: What type of expertise is needed to participate in the license review process? Kind regards, Rob Guinness FOSSID

Hi all, echoing Phil's comments -- several people have indicated interest in increasing the velocity of adding new licenses to the license list. I'd encourage anyone who shares this goal to

Hi Thomas, Sorry about the validation issue – the code is at https://github.com/spdx/spdx-online-tools Feel free to submit an issue and/or PR. We have an active group of Google Summer of Code

One consideration in this discussion is the practical limits of the legal team’s capacity. Adding a new license on the list requires a chunk of work and every license on the list adds

Hi Thomas, I've added an issue report for this request at: https://github.com/spdx/license-list-XML/issues/874 -- Steve Winslow Director of Strategic Programs The Linux Foundation swinslow@...

Hi Thomas! <thomas.steenbergen@...> wrote: FWIW, I agree this is rather common in the wild. It has been tracked and detected as "apple-runtime-library-exception" in the scancode-toolkit since

Hi, I would like to request below license exception to be added to the SPDX specification. This exception is popping up in open source project related the Swift programming language maintained by

Hi all, I realize I am new to this group, but I just to add my two cents: We are using the SPDX License List within our open source auditing tools, and when a license is not on the SPDX list, we have

It's true that many folks only use SPDX for the license list, to code their own license information in package manifests. But npm defines its own magic values for unidentified licenses. Those values

Phil Odence: > And, also, bear in mind that SPDX can handle any license. Worst case, you identify a local license identifier and include the license. The goal of the license list is to minimize the

And, also, bear in mind that SPDX can handle any license. Worst case, you identify a local license identifier and include the license. The goal of the license list is to minimize the need to do that,