Account for the chapel.py license in the SPDX expression and license files #112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that we are using an SPDX expression for the license metadata, we can account for the BSD-2-Clause license (`sphinxcontrib/chapeldomain/LICENSE`) of `chapel.py`. See https://peps.python.org/pep-0639/#spdx-license-expression-syntax.
Member
|
Hmm, I don't think the license mismatch is intentional. I suspect we just missed it when migrating to Apache 2.0 (I want to say we used to be BSD at the beginning, but it's been a long time since we switched). Lemme dig through the history a little bit and get back to you on that |
Member
|
Okay, looks like I was only half remembering the situation. The file you're referring to should have that license, and the Chapel project in general used to use BSD, but that was before this repo got its license file. Anyways, thank you for the catch, this looks good to me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that we are using an SPDX expression for the license metadata, we can account for the BSD-2-Clause license
(
sphinxcontrib/chapeldomain/LICENSE) ofchapel.py.See https://peps.python.org/pep-0639/#spdx-license-expression-syntax.
We can also list the applicable license file so that it is included in the
.dist-infometadata.