(I know, I’m on a roll - last email from me today!) There is an SPDX room available co-located and after the event for the LF Member Summit in Lake Tahoe. The SPDX meeting will be Friday afternoon,

Hi all, As many of your are aware, we have discussed revising the license inclusion principles over the last part of 2019 - in various calls and distilled in this issue:

While I am biased, GitHub issues are pretty useful and some of these scenarios are pretty well handled with issues and it gives people one place to look for content. For example, we could create an

Hi folks, I made some updates to some of the documentation files in the Github repo today related to some conversation on the call. Would love to have some feedback. See:

Hello all, the next regularly-scheduled SPDX legal team meeting will be today, Thursday, Feb. 27 at 9AM PT / noon ET. = = = = = Join Zoom Meeting https://zoom.us/j/611416785 Meeting ID: 611 416

Hi Steve, I think the description of the event contains an error: 13:00 EST ought to be 18:00 in UTC, not 17:00. Sending this to the list in case anybody was going by what the description says

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

Hello all, the next SPDX legal team meeting will be today, Thursday, Feb. 13 at 9AM PT / noon ET. = = = = = Join Zoom Meeting https://zoom.us/j/611416785 Meeting ID: 611 416 785 One tap

Hello all, The version 3.8 release of the license list is now tagged and live at https://spdx.org/licenses. Along with the usual assortment of documentation updates and markup tweaks, 9 new licenses

The next SPDX legal team meeting will be today, Thursday, Jan. 30 at 9AM PT / noon ET. We'll focus on finalizing items to be included in the upcoming 3.8 release. Best, Steve = = = = = Join Zoom

Thanks Mark, I've created an issue to track this new request at: https://github.com/spdx/license-list-XML/issues/966 Steve -- Steve Winslow Director of Strategic Programs The Linux

1. Provide a proposed Full Name for the license or exception. selinux-nsa-declaration-1.0 2. Provide a proposed Short Identifier.

Hi Steve, I got called out of town for a family emergency and won't be able to make it today. Things are going ok. Sorry, Paul Sent from my Verizon, Samsung Galaxy smartphone

The next SPDX legal team meeting will be today, Thursday, Jan. 16 at 9AM PT / noon ET. Today we'll focus on following up on status for the pending 3.8 issues that were selected during the last call

If you care about open source compliance automation and if you are going to FOSDEM there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as "fringe" event,

Happy new year, all! The next SPDX legal team meeting will be today, Thursday, Jan. 2 at 9AM PT / noon ET. Since the 3.8 release was delayed due to the holidays and canceled team meetings, today's

You have been invited to the following event. SPDX legal team meeting When Every 2 weeks from 12pm to 1pm on Thursday from Thu Jan 2, 2020 to Thu Dec 31, 2020 Eastern Time - New

Hi all, Due to the end of the year craziness many of us are experiencing and resulting low-turnout at recent meetings and on the mailing list, we are going to call it for the year and reconvene (with

Hi Richard, I think both your possibilities work, and with the current state of art, I would agree with Kate, Jilayne and Gary. On the other hand it seems to me that exactly how to mark source

+1 on Kate’s recommendation. This format will be properly parsed by the SPDX Tools parsers (the 3 parsers I am aware of) and I believe represents the intent behind the AND operator. Gary