chore: relicense to Apache-2.0 - #1
Open
simontaurus wants to merge 1 commit into
Open
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
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.
Relicense from AGPL-3.0 to Apache-2.0.
Changes
LICENSE: full Apache License 2.0 textNOTICE: copyright and year range, per Apache section 4(d)extension.json:license-nameset toApache-2.0Rationale
Compatibility
A license scan of the full OSL stack (210 composer packages, 100 extensions and skins) found no GPL-2.0-only component. Every GPL-2.0 dependency is
or-later, so Apache-2.0 introduces no compatibility barrier.Consent
Sole-authored repository. No third-party contributor holds surviving lines, so no external consent is required.