Date   

WTFPL(-2.0) license entry

Jan Engelhardt <jengelh@...>
 

The SPDX license list at http://spdx.org/licenses/ has an entry

Do What The F*ck You Want To Public License WTFPL

There are multiple versions of the WTFPL around, and the SPDX entry
shows the WTFPL version 2.0 text. In spirit of the SPDX naming of all
the remaining licenses, the "WTFPL" entry should be renamed to
"WTFPL-2.0".


January SPDX General Meeting Goes Virtual - PLEASE READ

Philip Odence
 

Because the General Meeting falls on Jan 2 and a number of folks will be out or just back from long holidays, we'll do this one virtually, i.e. I will ask all the team leads to provide team updates to me via email and I will issue minutes and solicit comment/thoughts on this list. 

In the meantime, some recommended reading:

Jilayne, Scott and I wrote an article for the I8l FOSS Law Review: 
http://www.ifosslr.org/ifosslr/article/view/89 

I wrote a blog on the state of SPDX (and am still planning another to wrap the year…we'll see): 
http://spdx.org/news/2013-11-14/spdx...how-are-we-doing 


Finally, keep your eyes open for a v2.0 requirements doc that Kirsten Newcomer has been pulling together at the behest of the Business Team (and with review by the Tech Team).


Meeting Time: Thurs, Jan 2, 8am PST / 10 am CST / 11am EST / 15: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

 
Administrative Agenda
Attendance
Approve Minutes- 

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack/Scott



Cross Functional Issues – Phil


article about SPDX in IFOSS Law Review

Jilayne Lovejoy <lovejoylids@...>
 

Hi All,

The latest edition of the IFOSS Law Review is now available: http://www.ifosslr.org/ifosslr/issue/current
and includes an article about SPDX!!  

Happy Holidays,

Jilayne


SPDX Legal Team lead





TR: FOSS: next steps

RUFFIN MICHEL
 

On Wednesday the OMG held a meeting on standardisation issues between organizations on FOSS issues.

It was a kick-off meeting on the topic

I would like to invite you to be part of the discussion if interested.

To do so you need to send an email to request@... to be part of the FOSS OMG mailing list

Bellow is an email of Richard Soley CEO of OMG

 

Michel
----------------------------------------------
On Wednesday 11 December, the OMG hosted a FOSS Licensing Standards Workshop at the OMG Technical Meeting in Santa Clara, California. 
There was significant discussion about the need for new model-based standards (as well as best practices standards) in the area of FOSS licensing.

The areas in which discussion centered, taking into account as much as possible existing standards such as SPDX, included:

  • To kick off the discussion, a reminder of the areas of consideration for new standards, taking into account and using as much as possible existing standards such as SPDX:
  • best practices for choosing a license and potentially agreeing on standard legal FOSS clauses
  • professional certification of FOSS licensing usage
  • capturing FOSS IP information in a Wikipedia-style database
  • agreeing standard contract clauses to lower the cost of supplier/customer relationships, M&A, etc.
  • standardizing unique software identifiers to support the automation of cross-organization identification of licenses & software

The agenda for the day, including presentation materials used, is at http://www.omg.org/news/meetings/tc/ca-13/special-events/FOSS.htm

        -- Richard



 



SPDX Thursday General Meeting Reminder

Philip Odence
 

Meeting Time: Thurs, Dec 5, 8am PST / 10 am CST / 11am EST / 15: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

 
Administrative Agenda
Attendance
Approve Minutes- 

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack/Scott



Cross Functional Issues – Phil


Nov General Meeting Minutes

Philip Odence
 

Just posted the minutes:

Special note:
The SPDX Legal group will be holding a special break out session to review a number of software examples where the SPDX licensing syntax (i.e., license list + AND/OR operators) may not be sufficient to represent the licensing terms of the software. For instance the group will be looking at the various kinds of special exception terms, the use of the ‘+’ in license names and programs derived from multiple source and library files, where each is potentially under a different license. The group will report back to the Legal and Tech working groups with its findings. If you are interested in attending or would like to submit relevant examples send email to Mark.Gisi@....

Thanks,
Phil

L. Philip Odence
Vice President of Corporate and Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence


SPDX Cloud Server now supports SPDX 1.2 file creation

Sameer Ahmed
 

Hi All,

 

Wind River just released SPDX 1.2 support for its free SPDX file creation cloud server.

 

Here is what’s new:

·         Supports newly released SPDX 1.2 format.

·         Improved Analysis Quality – Added several new license detector agents to improve expert system analysis engine.  

·         SPDX data now available in an easy to view spreadsheet format.

·         Upload your own package or now choose from a collection of preloaded sample packages (e.g., Apache Server, U-boot…)

  

You can create an SPDX 1.2 file for free by going to: http://spdx.windriver.com

 

Regards,
Sameer Ahmed

 

 

Sameer Ahmed | Member of Technical Staff - App | Wind River

Email: sameer.ahmed@...

 


Thursday SPDX General Meeting

Philip Odence
 

First some announcements:

News from the Linux Events in Europe

Wind River Presentation on SPDX and Yocto at the Embedded Linux Conference: http://events.linuxfoundation.org/sites/events/files/slides/2013_ELC-E_YP_SPDX.pdf
I also ran a BoF at LinuxCon and presented in intro to SPDX at the Automotive Grade Linux Conference



****

Meeting Time: Thurs, Nov 7, 8am PST / 10 am CST / 11am EST / 15: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

 
Administrative Agenda
Attendance
Approve Minutes- 

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack/Scott



Cross Functional Issues – Phil


(No subject)

RUFFIN MICHEL
 

Dear all,
The OMG (Object Management group) is organizing a workshop on standardizing open source governance practices on December 11 in Santa Clara (CA) http://www.omg.org/news/meetings/tc/ca-13/special-events/FOSS.htm
 
We would like to invite the members of the SPDX group to participate. From my discussions with a lot of companies since two years on this topic, there is more and more interested parties.
 
Michel
 
Michel.Ruffin@..., PhD
Software Coordination Manager, N&P IS/IT
Distinguished Member of Technical Staff
Tel +33 (0) 6 75 25 21 94
Alcatel-Lucent International, Centre de Villarceaux
Route De Villejust, 91620 Nozay, France
 
 
 


1.2 and BoF Report

Philip Odence
 

It's official, 1.2 is up.  Again, huge thanks to all who contributed. Credit Mark Gisi with finding this apt quote:

“people throw stones at you and you turned them into milestones”

             ― Sachin Tendulkar (Ted Williams of Cricket)


I had a good BoF session with folks from Intel, Qualcomm, HP, Orange, Valeo, and others. There were about 12 including a reporter from Munich. I thought this was a terrific turnout given that it was at the end of a long day and directly competed with the beer/wine and appetizers.I went through a presentation, but it was much more of a discussion and there was healthy discussion of just about every slide; we went for an hour and could have gone longer. At least a couple of the participants indicated enough interest to get involved and help. We'll see.


1.2 Announced at LinuxCon Europe

Philip Odence
 

I was going to hold of until the press release tomorrow, but Jim Zemlin jumped the gun slightly, prominently featuring the SPDX 1.2 release in his keynote this morning. Sorry I wasn't quicker getting my camera out, or I would include a pic. The press release is scheduled for 9am UK time Tuesday.

Big thanks and congrats to Kate and the Technical Team for achieving this milestone. And honorable mentions to Jilayne and the Legal team and Jack & Scott and the Business Team for their support. 

Will let you know how my SPDX BoF goes, but keep expectations in check as I seem to be competing with free (as in free beer) beer during my early evening timeslot.

Best,
Phil



SPDX 1.2 - final review - input needed by Oct 18 EOD.

kate.stewart@...
 

Dear SPDX participants,
    The attached specification has all the bugzilla issues targetted to be resolved in SPDX 1.2 addressed, so its pretty close (if no significant feedback in the next few days) we'll be publishing.     The changes since 1.1 have primarily involved standardizing some additional fields for supporting the supply chain information needs,  resolving issues that were found at the bakeoff at Collab by the participants, and giving more flexibility on naming of the licence references that aren't in the SPDX license list ( which has been updated too! ).   There is also a new appendix on the License Template that is being used in the license list. 

    If you have a chance to review it, and spot something that should be fixed:  
1)  If its a typo, spelling, or grammar issue - please send me the page number and description of what should be changed in an email.  I'll do my best to incorporate it in the final pass on Saturday.  
2) If its a problem with the fields and content or a suggestion for further improvement,  please open a bug in bugzilla [1]. 
3) If you have a question that doesn't fall into one of the two above cases,  please feel free to email spdx-tech@...

