docs: align README license section with the committed LICENSE file (AGPL-3.0) - #43
Open
danilaverbena wants to merge 1 commit into
Open
Conversation
The README's License section states Apache License 2.0, but the committed LICENSE file is the GNU Affero General Public License v3.0 (AGPL-3.0). This updates the README text to match the actual LICENSE file so the documentation reflects the license that legally applies. The LICENSE file itself is unchanged. If Apache-2.0 was the intended license, the LICENSE file should be updated instead (maintainer decision).
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
1 participant
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.
Problem
There is a mismatch between the stated license in two places:
README.md(License section): "This project is licensed under the Apache License 2.0"LICENSEfile: GNU Affero General Public License v3.0 (AGPL-3.0)License is legally significant, and the two documents currently disagree. Users, package tooling, and GitHub's license detection all key off the
LICENSEfile, so the README text is the one that's out of sync with the license that actually applies.Change
This PR updates only the README wording to match the committed
LICENSEfile:The
LICENSEfile itself is not modified — this only fixes the documentation so it reflects reality, without changing anyone's rights.I went with the direction that doesn't change the legally operative document (the
LICENSEfile). If the project actually intends to be Apache-2.0, then the correct fix is the opposite — replace theLICENSEfile with the Apache-2.0 text — and this PR should be closed in favor of that. Either way the two should be reconciled; happy to adjust this PR to whichever direction you prefer.Docs-only; no code changes.