update: I finally found the Bison exception notice in a few files in the 2.2 download. I guess it only applies to some of the files? Someone who is more familiar with this and can provide a general ex

Welcome, Ansel! Cheers, Jilayne SPDX Legal Team co-lead opensource@...

Hello SPDX Tech and Legal teams, Please find attached some documentation for our call on Tuesday regarding fields in the SPDX specification, v2.0 that use either NONE, NOASSERTION or both. The goal of

Thanks for the feedback Dennis! Can I get a few more comments today - would be nice to have a forum to be comfortable adding/resolving these things for 2.1 Thanks!!! Jilayne SPDX Legal Team co-lead op

Hi All, Thanks for the great joint call today. As discussed, I’m attaching the same table as distributed yesterday, which will show any changes discussed on the call, some comments as to what was reso

Well, I’m going to call that a quorum. Libtool, Qwt, and Nokia-Qt exceptions will be on v2.1 of the SPDX License List. The questions/issues regarding some of the exceptions already on the list, will b

Late reminder for our call today!! Dial-in info here: http://wiki.spdx.org/view/Legal_Team Agenda: 1) status of v2.1 2) Fedora list activity re: SPDX 3) review exceptions on lines: 23-29 in the Google

HI Camille, We discussed this on the legal call today and would like to add this exception but discovered a glitch. The exception text does not indicate a version of LGPL, but includes the language: “

The minutes from last week’s legal call have been posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-07-09 Note, there is also now a share-able Google sheet with comparison info between th

SPDX legal team, In case you are not on the tech team mailing list, an issue has been raised via bugzilla and the tech team, that we will need to discuss. Please see the full thread here: https://bugs

Hi Bob, Thanks for asking! My additional comments to Kate’s also below: This should definitely be handled as a new exception added to the exception list; if you think this is something SPDX should hav

Thanks, Kris. Would Aug 6th work for you? Here is the info for the meeting: http://wiki.spdx.org/view/Legal_Team and for joining the Legal mailing list as well: http://spdx.org/participate/legal-team

Great Bob! Funny timing, as I was just looking at some FOSSology scans (haven’t done so in awhile, it’s like re-visiting an old friend :) and may have some other feedback for re: license matching. I’l

Sorry for the last minute reminder! Call this number: (United States): +1-857-216-2871 User PIN: 38633 International: visit the URL at http://uberconference.com/SPDXTeam Jilayne SPDX Legal Team co-lea

For the last two calls: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-07-23 http://wiki.spdx.org/view/Legal_Team/Minutes/2015-08-06 Thanks! Jilayne & Paul SPDX Legal Team co-leads

Hi Philippe, Comments below: There is already markup in about 15% of the licenses, as per our in depth discussions a couple years ago. The conversation on the call was about improving some of the exis

Hi Michael, Bob, Apologies for the delayed response here, this got a bit buried in the old Inbox. I had a look at the table in the link Michael provided. For ease of reference, I cut and pasted your t

Hi Bob, Here’s some feedback on license identification in FOSSology based a recent scan I was looking at. I think some of the things I saw originally would be taken care of by using the LicenseRef-<FO

Hi Bob, I’m copying the SPDX tech team on this, as I suspect they will be better suited to answer your question or address any issues here :) Thanks, Jilayne SPDX Legal Team co-lead opensource@jilayne

Hi All, We have the SPDX Legal call in about half an hour. Agenda: 1) update from LinuxCon Seattle (assuming people who were/are still there joint the call!) 2) standard headers that need markup - Mar