A very big THANK YOU to all of the bakeoff participants and users of the SPDX 1.1 specification who opened bugs, as well as the tech-team members who worked out fixes for the issues.  In particular, I'd like to thank Bill Schineller, Gary O'Neall, Jack Manbeck and Mark Gisi for their excellent help cleaning up this final version of the specification and getting it ready to publish over the last month.   

Looking forward to your feedback.

Thanks, 
Kate 

[1] https://bugs.linuxfoundation.org/enter_bug.cgi?product=SPDX   


SPDX Awareness Building

Philip Odence
 

At LinuxCon Europe next week, the Linux Foundation will send out a press release announcing version 1.2. Also, in addition to a presentation for Black Duck, I will be hosting BoF session on SPDX and will be joining Claus Peter Wiedemann of Bearing Point to present SPDX at the Automotive Linux event later in the week.

In Asia, YoungTaek Kim will be presenting Samsung's use of SPDX at the Korean Linux Forum in Nov and at the Japan Open Compliance Summit in December. For those who missed the session in New Orleans, here are Taek's slides: http://events.linuxfoundation.org/sites/events/files/slides/Piloting%20SPDX%20in%20Samsung%20-%20case%20studies%20and%20experiences%20%28YoungTaek%20Kim%29.pdf

Lastly, I presented in introduction to SPDX last week at the GENIVI all members meeting in San Diego last week. There is good awareness of SPDX amongst anyone involved in licensing for GENIVI (the open source In-Vehicle Infotainment platform) and this was an opportunity to build awareness with a broader group.

