Add canonical AGPL-3.0 license text so GitHub detects it - #24
Merged
Merged
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.
What
Replace the truncated AGPL-3.0 notice in
LICENSEwith the full canonical GNU Affero General Public License v3.0 text (the standard 661-line document).Why
The repository is public but GitHub's license detector reports the license as "Other" because the existing
LICENSEwas only a short summary/notice, not the verbatim license document Licensee-detection requires. Shipping the canonical text lets GitHub correctly identify the project as AGPL-3.0, so the license badge, the repo sidebar, and the API all report the real terms and visitors immediately know the terms of use.Notes
LICENSEfile changes; the canonical AGPL-3.0 body is used verbatim (Version 3, 19 November 2007) with no project-specific edits inside the license text.