SPDX License List 3.22 - working session Scheduling this as an optional, open session for folks to drop in and help with working through the open issues in the license-list-XML repo prior to the upcom

Hi all, Here is a list of issues that need review: MPEG - https://github.com/spdx/license-list-XML/issues/2049 pnmstitch - https://github.com/spdx/license-list-XML/issues/2046 glibc startup code excep

Hi all, I was hoping to get a new list of issues to review out prior to this, but time slipped away from me! For Thursday's meeting, I'd like to focus on the issues labeled "XML markup change" - pleas

jimv@... has invited you to SPDX Legal Team - 4th Thursdays 2023

swinslow@... <swinslow@...> has canceled this event: SPDX Legal Team - 2nd Thursdays 2023

jimv@... has invited you to SPDX Legal Team - 2nd Thursdays 2023

swinslow@... <swinslow@...> has canceled this event: SPDX Legal Team - 4th Thursdays 2023

No worries James! These weird things happen! This is a good opportunity to remind people that we have the meeting details here https://github.com/spdx/meetings#legal-team-meetings — including a link t

PLEASE NOTE: this invitation is in error. Apparently, our IT person was upgrading/updating various apps. As far as I understand, it appears that my acceptance years back of the invitation to join the

SPDX Legal call Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 Join the call: https://www.uberconference.com/spdxteam Optional dial in number:

Hi Sebastian, Thanks for the update! I'm copying the SPDX-legal team as well, as I think many people there might be interested in this. I had actually tried to learn more about Cavil a year or so ago

Hi all, We have our regular call in about half hour at https://meet.jit.si/SPDXLegalMeeting Please review the following issues to cover during the call: https://github.com/spdx/license-list-XML/issues

Hi SPDX-legal, We currently have 24 license requests that need review. Links below, please contribute your valuable input! It’d be preferable if to all decisions were just Steve and I. Reminder - for

Hello spdx-legal and spdx-tech teams, As you may be aware, all SPDX specification versions since 1.1 have required that SPDX documents have a “DataLicense” value of CC0-1.0. Details about this in the

Hello all, For anyone who is interested, the Software Engineering Maintenance and Evolution Research Unit (SEMERU) lab at William and Mary is running a new survey relating to third-party software lice

Thanks for the productive call today! I'm revising the list below of issues that need input :) The following licenses have already been reviewed by Steve as a +1 to add and just need one other person

Hi all, A quick reminder that we have our SPDX-legal meeting coming up on Thursday at noon Eastern time at https://meet.jit.si/SPDXLegalMeeting The monthly general call will be just prior. We have a b

Hi David, This may be better for the legal team as they maintain the source repository for the license list. However, I can answer your question since I maintain the tools that produce the JSON data (

I just finished upgrading the software and hardware for the SPDX online tools. For a list of change, see the release notes at https://github.com/spdx/spdx-online-tools/releases/tag/v1.2.1 The compute

Hi SPDX Legal, Would it be beneficial if I made a pull request to license-list-XML replacing every <alt name="copyright"> with equivalent <copyrightText>? (See discussion in spdx-implementers)