<pombredanne@...> wrote: You really did help, thanks for the pointers and license disambiguation! I think with that in place there is no further need to fix (in project) or track (SPDX) them in

Hi Christian, Thanks for reaching to the SPDX project! As this has purely to do with licenses, it may be better addressed to the legal working group at spdx-legal@.... Alternatively,

Hi Christian: <christian.ehrhardt@...> wrote: I ran scancode-toolkit and the license in base64.c [1] is identified as an ISC alright. The only (IMHO not material) change is the

Hi SPDX, I was refreshing the license info on a Debian package and found two licenses that seemed to be MIT-variants that I wasn't sure about. The reason I looked at it was mostly technical as the

Whoops! https://wiki.spdx.org/view/General_Meeting/Minutes/2021-07-01 There were several attendees who’s organizations I don’t know. Please let me know and I will amend. Thanks. Phil

You should by this time have a new recurring meeting invite on your calendar with the Jitsi. PLEASE: When you sign in, please include your name and company (or put them in the chat) to facilitate

We've got a lot of historical cruft in our SPDX repo as well. Coming up with some criteria for inclusion & removal is overdue. After we settle the 3.0 template issue, you up for dedicating part of a

Hi Philippe, Thanks for your comments and thoughts on this. I know this was a couple of weeks ago, but I had a few thoughts I wanted to share. You're right that the Community Specification License is

Dear all, I bring good news: with the approval of the Libera.Chat staff, the #spdx IRC channel is now registered! This should be a great place to help introduce newcomers to the SPDX project, as well

Dear Phil: Thank you for these minutes! I want to comment on the spec license topic. <phil.odence=synopsys.com@...> wrote: The governance updates make change, but I cannot fathom the

We’ve had some new players joining. The minutes log names and companies. I didn’t get everyone’s company and there were a couple of phone numbers displayed; it wasn’t clear if those logged in

Please accept this recurring invitation “Dial In” info: Join the meeting: https://meet.jit.si/SPDXGeneralMeeting To join by phone instead, tap this: +1.512.647.1431,,1310118349# Looking

I will be sending out a replacement invite in a few hours. Please clear your calendar. Thanks, Phil

Because we are moving to Jitsi for video conferencing and try to avoid confusion, I will delete the old invite, wait a few hours and then send out a new one with the new information. To start the

I’m sure most of you are aware of the executive order by now. The draws attention to SPDX and the LF is keen to show the project in its best light. As such we are adding a page to the website to

Dear all, During today's SPDX Technical Team meeting, the US Government's recent Executive Order was a major point of discussion! Kate Stewart shared a link to a blog post from the Linux Foundation

You’re very welcome. Thanks for all you do! :-) We LOVE that place! Can’t wait to start going again! So yes, may see us there! From: <spdx@...> on behalf of Steve Winslow

For those interested -- as a follow-up to Kate's message about the EO, here is an article in ZDNet that mentions several aspects of SPDX and how it addresses objectives of the

Last night Biden signed Executive Order (EO) on Improving the Nation’s Cybersecurity. As part of this Executive order the concept of SBOM is getting widespread visibility. If the question comes up