It's exciting to see the word get out across the globe!

Best,
Phil

L. Philip Odence
Vice President of Corporate and Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence


Thursday SPDX General Meeting

Philip Odence
 


Meeting Time: Thurs, Oct 2, 8am PST / 10 am CST / 11am EST / 15: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

 
Administrative Agenda
Attendance
Approve Minutes- 

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack/Scott



Cross Functional Issues – Phil


SPDX License List v1.19 is now live!!

Jilayne Lovejoy <lovejoylids@...>
 


SPDX License List version 1.19 has been released!

The website pages at http://spdx.org/licenses/ has been updated and the download of the SPDX License List can now be found here: http://git.spdx.org/?p=license-list.git;a=summary

Here's a summary of changes over v1.18 (which is also summarized in the last column of the spreadsheet):
 
- 4 new licenses: 
  1. Artistic-1.0-cl8
  2. Artistic-1.0-Perl
  3. IBM-pibs
  4. SISSL-1.2
  5. Unlicense

- 1 license removed: 
  1. Ruby  --> in reviewing a newer version of Ruby License (where the notice regarding the disjunctive license choice changed from GPLv2 or Ruby to BSD-2-clause or Ruby) it was noticed there are also variations in the substantive text of the license.  The current situation (with how Ruby is listed on the SPDX License List) means we have text for the older version and link to the current version, which only adds to potential confusion/ambiguity in that people will continue to use that short identifier perhaps incorrectly.  The SPDX Legal Team is researching the variations and communicating with Ruby to come to an accurate way to represent the different license variations. (In other words, Ruby License will be put back on the SPDX License List in the near future, but in a more accurate and complete way than it had been.)
 
