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

Jilayne, SPDX Legal Team, Sorry, but I will not be able to join the joint Tech / Legal team call on June 16th. I hope and assume that enough legal group people can attend. Regards, Dennis

Many thanks for your generous reply, and for sending so quickly. Forgive me if I'm behind on general discussions about the purpose and function of SPDX expressions. I understood their purpose rather

BSD 0-clause "Public Domain Equivalent" License. BSD-0-Clause http://landley.net/toybox/license.html Copyright 2015 by Your Name Here <your@...> Permission to use, copy, modify, and/or

I will take the opportunity to offer an opinion to the forums on this question that is raised above: I think first and foremost this is a question around interpretation of the licenses. Only when you

Hi Jilayne, >> Someone who is more familiar with this and can provide a general explanation would be much appreciated Bison is a parser generator tool. Someone creates as input a grammar, and the

So glad to see this message! Ansel is a friend, colleague, and kindred spirit. Our conversations on law and software rank reliably among the most challenging and rewarding of my career. I am also an

Hello! After being introduced to SPDX by Kyle Mitchell, I've been browsing the Legal Team list archives and learning about SPDX generally. I hope to get more involved with the Legal Team starting in

Jilayne, Legal Team, My thoughts regarding these issues: Libtool exception -- I think the text we provide should be the exception text only, especially considering that the full notice text might

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

The meetings have been posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-06-11 We did not get through all of the questions on exceptions. Some of the outstanding questions may be

The two previous UK versions: http://www.nationalarchives.gov.uk/doc/open-government-licence/version/1/ http://www.nationalarchives.gov.uk/doc/open-government-licence/version/2/ Canada federal

Hi Legal Team, The two new license requests (CECILL-2.1 and OGL-3.0) have been added to our tracking spreadsheet. Rows 9 and 10. Regards, Dennis Clark nexB Inc.

Reminder that we have a legal team call tomorrow and have lots to cover in preparation for the v2.1 release of the SPDX License List at the end of the month! As such, we will stick strictly to the

HI Mike, Thanks for the info. Regarding the other versions of OGL, could you provide links to those? As for non-software licenses and the project mentioned below, could I ask you to join an SPDX Legal

Dear Mark, In message <01813E194C768044A6486DB30B5338CCC312E490@...> you wrote: This is the exact question I'm trying to get an official position for. From the technical point of

As a general rule of thumb, one should *not* modify the licensing terms of another copyright holder. Adding an SPDX Identifier to an existing file is one thing. Removing (or modifying) license

Roger - Thanks for bring attention to these additional efforts. As a more general comment: There are at least five different stakeholders who need to be taken into consideration when determining

Hi Henri, While Mark is right that there is no official recommendation by the SPDX working group, there does seem to be a bit of momentum forming around the use of: SPDX-License-Identifier:

Hi all This might be of interest: https://issues.apache.org/jira/browse/LEGAL-114 and here is another project using