Spdx-legal@lists.spdx.org

Home Messages Hashtags Subgroups

Messages

Between

and

The idea is that each license has a name. Then some licenses might have synonyms. The old GPLv2 WITH Bison Exception is now known as the GPL-2 WITH Bison Exception. The old name was

By dmg <dmg@...> · #1026 ·

we are on the 857-216-2871 number

invite had two dial-in numbers: PIN 38633 sorry!! Jilayne SPDX Legal Team co-lead opensource@...

By J Lovejoy · #1025 ·

Re: Call this Thursday!!

"... but links to those deprecated licenses have been removed from the SPDX License List in order to clarify the currently recommended syntax ..." The links are still there.

By Dennis Clark · #1024 ·

Re: Call this Thursday!!

For today’s call, please check out the release candidate for the SPDX License List v2.0, which can be found here: http://spdx.org/licenses/preview/ Thanks, Jilayne SPDX Legal Team

By J Lovejoy · #1023 ·

Re: Call this Thursday!!

Hi All, It appears that the invite I sent may not have rendered the time of the meeting correctly across time zones. The Legal Team meeting is at 10am Pacific / 11am Mountain / 1pm Eastern There

By J Lovejoy · #1022 ·

Call this Thursday!!

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

By J Lovejoy · #1020 ·

Jilayne Lovejoy invited you to “SPDX Legal Team bi-weekly call”.

By Jilayne Lovejoy <noreply@...> · #1021 ·

Re: Entries on the SPDX license list that are conjunctions of multiple licenses.

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

By Alan Tse · #1019 ·

Re: Entries on the SPDX license list that are conjunctions of multiple licenses.

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

By Sam Ellis · #1018 ·

Re: Entries on the SPDX license list that are conjunctions of multiple licenses.

Hi Sam, I can speak to Python. The relationships among various pieces of code and the licenses are quite complex. I have attached a map of the relationships. Although it may be technically

By Tom Incorvia · #1017 ·

Entries on the SPDX license list that are conjunctions of multiple licenses.

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

By Sam Ellis · #1016 ·

New LIcense Request: W3C Software Notice and License (19980720)

Hi, I would like to prose the addition of the W3C Software Notice and License (19980720) to the SPDX license list. The license list already contains a newer version of this license dated 20021231

By Sam Ellis · #1015 ·

New License Request: W3C Documentation License

Hi, I would like to propose the addition of the W3C Documentation License to the SPDX license list. There are (at least) two different versions with subtly different legal terms, so ideally both

By Sam Ellis · #1014 ·

Re: call today!

Hi David, Thank you for the feedback. You highlighted an important point. Outer parentheses was a requirement added by the tech team to support tool parsing but it is not required for human

By Mark Gisi · #1013 ·

minutes posted for today's call

here: http://wiki.spdx.org/view/Legal_Team/Minutes/2014-12-11 Thanks! SPDX Legal Team co-lead opensource@...

By J Lovejoy · #1012 ·

Re: call today!

I'm unavailable today. In client meetings in Scottsdale. Have a good meeting. * * * * * * * * * * * * Thomas H. Vidal, Esq. Abrams Garfinkel Margolis Bergson, LLP 5900 Wilshire Boulevard, Suite

By Tom Vidal <TVidal@...> · #1011 ·

Re: call today!

I’m glad to see the new expression syntax, including “+”, “with”, “and”, “or”, and “;”. Big improvement. However, I suggest NOT requiring that expressions be surrounded with

By David A. Wheeler · #1010 ·

call today!

Please note this is the correct dial-in info: Call this number: (United States): +1-857-216-2871 User PIN: 38633 International: visit the URL at http://uberconference.com/SPDXTeam Agenda items as

By J Lovejoy · #1009 ·

Updates to Licenses Under Consideration web page

Hi Legal Team, http://wiki.spdx.org/view/Legal_Team/License_List/Licenses_Under_Consideration has been updated to point the reader to our google spreadsheet that now tracks both license and license

By Dennis Clark · #1008 ·

Re: Please Consider BSD-JCharts Variant for Inclusion in SPDX List

My approach is to take a memorable phrase from the proposed license and use Linux / Mac 'grep' tool to find which existing SPDX licenses this phase occurs it. I run this over my local check-out of the

By Sam Ellis · #1007 ·

2381 - 2400 of 3406

Home Hashtags Subgroups Terms