Jilayne Lovejoy invited you to “SPDX Legal Team bi-weekly call”.
when: Thursday, January 8, 2015, 11:00 AM - 12:00 PM
location: 1-415-363-0849
PIN: 336247
invitees: You
note: Call this number: (United States): +1-857-216-2871
User PIN: 38633
International: visit the URL at http://uberconfe
Hi all and Happy New Year!!
We will have our first call of 2015 this Thursday, same Bat-time, same
Bat-channel. That is, 11am Mtn Time / 1pm Eastern Time at the following
dial-in:
+1-857-216-2871
User PIN: 38633
I just sent out an invite for this week only. Will get a recurring invite out
Going back to the main question about whether it makes sense to break down
licenses to more basic licenses, is there a historical reason why we decided to
include a particular license as a distinct license? Is it just ease of use,
popularity, etc.? I could see that for an established project w
I would agree that for python, and generally for any large software codebase
that contains multiple licenses, trying to work out which specific code is
covered under which specific license is a very hard problem, unless the authors
have been diligent enough to keep them separate. However, I see
Hi,
In using the SPDX license list I have come across a number of entries that
actually appear to conjunctions of multiple licenses. In my view, these entires
represent a specific combination of licenses that happened to be present in a
specific software release. I’d like to put forward the arg
