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

You have been invited to the following event. SPDX joint legal / tech team call When Thu Sep 24, 2020 12pm – 1pm Eastern Time - New

Hello legal and tech teams, This Thursday, September 24, will be a joint legal / tech team call. The call will be focused on continuing the discussions of the new "licensing" profile for SPDX 3.0. If

Greetings SPDX Tech and SPDX legal teams, A new URL for the SPDX online tools is now be available at https://tools.spdx.org. Please change any bookmarks or links from

Hello all, The next regularly-scheduled SPDX legal team meeting will be today, Thursday, Sept. 10, at 9AM PDT / noon EDT. Today's meeting will focus on reviewing and addressing questions from folks

Hello all, With apologies for the late reminder, the next regularly-scheduled SPDX legal team meeting will be today, Thursday, Aug. 27, at 9AM PDT / noon EDT. We'll start the meeting today with a

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

Greetings SPDX tech and legal team – I just posted minutes from our call at https://wiki.spdx.org/view/Technical_Team/Minutes/2020-08-11 A lot of good discussion, and I probably didn’t capture

My comments are in-line. Look for MDB: MDB My opinion is that the isMatch operator should be true/false only. I would also favor the addition of another operator with the name isValid for ensuring

Hi everyone, After discussing with mentors: Steve and Gary; we thought it wise to seek everyone's opinion on two topics: 1. Change back the isMatch field to Boolean(true/false) In the previous email

You have been invited to the following event. SPDX joint legal/tech team meeting When Tue Aug 11, 2020 1pm – 2pm Eastern Time - New York Where https://zoom.us/j/663426859

Hello all, The version 3.10 release of the license list is now tagged and live at https://spdx.org/licenses. This release included (as you’ll see below) a number of different variants on existing

< 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

Hello all, The next regularly-scheduled SPDX legal team meeting will be tomorrow, Thursday, July 30, at 9AM PDT / noon EDT. Tomorrow will be the last call before the 3.10 release, occurring Friday or

~ Gary O'Neall [2020-07-28 02:41 +0200]: Thank you! I've opened a Pull Request, but it only touches Annex E. I wondered whether we also have to clarify other snippet specifics

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

Hi Max, [G.O.] I personally would like to include this in the SPDX spec - we just need a volunteer to create an issue or (better yet) a pull request to update the Annex E Using SPDX license list

Hi all, At REUSE, we found some time to wrap our brains around this issue again. ~ Gary O'Neall [2020-06-05 19:58 +0200]: Thanks for the suggestions. I think what we need is a consensus on 1. how to

Hi everyone, This is a follow-up email on my previous email titled: Update on project: Validate license cross references Your contributions are welcome. Thanks, Smith

Hello all, The next regularly-scheduled SPDX legal team meeting will be this coming Thursday, July 16, at 9AM PDT / noon EDT. For the agenda we will focus on the (many!) open issues for 3.10: