allow Unicode-3.0 license #46
Merged
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
Signed-off-by: Ruihang Xia <[email protected]>
There was a problem hiding this comment.
Pull Request Overview
This PR updates the licensing configuration by allowing the Unicode-3.0 license and removing the now-unused Unicode-DFS-2016 exception.
- Added "Unicode-3.0" to the allow list.
- Removed the exceptions block containing "Unicode-DFS-2016".
progval
approved these changes
Mar 13, 2025
alamb
approved these changes
Mar 13, 2025
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.
According to "ASF 3rd Party License Policy Category A: What can we include in an ASF Project", The UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE is allowed to be included. And
Unicode-3.0is one of those from the link. Screenshots below:I also removed
Unicode-DFS-2016because it doesn't occur.