- Differences in Artistic License 1.0 variations accounted for in Notes field
- PHP-3.0 license text updated (was duplicate with PHP-3.01 previously)
- "v1.1" added to full name of SISSL (due to addition of SISSL-1.2)
- W3C - full name corrected
 
.odt and .xls formats of the SPDX License List spreadsheet are included in the git repo download.


Jilayne Lovejoy
SPDX Legal Team lead


Re: PIBS License Identifier

Wolfgang Denk
 

Dear Jilayne,

In message <BDE6BBEB-1FDC-4B89-9576-7BDC59BD4577@...> you wrote:

We are adding this license to the about-to-be-released version 1.19 of
the SPDX License LIst and I had a couple things I wanted to share with
you.
Thanks - much appreciated.

1) it was suggested to use the short identifier: "ibm-pibs" - do you
have any objection to "IBM-pibs"? The reason being that all other SPDX
License List short identifiers tend towards using capital letters unless
spelling a word. I'd prefer to be consistent to this end, but it's not
a major sticking point either way (in other words, if you are already
using the all-lower-case short identifier, I don't see why we can't
adopt that to the SPDX License List - if anyone on the Legal Team
disagrees with me, please speak up)
I like consistency, too, so please feel free to use "IBM-pibs".
the necessary change to the U_boot code is trivial, and was expected,
as I was aware that I was using an self-made name. So no objections
from my side.

2) in regards to the two different copyright dates you mentioned below
(2002 and 1995) - I have compared the actual text of the 2002 version
you listed in this email and the 1995 version you provided links to in a
subsequent email and the only difference is the date itself. In this
case, the SPDX License List matching guidelines would equate these two
license as the same, as this is only a copyright notice year difference,
not a difference in the substantive text of the license.
Agreed. I think I could find some more versions of this license if I
dig deeper in our old code archives, but those I've seen so far all
differ in the date only. So your suggestion makes perfect sense.

If you could get back to me as to the first item as soon as possible,
that would be great.
Thanks for your help with that!

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
Be kind to unkind people - they need it the most.


Re: PIBS License Identifier

Jilayne Lovejoy <lovejoylids@...>
 

Hello Wolfgang,

We are adding this license to the about-to-be-released version 1.19 of the SPDX License LIst and I had a couple things I wanted to share with you.

1) it was suggested to use the short identifier: "ibm-pibs" - do you have any objection to "IBM-pibs"? The reason being that all other SPDX License List short identifiers tend towards using capital letters unless spelling a word. I'd prefer to be consistent to this end, but it's not a major sticking point either way (in other words, if you are already using the all-lower-case short identifier, I don't see why we can't adopt that to the SPDX License List - if anyone on the Legal Team disagrees with me, please speak up)

2) in regards to the two different copyright dates you mentioned below (2002 and 1995) - I have compared the actual text of the 2002 version you listed in this email and the 1995 version you provided links to in a subsequent email and the only difference is the date itself. In this case, the SPDX License List matching guidelines would equate these two license as the same, as this is only a copyright notice year difference, not a difference in the substantive text of the license.

If you could get back to me as to the first item as soon as possible, that would be great.

Cheers,

Jilayne Lovejoy
SPDX Legal Team lead

On Jul 28, 2013, at 8:23 AM, Wolfgang Denk <wd@...> wrote:

Hello,

IBM has published several versions of their PIBS (PowerPC
Initialization and Boot Software) boot loader source code with a
license header like this:

