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.