Date   

SPDX General Meeting link

Philip Odence
 

Note: I realize that the link I sent our for the webshare has an older date embedded in it. Please ignore and use it anyway.
Thanks, Phil


L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502


Purpose of licensing info

Peter Williams <peter.williams@...>
 

There has been a bit of discussion in the technical working group
about the role of judgments in spdx. It has been suggested that
information that is the result of human, or automated heuristic,
judgment should disallowed/discouraged in spdx files.

This has lead me to wonder a about the primary purpose of the
licensing parts of spdx. Do we intended for spdx files to convey the
actual licenses under which a package is copyable? Or should spdx
files convey the just licenses under which a package is explicitly
stated/declared to be copyable?

The actual licensing of a package is often not fully and explicitly
stated. (Files don't have header, code snippets are copied, etc.)
Therefore if spdx conveys the actual licensing of a package this will
require representing human/heuristic judgments.

Conveying the actual licensing will also mean that two spdx files for
the same package might disagree regarding the licensing. This could
happen because one was generated by a person or tool that discovered
more facts. (For example, a tool might detect that some of the code
in a file appears to originate from some other project while a human
on their own might not.) Or it could result from different judgments
being made from the same information.

If we limit spdx to conveying only the stated/declared licensing we
would avoid inharmonious spdx files. This would be achieved by
precluding judgments (or limiting the types of allowed judgments to a
very small set). However, consumers would not be able to treat spdx
files as an authoritative guide to the licensing of the package. The
set of declared/explicitly stated licenses would often be incomplete
and sometimes it would be erroneous.

The beta spec states that "information that cannot be derived from an
inspection (whether manual or using automated tools) of the package to
be analyzed" is "not covered in the specification". This would seem
to imply that judgments about what licenses a package was copyable
under would be allowed if those judgments where based in discoverable
facts. However, i am not sure it is entirely cut and dry.

I think some this issue bares some discussion in the larger group.
Are technical judgments regarding the licensing of the files and
packages acceptable and/or desirable in spdx files?

Peter
openlogic.com


Agenda for Thursday's SPDX General Meeting

Philip Odence
 

Meeting Time: Dec 2, 8am PDT / 10 am CDT / 11am EDT / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

Web:
Note, we will be using a different URL for each meeting for purposes of taking attendance. When you login PLEASE INCLUDE YOUR FULL NAME IN THIS FORM: Phil Odence, Black Duck Software so I can just copy/paste into minutes. THXhttp://blackducksoftware.na6.acrobat.com/spdx2dec10
 
Administrative Agenda
Attendance

Technical Team Report - Kate

Business Team Report - Kim/JohnE
Beta program status

Legal Team Report - Rockett/Karen

Cross Functional Issues - Phil


Action Items

Most of the action items belong with the Teams. So, in addition to statusing, we will dispatch them to the respective teams and will not continue to track in this meeting. Action items for this meeting will be cross functional.

• Kate/Kim- Draft example for LF Member Counsel; include XML and spreadsheet. PENDING
• MichaelH/Rockett- Write up and share postion on "reporting" vs. "interpreting. PENDING
• Rockett- Post regular meeting times on Legal Team page. PENDING
• MartinM- Report back on # of people on respective mailing lists. DONE, BUT LET'S KEEP UPDATING

L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502


Updated Invitation: SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT @ Wed Jan 12 8am - 9am (spdx@fossbazaar.org)

Esteban Rockett <mgia3940@...>
 

This event has been changed.

SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT

Changed: All:

- Please note, proposed minutes from our last meeting are posted on the SPDX Wiki under the Legal Workstream section. Sorry for the delay. We will allow an additional week for approval of these minutes.

- Adding (1) Agenda for today's 2-Jan-2011 meeting, (2) International Dial-in Numbers, and (3) Proposed Minutes from Last Meeting:


(1) -- 12-Jan-2011 -- Proposed Agenda

(A) Last Meeting Minutes Posted; Additional Week to Review

(B) Update on "Create Process/Method to Add Licenses"

(C) Update on SPDX Metadata License Discussion with Bradley and SPDX Core Team

(D) Continue/Conclude Discussion on Use of SPDX Standard License Acronyms

(E) Issue raised from Tech Workstream on the need for a Legal Policy on "SPDX Not Validating License Recited"

(F) Any New Topics


(2) -- International Dial-in Numbers --

Conference PIN: 0376146

Country

Toll free number

AUSTRALIA

1800003691

AUSTRIA

0800292117

BELGIUM

080077968

CANADA

8772832663

CHINA Netcom (CNC)*

10 800 712 3245
10 800 714 0551

CHINA Telecom (CT)*

10 800 120 3245

DENMARK

80703158

FINLAND

0800770232

FRANCE

0800941694

GERMANY

08001014510

GREECE

0080016122038641

HONG KONG

800967971

HUNGARY

0680015286

INDIA (Bharti) **

000 800 001 2005

INDIA (Reliance)

000195

INDIA (VSNL)

0008001005009

INDIA (ALL OTHER CARRIERS) **

000 800 100 6006

INDONESIA

008800105490 (mobile excluded)

INDONESIA Alternate

0018030113665 (mobile excluded)

IRELAND

1800944115

ISRAEL

1809458641

ITALY

800781687

JAPAN

00531160347

LUXEMBOURG

80023984

MALAYSIA

1 800 802 411

MONACO

80093182

NETHERLANDS

08002658218

NEW ZEALAND

0800447808

NORWAY

80057408

PHILIPPINES

180011100676

POLAND

008001114561

PORTUGAL

800819894

RUSSIA

81080022521012

SINGAPORE

800 120 0250

SOUTH AFRICA

0800990934

SOUTH KOREA

00308140426

SPAIN

900971504

SWEDEN

0201400558

SWITZERLAND

0800563963

TAIWAN, THE REPUBLIC OF CHINA

00801126569

THAILAND

0018001562038641

UNITED KINGDOM

08006920816

UNITED STATES

8772832663


***
Happy New Year to all.

This calendar appointment is for our regular bi-weekly SPDX Legal Workstream call.

Many thanks,

Rockett

Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...

When
Wed Jan 12 8am – 9am Pacific Time
Where
Conference Bridge 1.877.825.8522 PIN:0376146 (map)
Calendar
spdx@...
Who
Esteban Rockett - organizer
amanda.brock@...
tony.gomes@...
sadams@...
feb.cabrasawan@...
jmcbroom@...
rfontana@...
linda.shih@...
Alexandra.Siegel@...
mpierovi@...
kathleen.mullins@...
JOHN ELLIS
rtiller@...
alastern@...
Mikko.Amper@...
adcohn@...
paul.madick@...
ilardi@...
areid@...
owen.james.boyle@...
smortin@...
Mansour Ghomeshi
scott.k.peterson@...
Guy.Colpitts@...
bgieseman@...
pmcbride@...
spaek@...
tcarlson@...
andrew.wilson@...
barbara.reilly@...
jwacha@...
bkahin@...
andrew.updegrove@...
mrc@...
mccoy.smith@...
ssemel@...
gsjones@...
kcopenhaver@...
spdx-legal-request@...
spdx@...

Going?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account spdx@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Updated Invitation: SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT @ Every 2 weeks from 8am to 9am on Wednesday from Wed Jan 12 to Wed Dec 14 (spdx@fossbazaar.org)

Esteban Rockett <mgia3940@...>
 

This event has been changed.

Changed: SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT

Happy New Year to all.

This calendar appointment is for our regular bi-weekly SPDX Legal Workstream call.

Many thanks,

Rockett

Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...

When
Every 2 weeks from 8am to 9am on Wednesday from Wed Jan 12 to Wed Dec 14 Pacific Time
Where
Conference Bridge 1.877.825.8522 PIN:0376146 (map)
Calendar
spdx@...
Who
Esteban Rockett - organizer
amanda.brock@...
sadams@...
tony.gomes@...
feb.cabrasawan@...
rfontana@...
jmcbroom@...
Alexandra.Siegel@...
linda.shih@...
mpierovi@...
kathleen.mullins@...
rtiller@...
JOHN ELLIS
alastern@...
Mikko.Amper@...
adcohn@...
paul.madick@...
ilardi@...
areid@...
owen.james.boyle@...
smortin@...
Mansour Ghomeshi
scott.k.peterson@...
Guy.Colpitts@...
bgieseman@...
pmcbride@...
tcarlson@...
spaek@...
andrew.wilson@...
barbara.reilly@...
jwacha@...
bkahin@...
mrc@...
andrew.updegrove@...
mccoy.smith@...
ssemel@...
gsjones@...
kcopenhaver@...
spdx@...
spdx-legal-request@...

Going?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account spdx@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Invitation: SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT @ Every 2 weeks from 8am to 9am on Wednesday from Wed Jan 12 to Wed Dec 14 (spdx@fossbazaar.org)

Esteban Rockett <mgia3940@...>
 

SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT

Happy New Year to all.

This calendar appointment is for our regular bi-weekly SPDX Legal Workstream call.

Many thanks,

Rockett

Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...

When
Every 2 weeks from 8am to 9am on Wednesday from Wed Jan 12 to Wed Dec 14 Pacific Time
Where
Conference Bridge 1.877.825.8522 PIN:0376146 (map)
Calendar
spdx@...
Who
Esteban Rockett - organizer
amanda.brock@...
sadams@...
tony.gomes@...
feb.cabrasawan@...
rfontana@...
jmcbroom@...
Alexandra.Siegel@...
linda.shih@...
mpierovi@...
kathleen.mullins@...
rtiller@...
JOHN ELLIS
alastern@...
Mikko.Amper@...
adcohn@...
paul.madick@...
ilardi@...
areid@...
owen.james.boyle@...
smortin@...
Mansour Ghomeshi
scott.k.peterson@...
Guy.Colpitts@...
bgieseman@...
pmcbride@...
tcarlson@...
spaek@...
andrew.wilson@...
barbara.reilly@...
jwacha@...
bkahin@...
mrc@...
andrew.updegrove@...
mccoy.smith@...
ssemel@...
gsjones@...
kcopenhaver@...
spdx@...
spdx-legal-request@...

Going?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account spdx@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Re: SPDX Web Site Linkes Appear to be broken

Martin Michlmayr
 

This was caused by a Drupal upgrade I did earlier today. The issue
has not been fixed yet (<http://drupal.org/node/1019788>) so I
downgraded to the previous version.

* Tom Incorvia <tom.incorvia@...> [2011-01-09 16:07]:

Hi SPDX Team,

Most of the links on the SPDSX site are not working – I was trying to get to the license list.


Tom

[cid:image001.jpg@...]

Tom Incorvia
tom.incorvia@...<mailto:tom.incorvia@...>
Direct: (512) 340-1336
Mobile: (408) 499 6850



This message has been scanned for viruses by MailController<http://www.MailController.altohiway.com/>.


_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard


SPDX Web Site Linkes Appear to be broken

Tom Incorvia
 

Hi SPDX Team,

 

Most of the links on the SPDSX site are not working – I was trying to get to the license list. 

 

 

Tom

 

 

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850



This message has been scanned for viruses by MailController.


Minutes from Business Call

Kim Weins
 

Hi All

Minutes are now available.

http://www.spdx.org/wiki/business-team-meeting-agendaminutes-20110106

We spent most of the call talking about the Beta program.  We are targeting Feb 3rd to have an introductory call with all of the potential beta sites (5 to date) to go over details of the program, what we are asking them to do, what we will be providing them, etc.

Our next business team call is in 2 weeks — Jan 20th

Kim


Next SPDX General Meeting

Philip Odence
 

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 13 follows that date by two weeks.

I'll send out a reminder, agenda and dial-in info a few days before.

Best,
Phil


L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502


Reminder: SPDX Business (Rollout) Call in 15 minutes

Kim Weins
 

------ 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 http://www.readytalk.com/support/international-numbers.php

ID 2404502

Web Meeting
Www.readytalk.com
ID 2404502

Agenda
We will be covering several areas on the rollout plan.

1. Beta process
2. User Content - what is needed
3. Evangelism and outreachOccurs every 2 week(s) on Thursday effective Thu
12/9/10

------ End Of Original Appointment


trying it out for size

Federico Lucifredi
 

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:

http://primates.ximian.com/~flucifredi/man/SPDX.rdf

I first drafted this in the fall, so the spec may have drifted from
there, but I would be interested in critique/comments. Let's have it.

Best -F
--
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish
(Federico L. Lucifredi) - flucifredi@... - GnuPG 0x4A73884C


Re: License List 1.4 posted on SPDX site

Tom Incorvia
 

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 if we rethink, but FYI below is the logic that the “early” team used to come up with the long names. 

 

The key issue that we tried to address was that the BSD licenses are inconsistently referred to with adjectives including “Original”, “New”, “Old”, “Modified”, “Simplified” and “Free”. 

 

These adjectives are also often combined inconsistently or outright incorrectly causing additional confusion.  We agreed on the # clauses as being definitive for the short names.  The current long names that were chosen were a compromise to have the names be as distinct as possible while retaining as much of the naming “lineage” as possible.

 

The June emails on this topic is below.

 

Tom

===============================

From: Tom Incorvia
Sent: Thursday, June 17, 2010 9:40 AM
To: package-facts@...
Subject: BSD Short and Long Name Recommendations

 

One of my tasks from the last call was to propose BSD license long and short names.

 

Here are the names and logic.  These have been integrated into Kate’s list.

 

BSD License Naming:

 

Lots of confusion has resulted from the BSD licenses being named with various adjectives including Original, New, Old, Modified, Simplified and Free.  These adjectives are also combined, often, and incorrectly, causing additional confusion. 

 

Suffixing with the number of clauses ,however, is quite consistent, so I propose that we do that for the short names as specified below. 

 

-          BSD-4-Clause

-          BSD-3-Clause

-          BSD-2-Clause

 

Regarding the long names, to limit the confusion we include accepted, non-overlapping adjectives for each.  The long names below reflect the most consistent use of the adjectives historically used to describe the BSD.  The only exception is that “New and Simplified” is NOT used in the long name.  This combination, although somewhat common, consistently obscures whether the license is the “New” (3-clause) or  “Simplified FreeBSD” (2-Clause).  Best to avoid this phrase.

 

Proposed long names are below:

 

-          BSD 4-Clause “Original” or “Old” License

-          BSD 3-Clause “New” or  “Revised” License

-          BSD 2-Clause “Simplified” or “FreeBSD” License

 

Tom

 

===============================

 

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850

From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Jilayne Lovejoy
Sent: Thursday, December 23, 2010 5:23 PM
To: spdx@...
Subject: License List 1.4 posted on SPDX site

 

http://www.spdx.org/wiki/working-version-license-list

 

Items of note:

Older versions of various licenses have been added.

Zlib and libpng licenses are both included.

 

Only remaining issue that I don’t think we addressed was the naming of the BSD licenses.  Currently the long title includes the various common names, e.g. “BSD 3-clause "New" or "Revised" License”

This is certainly makes it most identifiable and I didn’t have any better idea of how to handle the various ways these licenses are referred to, so I left as-is.

 

Happy Holidays!

 

Jilayne Lovejoy  |  Corporate Counsel

jlovejoy@...

 

720 240 4545  |  phone

720 240 4556  |  fax

1 888 OpenLogic  |  toll free

www.openlogic.com

 

OpenLogic, Inc.

Headquarters, Broomfield, Colorado 80021

 

 

Click here to report this email as spam.

This message has been scanned for viruses by MailController.


License List 1.4 posted on SPDX site

Jilayne Lovejoy <Jlovejoy@...>
 

http://www.spdx.org/wiki/working-version-license-list

 

Items of note:

Older versions of various licenses have been added.

Zlib and libpng licenses are both included.

 

Only remaining issue that I don’t think we addressed was the naming of the BSD licenses.  Currently the long title includes the various common names, e.g. “BSD 3-clause "New" or "Revised" License”

This is certainly makes it most identifiable and I didn’t have any better idea of how to handle the various ways these licenses are referred to, so I left as-is.

 

Happy Holidays!

 

Jilayne Lovejoy  |  Corporate Counsel

jlovejoy@...

 

720 240 4545  |  phone

720 240 4556  |  fax

1 888 OpenLogic  |  toll free

www.openlogic.com

 

OpenLogic, Inc.

Headquarters, Broomfield, Colorado 80021

 


Re: zlib and libpng licenses clarification

Tom "spot" Callaway
 

On 12/22/2010 07:37 PM, Jilayne Lovejoy wrote:
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 other text
differences. In which case, we might simply call it the "zlib" license
instead of the OSI's "zlib/libpng" license, which is a bit confusing.

Thoughts?
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 distinction.

~tom

==
Fedora Project


My screw up on SPDX biz call this AM

Kim Weins
 


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:





L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502
podence@...
http://www.blackducksoftware.com
http://twitter.com/podence
http://www.linkedin.com/in/podence
http://www.networkworld.com/community/odence (my blog)




Kim Weins | Senior Vice President, Marketing
kim.weins@...
Follow me on Twitter @KimAtOpenLogic

650 279 0410 | cell
www.openlogic.com
Follow OpenLogic on Twitter @OpenLogic

OpenLogic, Inc.
Headquarters, Broomfield, Colorado





Re: zlib and libpng licenses clarification

Jilayne Lovejoy <Jlovejoy@...>
 

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 other text
differences. In which case, we might simply call it the "zlib" license
instead of the OSI's "zlib/libpng" license, which is a bit confusing.

Thoughts?

I'd like to get the latest version of the license list uploaded
tomorrow, if possible, pending this issue :)

Jilayne

-----Original Message-----
From: Tom Callaway [mailto:tcallawa@...]
Sent: Tuesday, December 21, 2010 8:27 PM
To: Soeren_Rabenstein@...
Cc: Jilayne Lovejoy; spdx@...
Subject: Re: zlib and libpng licenses clarification

On 12/21/2010 09:14 PM, Soeren_Rabenstein@... wrote:
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 come up with a license template concept. If I
understand this right, we are going to define the reference license
text
of those licenses with a variable data field included in the text. Is
this right?
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 text, even
if templated.

~tom

==
Fedora Project


Re: zlib and libpng licenses clarification

Tom "spot" Callaway
 

On 12/21/2010 09:14 PM, Soeren_Rabenstein@... wrote:
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 come up with a license template concept. If I
understand this right, we are going to define the reference license text
of those licenses with a variable data field included in the text. Is
this right?
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 text, even
if templated.

~tom

==
Fedora Project


Re: zlib and libpng licenses clarification

Soeren_Rabenstein@...
 

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 come up with a license template concept. If I
understand this right, we are going to define the reference license text
of those licenses with a variable data field included in the text. Is
this right?

Cheers
Soeren

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...]
On Behalf Of Tom Callaway
Sent: Wednesday, December 22, 2010 9:20 AM
To: Jilayne Lovejoy
Cc: spdx@...
Subject: Re: zlib and libpng licenses clarification

On 12/21/2010 06:43 PM, Jilayne Lovejoy wrote:
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?
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 or
restrictions of the license, should be a separate and distinct license
for tracking purposes.

I happen to think that approach spirals off into absurdity, but that's
just my opinion. :)

~tom

==
Fedora Project
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
=====================================================================================================================================
This email and any attachments to it contain confidential information and are intended solely for the use of the individual to whom it
is addressed.If you are not the intended recipient or receive it accidentally, please immediately notify the sender by e-mail and delete
the message and any attachments from your computer system, and destroy all hard copies. If any, please be advised that any unauthorized
disclosure, copying, distribution or any action taken or omitted in reliance on this, is illegal and prohibited. Furthermore, any views
or opinions expressed are solely those of the author and do not represent those of ASUSTeK. Thank you for your cooperation.
=====================================================================================================================================


Re: zlib and libpng licenses clarification

Tom "spot" Callaway
 

On 12/21/2010 06:43 PM, Jilayne Lovejoy wrote:
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?
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 or
restrictions of the license, should be a separate and distinct license
for tracking purposes.

I happen to think that approach spirals off into absurdity, but that's
just my opinion. :)

~tom

==
Fedora Project

1341 - 1360 of 1589