cut and pasting them here, instead of sending a link - maybe that will stir some energy around the last statement in particular… ;) Attendees[edit] John Horan Jilayne Lovejoy Mark Atwood Gary O’Neall

sorry, thought I had sent this last night! agenda: 1) GSoC update 2) 3.6 release (aka lots o’ licenses that still need to be reviewed… Jilayne

Hi all, We’ve been working on some updates and improvements to some of the SPDX License List documentation over the last couple meetings. Below is a bit of a summary of some of the updates and an ask

Andrew! I wanted to get your Solderpad licenses on the last SPDX License List release, but didn’t make it as I had a couple remaining questions and you didn’t respond when I tagged you on Github :) We

from today’s call here: https://wiki.spdx.org/view/Legal_Team/Minutes/2019-05-16 please note: we have MANY new license requests. We need review by the whole team (not just one or two of us…) to get de

Agenda: review new license requests - there are a lot of them. Please have a look, if possible, in the Github issues list. Web conference: http://uberconference.com/SPDXTeam Optional dial in number: 4

Hi all, We will have our regularly scheduled call. (see dial in info here: https://wiki.spdx.org/view/Legal_Team) I’d like to make a point to spend a bit of time discussing the topic below. Otherwise,

Hi all, Just a reminder that we have our bi-weekly call today at 10am MDT. I think Europe has now also set their clocks forward so we should all be back to our normal time differences. Being that we j

Hi all, Version 3.5 of the SPDX License List is now released. Most notably, we have added several open hardware licenses (CERN and TAPR), which I think is a really sensible and exciting addition, cons

just a quick note on this: the leftpad issue had some very specific and extenuating circumstances that led to the mess it created which are really not applicable here. So while the legal team will con

Hi all, I’m admittedly a bit late to this party despite having a few thoughts on the topic. This thread has quite a few aspects to it, starting with Jeff’s initial proposal, so I’ll try to hit all of

Hi all, Gary asked us to log issues for any improvements we might think of for the SPDX online tools - particularly related to the submit license and generate XML tools. I have just added some notes o

I just posted meeting minutes for today’s call (still need to add those from last meeting). https://wiki.spdx.org/view/Legal_Team/Minutes/2019-03-21 Please note: for merging the final PRs, let’s try t

Hi all, Meant to send this out last night, but as a last minute reminder, we have a meeting today at the top of the hour. Dial-in info: Web conference: http://uberconference.com/SPDXTeam Optional dial

Hi Philippe, I’m not going to re-hash what was a very lengthy and (surprisingly to me) heated discussion on the Linux kernel enforcement statement, since that is all in the email list archives. But as

Hi all, Towards the end of 2018, Richard Fontana submitted the GPL Cooperation Commitment for review to be added to the SPDX License List. We had some discussion about how that might work, but due to

and here is the link to that announcement that I forgot to include before: https://www.finos.org/blog/announcing-the-open-source-license-compliance-handbook ;) Jilayne

Hi SPDX folks (legal and general list), I want to tell you about a project I’ve been working on with Aaron Williamson and the Fintech Open Source Foundation (FINOS) that I think many of you may be int

Hi all, As discussed on a previous call, I’ve added a new doc describing the workflow for adding a new license. This aims to capture the steps for our team members who are shepherding a request throug

Hi Philippe, I’m a bit lost on what the goal of this is. Can you provide a bit more context. I looked at a couple entries and noticed, for example, this one: https://github.com/nexB/spdx-license-names