|
[Update] SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT
All:
A few items for today's SPDX Legal Workstream Meeting:
(A) For those not in the US, I provided International dial in numbers below.
(B) For those in Boston for the Project Harmony meeting,
All:
A few items for today's SPDX Legal Workstream Meeting:
(A) For those not in the US, I provided International dial in numbers below.
(B) For those in Boston for the Project Harmony meeting,
|
By
mgia3940@motorola.com <mgia3940@...>
·
#221
·
|
|
Re: Python History and License
For Today’s Legal Stream Call (attached). Tom
Tom Incorvia
tom.incorvia@...
Direct: (512) 340-1336
Mobile: (408) 499 6850
For Today’s Legal Stream Call (attached). Tom
Tom Incorvia
tom.incorvia@...
Direct: (512) 340-1336
Mobile: (408) 499 6850
|
By
Tom Incorvia
·
#222
·
|
|
[Update] SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT
http://www.spdx.org/wiki/license-list
http://www.spdx.org/wiki/license-list
|
By
mgia3940@motorola.com <mgia3940@...>
·
#223
·
|
|
Agenda for Dec 16 SPDX General Meeting
The SPDX General Meeting is for sharing and cross functional coordination between the Technical, Business and Legal Teams. General Meetings are currently scheduled for 60 minutes, but may only require
The SPDX General Meeting is for sharing and cross functional coordination between the Technical, Business and Legal Teams. General Meetings are currently scheduled for 60 minutes, but may only require
|
By
Philip Odence
·
#224
·
|
|
Minutes from Dec 16 General Meeting
Minutes are posted: http://www.spdx.org/wiki/20101216-general-meeting-minutes
The GM minutes provide a good bi-weekly summary of everything SPDX.
If you have interest in more closely monitoring or
Minutes are posted: http://www.spdx.org/wiki/20101216-general-meeting-minutes
The GM minutes provide a good bi-weekly summary of everything SPDX.
If you have interest in more closely monitoring or
|
By
Philip Odence
·
#225
·
|
|
Issue tracker
We now have a issue tracker for the SPDX specification and related
tools. Please report any issues you are aware of with the spec or
tools at
We now have a issue tracker for the SPDX specification and related
tools. Please report any issues you are aware of with the spec or
tools at
|
By
Peter Williams <peter.williams@...>
·
#226
·
|
|
zlib and libpng licenses clarification
I hada question regarding clarifying the zlib and libpng licenses versus what theOSI lists as the zlib/libpng license on their list. Perhaps Tom, Martin,or Jeff can shed some light on this?
I hada question regarding clarifying the zlib and libpng licenses versus what theOSI lists as the zlib/libpng license on their list. Perhaps Tom, Martin,or Jeff can shed some light on this?
|
By
Jilayne Lovejoy <Jlovejoy@...>
·
#227
·
|
|
Re: zlib and libpng licenses clarification
Fedora treats these two licenses as functionally identical, and calls
them both "zlib".
The third license looks to just be a templated version of the zlib license.
~tom
==
Fedora Project
Fedora treats these two licenses as functionally identical, and calls
them both "zlib".
The third license looks to just be a templated version of the zlib license.
~tom
==
Fedora Project
|
By
Tom "spot" Callaway
·
#228
·
|
|
Re: zlib and libpng licenses clarification
So, do you think we should only list the OSI template version, using
their name, "zlib/libpng license" and not include the two
package-specific licenses on our initial list?
Jilayne
So, do you think we should only list the OSI template version, using
their name, "zlib/libpng license" and not include the two
package-specific licenses on our initial list?
Jilayne
|
By
Jilayne Lovejoy <Jlovejoy@...>
·
#229
·
|
|
Re: zlib and libpng licenses clarification
Yes, but I think the general trend for the SPDX initiative has been that
any difference in wording (with the possible exception of copyright
holder identifiers), even if it has no effect on the rights
Yes, but I think the general trend for the SPDX initiative has been that
any difference in wording (with the possible exception of copyright
holder identifiers), even if it has no effect on the rights
|
By
Tom "spot" Callaway
·
#230
·
|
|
Re: zlib and libpng licenses clarification
This is related to my question in the last legal team conference call:
How to deal with the billions of 'BSD-style'-licenses, the only
difference of which is the Copyright notice?
The answer was to
This is related to my question in the last legal team conference call:
How to deal with the billions of 'BSD-style'-licenses, the only
difference of which is the Copyright notice?
The answer was to
|
By
Soeren_Rabenstein@...
·
#231
·
|
|
Re: zlib and libpng licenses clarification
Sure, but in the case of libpng's license, the difference is more
significant than Copyright holder identifiers. It doesn't fundamentally
change the license's meaning, but it is technically different
Sure, but in the case of libpng's license, the difference is more
significant than Copyright holder identifiers. It doesn't fundamentally
change the license's meaning, but it is technically different
|
By
Tom "spot" Callaway
·
#232
·
|
|
Re: zlib and libpng licenses clarification
Instead of all three variations, we could just have the OSI one, which
is basically the zlib license template (no specific copyright) and then
the specific libpng license, since it does have some
Instead of all three variations, we could just have the OSI one, which
is basically the zlib license template (no specific copyright) and then
the specific libpng license, since it does have some
|
By
Jilayne Lovejoy <Jlovejoy@...>
·
#233
·
|
|
My screw up on SPDX biz call this AM
I told everyone we were planning to have it, and then forgot myself. Holiday brain I guess.
We’ll reconvene post-holidays.
Kim
On Thu 12/23/10 9:09 AM, "Philip Odence" <podence@...> wrote:
Kim
I told everyone we were planning to have it, and then forgot myself. Holiday brain I guess.
We’ll reconvene post-holidays.
Kim
On Thu 12/23/10 9:09 AM, "Philip Odence" <podence@...> wrote:
Kim
|
By
Kim Weins
·
#234
·
|
|
Re: zlib and libpng licenses clarification
For SPDX, I suppose it makes sense to take the templated zlib and call
it "zlib", and call the libpng variant "libpng", even though I don't
think Fedora will ever make that
For SPDX, I suppose it makes sense to take the templated zlib and call
it "zlib", and call the libpng variant "libpng", even though I don't
think Fedora will ever make that
|
By
Tom "spot" Callaway
·
#235
·
|
|
License List 1.4 posted on SPDX site
http://www.spdx.org/wiki/working-version-license-list
Itemsof note:
Olderversions of various licenses have been added.
Zlib andlibpng licenses are both included.
Onlyremaining issue that I
http://www.spdx.org/wiki/working-version-license-list
Itemsof note:
Olderversions of various licenses have been added.
Zlib andlibpng licenses are both included.
Onlyremaining issue that I
|
By
Jilayne Lovejoy <Jlovejoy@...>
·
#236
·
|
|
Re: License List 1.4 posted on SPDX site
Hi Jilayne,
Thanks for getting the next rev of the license list out!
Regarding the BSD licenses: I did some of the original work on the BSD licenses. Below is the post from June 2010. Fine
Hi Jilayne,
Thanks for getting the next rev of the license list out!
Regarding the BSD licenses: I did some of the original work on the BSD licenses. Below is the post from June 2010. Fine
|
By
Tom Incorvia
·
#237
·
|
|
trying it out for size
Hello SPDX,
I have been lurking in the background for a while now; I maintain
man(1) and I keep a DOAP file on the project site, I thought I would
take a crack at SPDX:
Hello SPDX,
I have been lurking in the background for a while now; I maintain
man(1) and I keep a DOAP file on the project site, I thought I would
take a crack at SPDX:
|
By
Federico Lucifredi
·
#238
·
|
|
Reminder: SPDX Business (Rollout) Call in 15 minutes
------ Original Appointment
From: kim.weins@...
When: 9:00 AM - 10:00 AM December 9, 2010
Subject: SPDX Business (Rollout) Call 11ET/8PT
Location: See dial in below
US 866-740-1260
Int'l
------ Original Appointment
From: kim.weins@...
When: 9:00 AM - 10:00 AM December 9, 2010
Subject: SPDX Business (Rollout) Call 11ET/8PT
Location: See dial in below
US 866-740-1260
Int'l
|
By
Kim Weins
·
#239
·
|
|
Next SPDX General Meeting
To avoid any confusion, I wanted to make clear that the next SPDX General Meeting is next Thursday, January 13. There would have been a meeting last week, but we cancelled it due to the holidays; Jan
To avoid any confusion, I wanted to make clear that the next SPDX General Meeting is next Thursday, January 13. There would have been a meeting last week, but we cancelled it due to the holidays; Jan
|
By
Philip Odence
·
#240
·
|