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

Add proper license attribute per OSI license #155

Merged
merged 5 commits into from
Feb 17, 2021
Merged

Add proper license attribute per OSI license #155

merged 5 commits into from
Feb 17, 2021

Conversation

rpcme
Copy link
Contributor

@rpcme rpcme commented Feb 17, 2021

Issue #, if available:
N/A
Description of changes:
We should be using the OSI license attribute in the classifier, and the license attribute should match that.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

setup.py Outdated
@@ -8,11 +8,16 @@
setup(
name='awsiotsdk',
version='1.0.0-dev',
license='Apache-2.0',
license='Apache Software License',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should remain as "Apache-2.0'?
Honestly, this all baffles me 😐
Ask a lawyer?

Here are some github issues where people are just as confused as us regarding what they're supposed to do, because "Apache Software License" is less specific than "Apache-2.0" but it's the only classifier available:
pypi/legacy#91
pypa/trove-classifiers#17

And here's an issue about how the classifier field is recommended in the dev guide, but the APIs still use the license field:
pypi/warehouse#8960

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Different communities have different standardized names for common licenses. The list of valid classifiers for PyPI is at https://pypi.org/classifiers/ and you can search for Apache there to see which is preferred.

@graebm graebm merged commit 7a5a6e4 into aws:main Feb 17, 2021
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.

None yet

3 participants