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 PSF-2.0 license (https://spdx.org/licenses/PSF-2.0) #175

Closed
wants to merge 1 commit into from

Conversation

felixfontein
Copy link
Contributor

This is used in quite a few collections, and in ansible-core as well (often due to the vendored LooseVersion / StrictVersion code). See for example https://github.com/ansible/ansible/blob/devel/licenses/PSF-license.txt or https://github.com/ansible-collections/community.crypto/blob/main/PSF-license.txt.

@felixfontein
Copy link
Contributor Author

The CI failures seem to be unrelated to this PR.

@awcrosby
Copy link
Contributor

@felixfontein can you add a No-Issue on a separate line in your commit (and also make sure your commit is signed) so that Commit Check used in GalaxyNG / commit-check passes?

And yes, the test coverage failure is unrelated, I'll handle that separately. Thanks for adding this!

@felixfontein
Copy link
Contributor Author

@awcrosby hmm, with 'signed', you mean actually signed with GPG, and not just git commit --signoff, right? (Guessing from the error message I got :) ) I guess I'll first have to set up some infrastructure for that...

If you prefer to create your own PR for this instead of waiting for me to set everything up (I won't really have time for it until in some days) feel free to do so :)

@awcrosby
Copy link
Contributor

@felixfontein yes --gpg-sign

@awcrosby
Copy link
Contributor

closing in favor of #178

@awcrosby awcrosby closed this Aug 22, 2022
@felixfontein felixfontein deleted the psf-2.0 branch August 23, 2022 05:23
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.

2 participants