Hi all, We are going to aim for the end of next week for the 3.14 release - giving everyone an extra week to tidy up any outstanding issues. So, if you haven't gotten to something, you have a bit more

Hi Legal, Tech teams, I just want to clarify my understanding of capitalization sensitivity for SPDX license ids and license expression operators: Appendix IV states: License expression operators (AND

Hi Max to clarify: the FSF turned down GPL-3.0* WITH LGPL-3.0* or GPL-3.0* AND LGPL-3.0* (as you understand it, not asking you to speak for the FSF) Having the discussion and getting input from the FS

I meant to add: our next legal call is Thursday, Aug 5th at 10am mountain time. Happy to dedicate some time then to this topic, if a live-discussion would help and all interested parties can attend.

This is a problem. We already went down this road with having back-and-forth conversations with FSF (by way of Richard Stallman and John Sullivan) in 2018 when Richard Stallman wanted us to change the

Hi Max, Do I understand correctly that FSF still doesn't think of LGPL-3.0 as an exception to GPL-3.0 (even though functionally and structurally it is) and thus wants us all now to identify LGPL-3.0 a

Hi SPDX-legal, I've been chatting to some of the Fedora folks about adopting the use of SPDX license identifiers in its package spec files. I just posted a comment/ proposal to a PR that was opened so

Hi all, We have our regular meeting today at 10am mountain time via https://meet.jit.si/SPDXLegalMeeting We will focus on what can be wrapped up for the 3.14 release at the end of this month! Thanks,

Jonas, Is using the phone dial-in still objectionable or not an option? Just wondering. Thanks! Jilayne

Hi legal folks, Steve and I are doing a bit of clean-up on the SPDX License List Github repo to make sure everyone has the right access to easily be able to contribute there. A bunch of you will have

Hi Gary, We had some updated text for the description of deprecated licenses which goes on the license list landing page. Should I simply make a pull request in the license-list-publisher repo? Thanks

Hi all, Just a reminder that we have our regular call today at 10am MDT. We will focus on wrapping up as much as we can for the next release. Please have a look at the issues labeled for 3.13 if you h

Hi all, I just made a couple PRs to improve some of our documentation in the Github repo as per prior discussions. It'd be great to get some eyeballs on that and comments as to any other improvements,

Hi Gary, Bhavya, I too do all my SPDX-related work on my laptop/desktop setup. I’d be curious to hear if there are others who use their mobile. Thanks, Jilayne SPDX legal team co-lead

Thanks Gary! Legal team: note I added an issue here: https://github.com/spdx/spdx-online-tools/issues/252 to request some text at the top of the page encouraging people to read the license inclusion p

Hi all, In follow-up to Steve’s email and invite - we will resume our joint legal/tech team review of the License Profile draft on the legal call this week (Thursday) and the next tech team call (next

Hi all, Tomorrow’s regularly scheduled legal team call will be a joint call with the tech team to continue the conversation about the licensing fields and consolidation of such for the 3.0 spec. By wa

< bcc general list as FYI for anyone who wants to follow the discussion, but moving to legal list> Quick search shows: - both version were on the list when we moved to the XML format in 2016 - email a

Hey folks, Gary has a CommunityBridge funding drive for the online SPDX tool. To support SPDX, an online tool has been developed which provides an easy all-in-one website to upload and parse SPDX docu

Hi all, I merged the minutes from the last 3 meetings: https://github.com/spdx/meetings/tree/master/legal I also updated the wiki to remove the outdated conference call info and add a link to the new