|
CDDL-1.0 broken link
Vladimír Čunát <vcunat@...>
Hi,
(I'm not sure this is the proper place to report; please, CC me in the answers.) the first link in http://spdx.org/licenses/CDDL-1.0 is broken, and it looks like a permanent breakage. Vlada |
|
|
|
July General Meeting Minutes & IMPORTANT QUESTION
Philip Odence
Please reply (not Reply All) and let me know if you are attending or may be attending LinuxCon.
We will have a ~half day face to face meeting, still zeroing in on Wed or Thursday, and want to make sure we have a sense for who will be there.
General Meeting/Minutes/2014-07-03
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Kate (wrote in)
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Thursday SPDX General Meeting Reminder [license list info]
J Lovejoy
Hi Oliver,
toggle quoted message
Show quoted text
Indeed, Phil is right - all are welcome! In addition to the link Phil included below, there is also this page explaining when/how the license list inclusion guidelines came about: http://wiki.spdx.org/view/Legal_Team/Decisions/Inclusion_Guidelines_(Background) We also started tracking the status of requests around the same time, which is on the wiki here: http://wiki.spdx.org/view/Legal_Team/Decisions/Inclusion_Guidelines_(Background) Any discussion around a decision would be recorded in the relevant meeting minutes, but the best way to participate is of course to join the meetings, as meeting minutes often summarize any discussion. Cheers, Jilayne On Jul 7, 2014, at 2:08 PM, Philip Odence <podence@...> wrote:
|
|
|
|
Re: Thursday SPDX General Meeting Reminder
Philip Odence
Oliver,
There are a number of people on the Legal Team who are not lawyers. We would welcome your participation.
Best,
Phil
From: "Fendt, Oliver" <oliver.fendt@...>
Date: Mon, 7 Jul 2014 10:27:21 +0000 To: Phil Odence <podence@...>, Kate Stewart <kate.stewart@...>, "spdx@..." <spdx@...> Subject: AW: AW: Thursday SPDX General Meeting Reminder Hi Phil,
thanks that would really help. If it is not a requirement to be a lawyer, then I will be happy to participate in the legal team, as well as in the technical team. You are right the time is sometimes a problem but also I understand your restrictions.
Best regards
Oliver
Von: Philip Odence [mailto:podence@...]
Thank you for the clarification Oliver. This kind of feedback it very helpful. We try out best to lay out the inclusion criteria here: Also, it would be great if you, or someone from Siemens, would participate in our Legal Team meetings. In fact, we would welcome participation from Siemens on all of our teams. We try to schedule at times that are not too difficult for CET and if Europe participation increases, we are willing to look at moving the meeting, although we need to be mindful of having heavy west coast US participation as well. Best regards, Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
From:
"Fendt, Oliver" <oliver.fendt@...>
Hi all, sorry for not being able to participate yesterday in the conf call. I want to comment on one topic of the last minutes. The topic is: “ o Mikael delivered a workshop at Siemens They didn't understand license request process Mikael encouraged them to participate in SPDX “
I want to thank Mikael for the presentation. He did a very well job and gave us an interesting talk although he had a flue. In the Q&A part of his talk, I raised the point that at least for me the criteria a license has to fulfill to be accepted for inclusion in the SPDX® license list is not really transparent to me. In the past I submitted several licenses, some were accepted and some not. That’s totally ok but and the reasons for not accepting those were not transparent to me, like “this is not really an Open Source license” although already some creative commons license instances are in the SPDX license list which are not compliant to the open source definition as well. Another license was not accepted because it has no version number. When I raised the point to Mikael I wanted to express that the process for submission is quite clear and we understand it, because it is well described. But it is not described what criteria are checked by the team in charge in order to decide whether the license will be included or not. It would really help (at least me) if these criteria are described because this would help me to save effort and submit in future only those which will meet al criteria. I hope that the topic of the minutes is bit more clear now
regards Oliver
Von:spdx-bounces@...
[mailto:spdx-bounces@...]
Im Auftrag von kate.stewart@...
Appologies, have a work conflict today and not able to join in.
Technical team activities: - work continues on spec. Have resolved out file types, file usage portions. - decision made to not include the RDF vocabulary in the SPEC going forward, Gary is was having issues regenerating it in form suitable for inclusion, and prefers to go with a different tool in future. Spec will be the master and refer to a static version, that will be on web site.
On Wednesday, July 2, 2014 6:56 PM, Philip Odence <podence@...>
wrote:
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Administrative Agenda Attendance Approve Minutes- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Thursday SPDX General Meeting Reminder
Oliver Fendt
Hi Phil,
thanks that would really help. If it is not a requirement to be a lawyer, then I will be happy to participate in the legal team, as well as in the technical team. You are right the time is sometimes a problem but also I understand your restrictions.
Best regards
Oliver
Von: Philip Odence [mailto:podence@...]
Thank you for the clarification Oliver. This kind of feedback it very helpful. We try out best to lay out the inclusion criteria here: Also, it would be great if you, or someone from Siemens, would participate in our Legal Team meetings. In fact, we would welcome participation from Siemens on all of our teams. We try to schedule at times that are not too difficult for CET and if Europe participation increases, we are willing to look at moving the meeting, although we need to be mindful of having heavy west coast US participation as well. Best regards, Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
From:
"Fendt, Oliver" <oliver.fendt@...>
Hi all, sorry for not being able to participate yesterday in the conf call. I want to comment on one topic of the last minutes. The topic is: “ o Mikael delivered a workshop at Siemens They didn't understand license request process Mikael encouraged them to participate in SPDX “
I want to thank Mikael for the presentation. He did a very well job and gave us an interesting talk although he had a flue. In the Q&A part of his talk, I raised the point that at least for me the criteria a license has to fulfill to be accepted for inclusion in the SPDX® license list is not really transparent to me. In the past I submitted several licenses, some were accepted and some not. That’s totally ok but and the reasons for not accepting those were not transparent to me, like “this is not really an Open Source license” although already some creative commons license instances are in the SPDX license list which are not compliant to the open source definition as well. Another license was not accepted because it has no version number. When I raised the point to Mikael I wanted to express that the process for submission is quite clear and we understand it, because it is well described. But it is not described what criteria are checked by the team in charge in order to decide whether the license will be included or not. It would really help (at least me) if these criteria are described because this would help me to save effort and submit in future only those which will meet al criteria. I hope that the topic of the minutes is bit more clear now
regards Oliver
Von:
spdx-bounces@... [mailto:spdx-bounces@...]
Im Auftrag von kate.stewart@...
Appologies, have a work conflict today and not able to join in.
Technical team activities: - work continues on spec. Have resolved out file types, file usage portions. - decision made to not include the RDF vocabulary in the SPEC going forward, Gary is was having issues regenerating it in form suitable for inclusion, and prefers to go with a different tool in future. Spec will be the master and refer to a static version, that will be on web site.
On Wednesday, July 2, 2014 6:56 PM, Philip Odence <podence@...>
wrote:
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Administrative Agenda Attendance Approve Minutes- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Thursday SPDX General Meeting Reminder
Philip Odence
Thank you for the clarification Oliver. This kind of feedback it very helpful.
We try out best to lay out the inclusion criteria here:
Also, it would be great if you, or someone from Siemens, would participate in our Legal Team meetings. In fact, we would welcome participation from Siemens on all of our teams. We try to schedule at times that are not too difficult for CET and if Europe
participation increases, we are willing to look at moving the meeting, although we need to be mindful of having heavy west coast US participation as well.
Best regards,
Phil
L. Philip Odence
Vice President and General Manager
Black Duck
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence
From: "Fendt, Oliver" <oliver.fendt@...>
Date: Fri, 4 Jul 2014 08:26:25 +0000 To: Kate Stewart <kate.stewart@...>, Phil Odence <podence@...>, "spdx@..." <spdx@...> Subject: AW: Thursday SPDX General Meeting Reminder Hi all, sorry for not being able to participate yesterday in the conf call. I want to comment on one topic of the last minutes. The topic is: “ o Mikael delivered a workshop at Siemens They didn't understand license request process Mikael encouraged them to participate in SPDX “
I want to thank Mikael for the presentation. He did a very well job and gave us an interesting talk although he had a flue. In the Q&A part of his talk, I raised the point that at least for me the criteria a license has to fulfill to be accepted for inclusion in the SPDX® license list is not really transparent to me. In the past I submitted several licenses, some were accepted and some not. That’s totally ok but and the reasons for not accepting those were not transparent to me, like “this is not really an Open Source license” although already some creative commons license instances are in the SPDX license list which are not compliant to the open source definition as well. Another license was not accepted because it has no version number. When I raised the point to Mikael I wanted to express that the process for submission is quite clear and we understand it, because it is well described. But it is not described what criteria are checked by the team in charge in order to decide whether the license will be included or not. It would really help (at least me) if these criteria are described because this would help me to save effort and submit in future only those which will meet al criteria. I hope that the topic of the minutes is bit more clear now
regards Oliver
Von:
spdx-bounces@... [mailto:spdx-bounces@...]
Im Auftrag von kate.stewart@...
Appologies, have a work conflict today and not able to join in.
Technical team activities: - work continues on spec. Have resolved out file types, file usage portions. - decision made to not include the RDF vocabulary in the SPEC going forward, Gary is was having issues regenerating it in form suitable for inclusion, and prefers to go with a different tool in future. Spec will be the master and refer to a static version, that will be on web site.
On Wednesday, July 2, 2014 6:56 PM, Philip Odence <podence@...>
wrote:
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Administrative Agenda Attendance Approve Minutes- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Thursday SPDX General Meeting Reminder
Oliver Fendt
Hi all, sorry for not being able to participate yesterday in the conf call. I want to comment on one topic of the last minutes. The topic is: “ o Mikael delivered a workshop at Siemens They didn't understand license request process Mikael encouraged them to participate in SPDX “
I want to thank Mikael for the presentation. He did a very well job and gave us an interesting talk although he had a flue. In the Q&A part of his talk, I raised the point that at least for me the criteria a license has to fulfill to be accepted for inclusion in the SPDX® license list is not really transparent to me. In the past I submitted several licenses, some were accepted and some not. That’s totally ok but and the reasons for not accepting those were not transparent to me, like “this is not really an Open Source license” although already some creative commons license instances are in the SPDX license list which are not compliant to the open source definition as well. Another license was not accepted because it has no version number. When I raised the point to Mikael I wanted to express that the process for submission is quite clear and we understand it, because it is well described. But it is not described what criteria are checked by the team in charge in order to decide whether the license will be included or not. It would really help (at least me) if these criteria are described because this would help me to save effort and submit in future only those which will meet al criteria. I hope that the topic of the minutes is bit more clear now
regards Oliver
Von: spdx-bounces@... [mailto:spdx-bounces@...]
Im Auftrag von kate.stewart@...
Appologies, have a work conflict today and not able to join in.
Technical team activities: - work continues on spec. Have resolved out file types, file usage portions. - decision made to not include the RDF vocabulary in the SPEC going forward, Gary is was having issues regenerating it in form suitable for inclusion, and prefers to go with a different tool in future. Spec will be the master and refer to a static version, that will be on web site.
On Wednesday, July 2, 2014 6:56 PM, Philip Odence <podence@...> wrote:
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Administrative Agenda Attendance Approve Minutes- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence Vice President and General Manager Black Duck 8 New England Executive Park, Suite 211, Burlington MA 01803 Phone: 781.810.1819, Mobile: 781.258.9502 Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Thursday SPDX General Meeting Reminder
kate.stewart@...
Appologies, have a work conflict today and not able to join in. Technical team activities: - work continues on spec. Have resolved out file types, file usage portions. - decision made to not include the RDF vocabulary in the SPEC going forward, Gary is was having issues regenerating it in form suitable for inclusion, and prefers to go with a different tool in future. Spec will be the master and refer to a static version, that will be on web site. On Wednesday, July 2, 2014 6:56 PM, Philip Odence <podence@...> wrote:
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 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- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence
Vice President and General Manager
Black Duck
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
_______________________________________________ Spdx mailing list Spdx@... https://lists.spdx.org/mailman/listinfo/spdx |
|
|
|
Thursday SPDX General Meeting Reminder
Philip Odence
GENERAL MEETING
Meeting Time: Thurs, July 3, 8am PDT / 10 am CDT / 11am EDT / 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- below and http://wiki.spdx.org/view/General_Meeting/Minutes/2014-06-05
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
L. Philip Odence
Vice President and General Manager
Black Duck
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence
General Meeting/Minutes/2014-06-05
ContentsBiz Team Report - Jack
Legal Team Report - Jilayne
Tech Team Report - Gary
Cross Functional Issues – Phil
Attendees
|
|
|
|
SPDX General Meeting Reminder. Toda
Philip Odence
Sorry for the late reminder.
GENERAL MEETING
Meeting Time: Thurs, June 5, 8am PDT / 10 am CDT / 11am EDT / 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- Attached below
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
From: Phil Odence <podence@...>
Date: Tue, 13 May 2014 10:33:16 -0400 To: <spdx@...> Subject: Minutes from May General Meeting Next meeting is June 5 at the normal time. (11EDT)
General Meeting/Minutes/2014-05-01
ContentsTech Team Report - Kate
Biz Team Report - Jack (unable to attend, but provided written summary)
Legal Team Report - Jilayne
Cross Functional Issues – Phil
Attendees
|
|
|
|
Minutes from May General Meeting
Philip Odence
Next meeting is June 5 at the normal time. (11EDT)
General Meeting/Minutes/2014-05-01
ContentsTech Team Report - Kate
Biz Team Report - Jack (unable to attend, but provided written summary)
Legal Team Report - Jilayne
Cross Functional Issues – Phil
Attendees
|
|
|
|
Re: Help converting Fedora license IDs to SPDX format
J Lovejoy
Hi Richard (x2)!
toggle quoted message
Show quoted text
Richard H - great to hear you are using the SPDX License List for identifying licenses in AppStream for a number of reasons. Your responses below are all correct in terms of understanding the SPDX License List, so I’ll only add a bit more info in regards to the issues you have come across. As Phil mentioned in his response, the SPDX legal team is currently working through the Fedora Good License list (https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Good_Licenses) in order to identify where the SPDX License List is missing a license that is on the Fedora list. The inclination is to add any such licenses and try to align the SPDX short identifier with whatever Fedora had been using. However, for the reasons you and Richard F identified (e.g. I’ll call it the “MIT bucket,” identifying that Fedora uses to describe similar licenses) not all the short identifiers will align. I suspect we will end up with a “equivalency” document as part of the SPDX License List reference materials, for convenience. In any case, the next release of the SPDX License List is currently schedule to coincide with the release of 2.0 of the spec, so at that point you will see many additions to this end. In regards to the exceptions, this is also something we are currently working on. As of 2.0, license exceptions will be treated as a modifier to the base license to better enable capturing the various exceptions that exist in the wild. An explanation of this change, as well as the bigger picture in regards to creating a better way to express complex licensing info for files was recently summarized here: http://article.gmane.org/gmane.comp.licenses.spdx.legal/855/match=expression If you are not on the legal mailing list, please join!! (http://lists.spdx.org/mailman/listinfo/spdx-legal) <<I have responded to both the general and legal mailing lists here, but subsequent discussion should move to the legal list only, where it will get more direct responses/discussion :) Thanks! Jilayne SPDX Legal Team co-lead opensource@... On May 2, 2014, at 8:03 AM, Richard Hughes <hughsient@...> wrote:
On 2 May 2014 14:41, Richard Fontana <rfontana@...> wrote:Also (based on what little documentation on AppStream that I looked at) it is unclear what the purposes are in the case of AppStream.So, for AppStream the idea is to explain the licenses in the |
|
|
|
Re: Help converting Fedora license IDs to SPDX format
On 2 May 2014 14:41, Richard Fontana <rfontana@...> wrote:
Also (based on what little documentation on AppStream that I looked at) it is unclear what the purposes are in the case of AppStream.So, for AppStream the idea is to explain the licenses in the user-facing software center, e.g. gnome-software or apper for KDE. This would mean you could click on a link that says "GPLv3+" and get sent to http://spdx.org/licenses/GPL-3.0+ rather than just having a license string to look at and perhaps Google. My knowledge of SPDX itself is limited, but if you look at:Right. The idea is that you can define "upstream" what licenses your software is using, rather than relying on the packager to work it out and apply broad classification during the packaging step. I'm really only doing this for applications not explicitly specifying what SPDX licences they are using. A good example, though not on your list probably because you assume itRight. For Fedora, however, "MIT" is supposedYes, this is the fudge-factor I was talking about. Ideally we would have all these MIT-variants as separate SPDX license IDs. So for the ones you list, first of all for most of these there isn'tRight. (By contrast there areAgreed, I didn't know whether the "with exceptions" AGPL thing could/should be broken down any further for SPDX. This is what Fedora "MIT" means some of the time but not allYes, it's not ideal at all, but the data I'm presenting is more of an interesting titbit of information about the application rather than a comprehensive legal explanation. Apps are still free to specify a special license ID of "libtiff with extensions" but it just won't be hyperlinked in the front end tool. Richard |
|
|
|
Re: Help converting Fedora license IDs to SPDX format
Richard Fontana
On Fri, May 02, 2014 at 12:53:30PM +0100, Richard Hughes wrote:
Hi all,I think the problem is that you are dealing with three different notions of license identifiers, two of which are superficially the same in that AppStream has decided to use SPDX identifiers for its own purposes, if I understand correctly. Also (based on what little documentation on AppStream that I looked at) it is unclear what the purposes are in the case of AppStream. My knowledge of SPDX itself is limited, but if you look at: http://spdx.org/spdx-license-list/matching-guidelines you will see that SPDX is using license identifiers in an entirely different way from how Fedora uses RPM metadata license identifiers. A good example, though not on your list probably because you assume it is not problematic, is "MIT". For SPDX, this means http://spdx.org/licenses/MIT#licenseText subject to the points made in the SPDX matching guidelines. For Fedora, however, "MIT" is supposed to mean a wide range of different license texts (which SPDX would surely treat as distinct, non-matching licenses) that were determined by the Fedora Project to be what I myself might verbosely call "X Window Project-descended license family licenses, particularly as distinguished from BSD-family licenses" if I had to call it anything. So for the ones you list, first of all for most of these there isn't any SPDX license identifier anyway even if you ignore the issue I just talked about, since the SPDX list is, at least at present, not meant to be a comprehensive list of all licenses ever encountered in, say, a conventional Linux distribution, but rather those that are "commonly found". In your list, none of those are "commonly found" in that sense except that the AGPLv3 part of "AGPLv3 with exceptions" is *likely* to correspond to SPDX AGPL-3.0, but not the "with exceptions" part which has no SPDX license identifier counterpart. (By contrast there are some GPLv2 and GPLv3 SPDX license identifiers that include some commonly-found permissive exceptions.) So when you say "I'm required to convert the existing Fedora license tag to an SPDX-compatible string so it can be made into a hyperlink and be clickable", this is only meaningful if what you mean by "Most license IDs are either the same, or map between one and the other with a small fudge factor" is understood with my point about, e.g. the significant distinction between SPDX "MIT" and Fedora "MIT" in mind. And what would "MIT" hyperlink to -- the OSI version of the MIT license? This is what Fedora "MIT" means some of the time but not all of the time. - Richard |
|
|
|
Re: Help converting Fedora license IDs to SPDX format
Philip Odence
Richard,
toggle quoted message
Show quoted text
I¹m moving you from the general SPDX list to the legal team. We are actually in the middle of marching through the Fedora licenses and are happy to work with you on this. You should be hearing shortly from someone on our legal team. Best, Phil Odence SPDX Chair On 5/2/14, 7:53 AM, "Richard Hughes" <hughsient@...> wrote:
Hi all, |
|
|
|
Help converting Fedora license IDs to SPDX format
Hi all,
I hope I'm asking in the right place, if not please disregard this message. When writing AppStream metadata I'm required to convert the existing Fedora license tag to an SPDX-compatible string so it can be made into a hyperlink and be clickable. Most license IDs are either the same, or map between one and the other with a small fudge factor, but I'm having problems finding SPDX licences for a few Fedora IDs. The fedora license ID's that probably should map to something (ideas welcome!): * Afmparse * AGPLv3 with exceptions * AGPLv3+ with exceptions * libtiff * mecab-ipadic * Mup * OpenPBS * softSurfer * Teeworlds * TORQUEv1.1 * UCD * Vim * XSkat * Baekmuk * Bitstream Vera * Crystal Stacker * Liberation * MgOpen * mplus There are a few things that don't make sense, e.g. * Public Domain * Copyright only * Freely redistributable without restriction * Redistributable, no modification permitted If anyone knows of any existing SPDX IDs suitable for any of the above, I'd be very grateful. Thanks. Richard |
|
|
|
Thursday SPDX General Meeting
Philip Odence
REMINDER – Call for talks
GENERAL MEETING
Meeting Time: Thurs, May 1, 8am PDT / 10 am CDT / 11am EDT / 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- Note, minutes have not yet been posted.
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack
Cross Functional Issues – Phil
|
|
|
|
Call for Talks...SPDX to rock LinuxCon
Philip Odence
Although LinuxCon NA is a few months off (Chicago, Aug 20) we are just one week from the deadline for submitting talks (May 2). “SPDX” is specifically mentioned under suggested topics, and we would love to get a few submissions. Jack tapped me to co-submit
an update on SPDX 2.0 and we are talking about doing a hands on session with tools, but there’s certainly room for other topics. In particular, it would be interesting to get some talks on usage. The crowd would be really interested to understand what you
are doing in your company with SPDX. If you don’t feel you have a full 40 minutes worth but would like to talk, let me and Jack know and perhaps we can pull together 3 or 4 mini presentations.
Here’s the link for submitting:
|
|
|
|
Re: TripleCheck 0.4
Lamons, Scott (Open Source Program Office) <scott.lamons@...>
Nick,
toggle quoted message
Show quoted text
While I've only spent ~15min with the tool, I was very impressed with the ease of use and the ability to install this and get almost immediate and useful! results. Great work! I'll keep you posted on my findings. Best Regards, Scott -----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Nuno Brito Sent: Monday, March 31, 2014 1:02 PM To: Manbeck, Jack; spdx@... Subject: RE: TripleCheck 0.4 Hi Jack, Thank you for the kind suggestion, very appreciated. I'd just ask to wait some weeks before the tool is listed. Some defects were reported that I'd like to get sorted before more users run the software. Will get back to this message as soon as possible. With kind regards, Nuno Brito On March 31, 2014 8:44:47 PM GMT+02:00, "Manbeck, Jack" <j-manbeck2@...> wrote: Nuno,_______________________________________________ Spdx mailing list Spdx@... https://lists.spdx.org/mailman/listinfo/spdx |
|
|
|
Re: TripleCheck 0.4
Nuno Brito
Hi Jack,
I'd like to follow-up on this message if possible, the points from the requirement list were quoted to place my answers in context. The tool must currently support SPDX (i.e. it is not a planned release).Checked. You have a page on your website that describes how the tool supports SPDX. This will be the link you provide in the Required Information below.Checked. Whether this is a community or commercial tool.Community. Contributions from other developers interested in submitting additional license detection rules and fix defects are warmly welcome through github or email. To clarify, I use this software on commercial practice to "scratch my own itch" [1] in the open source way of doing things. A small logo which can be displayed. This is optional. If provided it must meet the following criteriaAttached to this message you find a TripleCheck with 251x122px as specified in the criteria A short teaser of one or two sentences that describes your tool. No more than 160 characters including spacesStraight-forward free tool to create SPDX reports right from your desktop. A long description which can be up to a couple of paragraphs. Try not to get too verbose. You will have a link to your website for lengthy explanations.The TripleCheck reporter is the ideal tool for a quick overlook of the licensing compliance status for a given set of source code files in your desktop computer (Windows, Linux, Mac OSX). If some license or copyright is not detected by the tool, you can easily add new rules by yourself. We are building a community around open source tooling and your help is welcome to grow the open database of licensing rules. Look for us on GitHub. An http link to your site for access to the tool and information on how it supports SPDX.http://www.triplecheck.de/download/ The current version of the tool is 0.6 so perhaps is better to omit version references and just call the tool "TripleCheck reporter". If there is anything else needed, please do let me know. Just in case, I have prepared a short video showcasing the tool that you find at http://youtu.be/nljP6hC8xbc With kind regards, Nuno Brito [1] http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar#Lessons_for_creating_good_open_source_software --- email: nuno.brito@... phone: +49 615 146 03187 On 2014-03-31 20:44, Manbeck, Jack wrote: Nuno, |
|
|