---------- snip ----------
This source code has been made available to you by IBM on an AS-IS
basis. Anyone receiving this source is licensed under IBM
copyrights to use it in any way he or she deems fit, including
copying it, modifying it, compiling it, and redistributing it either
with or without modifications. No license under IBM patents or
patent applications is to be implied by the copyright license.

Any user of this software should understand that IBM cannot provide
technical support for this software and will not be responsible for
any consequences resulting from the use of this software.

Any person who transfers this source code or any derivative work
must include the IBM copyright notice, this paragraph, and the
preceding two paragraphs in the transferred software.

COPYRIGHT I B M CORPORATION 2002
LICENSED MATERIAL - PROGRAM PROPERTY OF I B M
---------- snip ----------

I have another version of this license text dated 1995.

Has any of these been evaluated before? I can't find a SPDX License
Identifier for this?

Thanks in advance.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
Computers are not intelligent. They only think they are.
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx


Re: New Person Questions

Gary O'Neall
 

Hi David,

 

As Mark mentioned, 1.2 is still under development.  The current schedule has the spec being release within the next 2 weeks.  The SPDX tools typically follow within a week.

 

I’ll take care of update the version number of the tag to RDF tools (your #1 below).  Thanks for pointing that out.

 

Feel free to report any problems or suggest any improvements in the tools through bugs.linuxfoundation.com, the spdx-tech mailing list, or emailing me.

 

Thanks,


Gary

 

From: Gisi, Mark [mailto:Mark.Gisi@...]
Sent: Wednesday, September 11, 2013 9:18 AM
To: Good, David; spdx@...
Cc: Gary O'Neall
Subject: RE: New Person Questions

 

Hi David,

 

Thank you for expressing interest in SPDX and for your insightful questions.

 

>>  SPDX-1.2 is not supported by this version of the rdf parser

 

The SPDX 1.2 version of the specification has not been released yet. It is in the final stage of review and is expected to be released around the end of the month. Wind River wanted to provide a customer with access to a beta implementation of 1.2 via our cloud solution. This has created some confusion. It was a mistake to provide general available access to a beta version prior to the final release of the 1.2 specification. I apologize.

 

Gary O’Neal is the SPDX tools lead who could best address your questions with respect to upcoming SPDX project tool support for the different versions of the specification.

 

Kind regards,

Mark

 

Mark Gisi | Wind River | Senior Intellectual Property Manager

Tel (510) 749-2016 | Fax (510) 749-4552

 

 

 

 

From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Good, David
Sent: Wednesday, September 11, 2013 7:23 AM
To: spdx@...
Subject: New Person Questions

 

Hi!

I’ve just gotten started looking at generating SPDX files for our WindRiver Linux-based project.

Wind River gave us a bunch of SPDX files in the form of Excel spreadsheets,

but I need to generate some more, so I was looking at the tools here.

 

Before splattering things into bugzilla, I thought I’d ask about proper channels.

 

Should this all be in the Technical newsgroup?

 

1) On the tools -> Tag to RDF page, the offered download of 1.1.7 actually gives one 1.1.17

     Is there a webmaster to contact?

 

2) I generated a tag file using the WindRiver cloud service,

and running TagToRdf version 1.1.17 reports:

                unrecognized SPDX Tag: LicenseListVersion

It was easy to work-around this, I just commented out the line

                LicenseListVersion: 1.18

(or is TagToRdf expecting LicenseListVersion: 1.17 ?)

If I look on the Licenses page, the current version is 1.18, but there doesn’t appear to

be any history of previous versions of the license list?  What changed from 1.17 to 1.18?

Is LicenseListVersion an invalid tag?  or is TagToRdf wrong?

 

3) The latest version of RdfToSpreadsheet is 1.1.3,

and running it on the output of TagToRdf reports:

                SPDX-1.2 is not supported by this version of the rdf parser

It did appear to work.

Are there plans to update RdfToSpreadsheet to handle SPDX-1.2?

Is the tool disconnect worthy of bugzilla?

 

 

D.Good

 


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


Re: New Person Questions

