Change license to gpl-2.0-or-later #62
Merged
+36
−36
Conversation
This file contains 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
TravisCarden
approved these changes
May 26, 2023
There was a problem hiding this comment.
Sorry, @danepowell, this got past me. I'm fine with this. I'm going to update the issue summary to indicate that this is also bumping some dependencies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our current license is gpl-2.0-only, which means that downstream projects must also be gpl-2.0 licensed (not gpl-3.0). This seems unnecessarily restrictive and out of line with other Acquia and Drupal projects.
This also bumps some dependencies: