(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, th

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: https://github.com/spdx/licens

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: https://github.com/spdx/licen

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

Agree. And also agree with Richard’s comment about avoiding legal interpretations. When you say that the license is “X AND Y” you are saying both licenses apply. Which is the fact for this file. You a

Hi all, Due to some unforeseen circumstances, both Steve and I are not available tomorrow. Given this would be our last meeting for 2019 (unless people wanted to meet on Dec 26th?), I'd like to postpo

Thanks Mike - responses below! Yes, I think this is how it has been set up in the PR - as it’s own Appendix and .md file, so one can refer to it separately there. I suppose we could change links to po

Hi SPDX legal and tech teams, Some time ago, we decided to move the Matching Guidelines to an Appendix in the SPDX specification, instead of only having them live on a webpage (here: https://spdx.org/

better late, than never... I really wouldn’t conflate attribution and copyright notices - that seems to lead to a lot of unnecessarily confusion and other energy FWIW - this reminded me that there are

Good catch Steve! I should have looked there first before replying. (carry on as usual, all, don’t mind me!)

Hi Bastien, The process for requesting a new license be added to the SPDX License List is documented here: https://github.com/spdx/license-list-XML/blob/master/CONTRIBUTING.md (and happy to get your f

Hi all, A few months ago we began a project to update the license inclusion principles (as well as some other documentation updates in terms of both substance and location). Specifically, currently th

Hi all, As Steve and I are at Open Source Summit (as are others), we’ll skip this week’s meeting. Please check and comment on open Github issues! Jilayne Sent from my phone, please excuse brevity and

Hi Steve, I thought we were going to maybe have a demo by the GSoC student who is working on the license submission tool improvements. Is that not going to happen for this call? Thanks, Jilayne

Hi all, Please find the meeting minutes here: https://wiki.spdx.org/view/Legal_Team/Minutes/2019-07-11 We had a very fruitful discussion about the SPDX-FileCopyrightText proposal, which is mostly docu

Hi Tanjong, Thanks for sending this to the SPDX legal team and sorry for the delayed response. This looks good, but I have one main concern: how will people know when to submit a license to the namesp

Hi Yegor, We have Matching Guidelines to explain when a license may be a match or not, see: https://spdx.org/spdx-license-list/matching-guidelines ISC License has markup to accommodate different names

Thanks Mike!

Hello SPDX legal team members, I wanted to inform you of some updates to the SPDX legal team membership. For some years now, Paul Madick, Karen Copenhaver and I have shared the SPDX legal team leaders

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