docs: align README license to GPL-3.0-or-later#412
Open
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
Open
docs: align README license to GPL-3.0-or-later#412shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
Conversation
The repository declares GPL-3.0-or-later in both legally-binding locations (the LICENSE file at the repository root and package.json line 20), while README.md and README.zh-CN.md advertise MIT in the shields badge and the License section. npm consumers, SPDX scanners, and GitHub's dependency graph record the package as GPL-3.0 because they read package.json; human readers see MIT. This PR aligns the README to the authoritative declaration (the LICENSE file). The badge target is updated to https://www.gnu.org/licenses/gpl-3.0, and the License section quotes the same SPDX identifier used in package.json. If MIT is actually the intended license, the direction of this PR should be reversed — the LICENSE file and package.json would change, not the README. Aligning to the LICENSE file is the safe default because that is the legally binding source for redistribution. Closes EvoMap#407
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
The license is declared four times and the declarations do not agree:
README.md:4(shields badge)README.md:428(Section "License")README.zh-CN.md:4README.zh-CN.md:424package.json:20\"license\": \"GPL-3.0-or-later\"LICENSESee #407 for the full rationale.
Fix
This PR aligns the four README locations to the authoritative
declaration already present in the LICENSE file and
package.json.https://www.gnu.org/licenses/gpl-3.0.GPL-3.0-or-later.Why this direction
Three signals point to GPL-3.0 as the intended license:
the full GPL-3.0 text, not an MIT text.
package.json:20uses the SPDX identifierGPL-3.0-or-later, which is what npm, SPDX scanners, and GitHub'sdependency graph record.
src/gep/*.js) imply that thepublisher is exercising GPL-3.0 §6 terms for object-code
distribution; that is not a posture the MIT license contemplates.
If MIT is actually the intended license, the direction should be
reversed: LICENSE and package.json would change instead. Aligning the
README to the LICENSE file is the safer default — the README is
documentation, the LICENSE file is the contract with redistributors.
Testing
Markdown only. No runtime behaviour change.
Scope
Two files, +4/−4 lines.
Closes #407.