Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python-2.0.1 is FSF approved but not OSI approved #1929

Closed
wants to merge 1 commit into from

Conversation

akostadinov
Copy link

@akostadinov akostadinov commented Apr 13, 2023

License was added with #1549 as a follow up on #1200

renaming license to match FSF identifier [1][2]

In #1200 it is stated that the license is FSF approved but no OSI
approved or at least not with the right name. With a link to the FSF
website [1].

So I'm adding this attribute to the license for it to be properly tagged
as FSF approved.

[1] https://www.gnu.org/licenses/license-list.en.html#Python
[2] https://wking.github.io/fsf-api/licenses-full.json

@akostadinov
Copy link
Author

Actually in FSF JSON [1] it's identifier is "Python". So probably just rename identifier to Python.

[1] https://wking.github.io/fsf-api/licenses-full.json

License was added with spdx#1549 as a follow up on spdx#1200

Renaming license to match FSF identifier see [1].

[1] https://wking.github.io/fsf-api/licenses-full.json
@akostadinov
Copy link
Author

But then in its own page it is listed as Python-2.0.1...

https://directory.fsf.org/wiki/License:Python-2.0.1

So an alternative would be to somehow match it with a different identifier in the JSON. But I don't see a way presently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant