chore(license): relicense from MIT to AGPL-3.0-or-later#86
Merged
Conversation
Aligns with the broader anti-censorship FOSS ecosystem (Hiddify, Marzban, Outline, AmneziaVPN, sing-box are all AGPL-3.0). The network-use clause closes the SaaS-clone vector that MIT left fully open while keeping the project welcoming to community contributions. Pre-relicense SHA: f944cef Code at or before f944cef remains available under the MIT License per its original release. From this commit forward, AGPL-3.0-or-later. Past copyright holders consented to the relicense: * findias (project lead, 254 commits, original author) * Jochan Conrad <johanconrad@atomicmail.io> — 3 commits, 115 surviving lines, all in CI workflow files (.github/workflows/test.yml + .github/actions/setup-go-env/). Consent recorded as AlchemyLink/Raven-server-install#38 (comment) ("Yes, OK to relicense", 2026-05-06). dependabot[bot] commits are excluded as automated dependency bumps do not generate copyright. Adds: * LICENSE replaced with the canonical AGPL-3.0 text from gnu.org/licenses/agpl-3.0.txt (sha256 0d96a4ff68ad6d4b6f1f30f713b18d5184912ba8dd389f86aa7710db079abcb0). * README.md and README.ru.md badge + License section updated. * CONTRIBUTING.md gains a top-level "License and Developer Certificate of Origin" section with the DCO v1.1 sign-off requirement for future contributions; the existing Quality Gate + Lint Policy + nolint Rules + Security Notes sections are preserved unchanged. Signed-off-by: findias <findias@gmail.com>
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.
Why
Aligns with the broader anti-censorship FOSS ecosystem (Hiddify, Marzban, Outline, AmneziaVPN, sing-box are all AGPL-3.0). AGPL's network-use clause closes the SaaS-clone vector that MIT left fully open while keeping the project welcoming to community contributions.
This is the final piece of the org-wide AGPL-3.0 relicense:
raven-dashboardv1.7.0 — Phase 1, donexray-stats-exporterv1.0.3 — Phase 1, doneRaven-server-install— Phase 2, PR #40Raven-subscribe— Phase 2, this PRWhat this means for you
f944cef5afe32e4519825e630d4ab00cf2be8d27remains available under the MIT License per its original release. From this PR forward, AGPL-3.0-or-later.Consent and authorship
Past copyright holders consented to the relicense:
findias(project lead, 254 commits, original author)@johanconrad— 3 commits, 115 surviving lines (all in.github/workflows/test.yml+.github/actions/setup-go-env/action.yml). Consent recorded at Relicensing AlchemyLink repos to AGPL-3.0-or-later — request your consent for past contributions Raven-server-install#38: "Yes, OK to relicense" on 2026-05-06.dependabot[bot]commits are excluded as automated dependency bumps do not generate copyright.Changes
0d96a4ff68ad...).Test plan
gnu.org/licenses/agpl-3.0.txtbyte-for-byte (verified via sha256).Tagging
Suggest tagging
v0.2.0on merge — minor bump for license change (last release wasv0.1.8). Cross-repo audit trail lands in the release notes.