Mark Gisi
 

Hi David,

 

Thank you for expressing interest in SPDX and for your insightful questions.

 

>>  SPDX-1.2 is not supported by this version of the rdf parser

 

The SPDX 1.2 version of the specification has not been released yet. It is in the final stage of review and is expected to be released around the end of the month. Wind River wanted to provide a customer with access to a beta implementation of 1.2 via our cloud solution. This has created some confusion. It was a mistake to provide general available access to a beta version prior to the final release of the 1.2 specification. I apologize.

 

Gary O’Neal is the SPDX tools lead who could best address your questions with respect to upcoming SPDX project tool support for the different versions of the specification.

 

Kind regards,

Mark

 

Mark Gisi | Wind River | Senior Intellectual Property Manager

Tel (510) 749-2016 | Fax (510) 749-4552

 

 

 

 

From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Good, David
Sent: Wednesday, September 11, 2013 7:23 AM
To: spdx@...
Subject: New Person Questions

 

Hi!

I’ve just gotten started looking at generating SPDX files for our WindRiver Linux-based project.

Wind River gave us a bunch of SPDX files in the form of Excel spreadsheets,

but I need to generate some more, so I was looking at the tools here.

 

Before splattering things into bugzilla, I thought I’d ask about proper channels.

 

Should this all be in the Technical newsgroup?

 

1) On the tools -> Tag to RDF page, the offered download of 1.1.7 actually gives one 1.1.17

     Is there a webmaster to contact?

 

2) I generated a tag file using the WindRiver cloud service,

and running TagToRdf version 1.1.17 reports:

                unrecognized SPDX Tag: LicenseListVersion

It was easy to work-around this, I just commented out the line

                LicenseListVersion: 1.18

(or is TagToRdf expecting LicenseListVersion: 1.17 ?)

If I look on the Licenses page, the current version is 1.18, but there doesn’t appear to

be any history of previous versions of the license list?  What changed from 1.17 to 1.18?

Is LicenseListVersion an invalid tag?  or is TagToRdf wrong?

 

3) The latest version of RdfToSpreadsheet is 1.1.3,

and running it on the output of TagToRdf reports:

                SPDX-1.2 is not supported by this version of the rdf parser

It did appear to work.

Are there plans to update RdfToSpreadsheet to handle SPDX-1.2?

Is the tool disconnect worthy of bugzilla?

 

 

D.Good

 


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


New Person Questions

Good, David <dgood@...>
 

Hi!

I’ve just gotten started looking at generating SPDX files for our WindRiver Linux-based project.

Wind River gave us a bunch of SPDX files in the form of Excel spreadsheets,

but I need to generate some more, so I was looking at the tools here.

 

Before splattering things into bugzilla, I thought I’d ask about proper channels.

 

Should this all be in the Technical newsgroup?

 

1) On the tools -> Tag to RDF page, the offered download of 1.1.7 actually gives one 1.1.17

     Is there a webmaster to contact?

 

2) I generated a tag file using the WindRiver cloud service,

and running TagToRdf version 1.1.17 reports:

                unrecognized SPDX Tag: LicenseListVersion

It was easy to work-around this, I just commented out the line

                LicenseListVersion: 1.18

(or is TagToRdf expecting LicenseListVersion: 1.17 ?)

If I look on the Licenses page, the current version is 1.18, but there doesn’t appear to

be any history of previous versions of the license list?  What changed from 1.17 to 1.18?

Is LicenseListVersion an invalid tag?  or is TagToRdf wrong?

 

3) The latest version of RdfToSpreadsheet is 1.1.3,

and running it on the output of TagToRdf reports:

                SPDX-1.2 is not supported by this version of the rdf parser

It did appear to work.

Are there plans to update RdfToSpreadsheet to handle SPDX-1.2?

Is the tool disconnect worthy of bugzilla?

 

 

D.Good

 


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

681 - 700 of 1543