chore!: relicense from MIT to GPL-3.0-or-later - #220
Merged
Conversation
Re-land of #219. That PR was stacked on #218, and #218 squash-merged to main first, so its squash captured only the README commit — #219 then merged into the docs branch and never reached main. Same tree, verified byte-identical to the merged docs/readme-refresh branch. MIT let anyone ship a closed-source fork. The intent is that derivative works stay open, so the project moves to the GPL. Attribution was never the missing piece — MIT already required the copyright notice to be kept — the copyleft is. Sole authorship makes this possible: every non-bot commit in the history is mine, so there are no contributors whose consent is needed. - LICENSE: the GPL-3.0 text, verbatim from gnu.org. The repo previously claimed MIT in Cargo.toml and the README without ever shipping a licence file, so this is also the first real grant. - src-tauri/Cargo.toml, package.json: license metadata, plus the author and repository fields, which were still Tauri template placeholders ("you", empty string). - README, NOTICE.md: state the licence, keep the icon's separate CC BY-SA 3.0 terms, and note that v0.1.61 and earlier remain MIT — relicensing is not retroactive. Dependencies are all GPL-3 compatible (MIT / Apache-2.0 / ISC / BSD / MPL-2.0, and MIT for the llama.cpp and whisper.cpp sidecars). Apache-2.0 is why this is v3 and not v2. Code signing is unaffected: GPLv3's Installation Information clause applies to User Products, not to a desktop app, so Developer ID and Authenticode signing remain available. The Mac App Store does not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01REbcwnYDg6DFC4cPASbAMG
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.
Re-land of #219, which never reached
main.What happened
#219 was stacked on #218. #218 squash-merged to
mainfirst, so its squash captured only the README commit. #219 then merged intodocs/readme-refresh— a branch that was already merged and no longer headed anywhere. The license work ended up stranded there.My fault: stacking was the right call to avoid a README conflict, but it only works if the base PR merges last. I should have flagged the merge order.
This PR
The same commit, cherry-picked onto
main. The tree is byte-identical to the mergeddocs/readme-refreshbranch (git diff origin/docs/readme-refresh HEADis empty), so nothing was lost or changed in the move.LICENSEsha256 3972dc97…), 674 linessrc-tauri/Cargo.tomllicense = "GPL-3.0-or-later";authorsandrepositoryfilled in — they were still Tauri placeholders ("you","")package.jsonlicense,author,repositoryREADME.mdNOTICE.mdVerified after the cherry-pick: both manifests parse,
cargo metadatareportsGPL-3.0-or-later, prettier passes.After merging
docs/readme-refreshstill holds the orphaned copy of this commit. Once this lands, that branch is fully redundant and safe to delete — I left it alone rather than deleting a remote branch on your behalf.Heads up: this is marked
chore!, so release-please will treat it as breaking. The open release PR #217 (0.1.62) will likely re-cut as 0.2.0. That's correct for a licence change, but worth knowing before you merge.🤖 Generated with Claude Code
https://claude.ai/code/session_01REbcwnYDg6DFC4cPASbAMG