Repository navigation
docs: relicense from GPL-3.0 to AGPL-3.0 - #93
Merged
Merged
Conversation
en0f
previously approved these changes
Oct 13, 2026
liquidsec
previously approved these changes
Oct 19, 2026
liquidsec
dismissed stale reviews from en0f and themself
October 19, 2026 19:39
The base branch was changed.
`radixtarget` is a Black Lantern original, so this is the copyright holder relicensing its own work. The notices carry `either version 3 of the License, or (at your option) any later version`, and GPLv3 section 13 already permits AGPLv3 interoperation, so making the AGPL grant explicit needs no contributor sign-off. The file is the same AGPL-3.0 text `bbot` carries. The manifest moves in the same commit. A tree that ships an AGPL-3.0 file next to a manifest naming something else is self-contradictory at the point a packager reads it: `Cargo.toml`, `pyproject.toml`. Refs #151
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #93 +/- ##
===================================
Coverage 100% 100%
===================================
Files 3 3
Lines 604 605 +1
===================================
+ Hits 604 605 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
liquidsec
force-pushed
the
license-agpl
branch
from
October 19, 2026 19:41
ea0cf93 to
55130d4
Compare
liquidsec
approved these changes
Oct 19, 2026
This was referenced Oct 19, 2026
Merged
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
4 participants
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
LICENSEmoves from GPL-3.0 to AGPL-3.0.Cargo.toml,pyproject.tomlmoves with it, in the same commit.Why
Every Black Lantern original carries AGPL-3.0. This repository is an original,
not a fork, so this is the copyright holder relicensing its own work. The
notices carry
either version 3 of the License, or (at your option) any later version, and GPLv3 section 13 already permits AGPLv3 interoperation, so makingthe AGPL grant explicit needs no contributor sign-off.
Manifest
A tree that ships an AGPL-3.0 file next to a manifest naming something else is
self-contradictory at the point a packager reads it, so both edits belong in
one commit rather than a follow-up.
Validation
LICENSEfirst line readsGNU AFFERO GENERAL PUBLIC LICENSEtomllibRefs #151