Miroslav Suchý wrote:
> There are two common ways to find out what SPDX identifier you should use
> in such cases.
>
>
> 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> identify your license. This is a Chrome and Firefox plugin and allows you
> to select the text; and in the context menu, you can choose to identify
> the license. It will print, e.g., that it matches 60% of the MIT-feh
> license and highlight the difference. Or...
>
>
> 2) you can navigate to
>
> https://docs.fedoraproject.org/en-US/legal/allowed-licenses/
>
> in the search box above the first table, you enter your license and filter
> the content. If you enter "MIT", it will find you 26 licenses. Out of
> them, 15 have "MIT" in the "Fedora abbreviation" column (Hmm, this should
> be changed to "legacy name"). Now you have to open the link in the "URL"
> column and find your package's license. This may look painful, but you
> usually find the correct license within a few clicks.
That is a lot of pointless work for details that almost certainly is going
to care about, or even notice to begin with.
I would suggest just picking the most common option (MIT→MIT and BSD→BSD-3-
Clause) and letting people file a bug if it turns out to be wrong. We have
had packages with more inaccurate License tags than that (wrong GPL version,
GPL instead of LGPL or vice-versa, etc., sometimes even entirely wrong
licenses).
Kevin Kofler
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
