chore(license): relicense from MIT to AGPL-3.0-or-later#207
Open
parth0025 wants to merge 1 commit into
Open
Conversation
- Replace LICENSE with canonical AGPL-3.0 text (660 lines, includes Β§13 SaaS clause) - Add COPYRIGHT file with Alian Software notice (2025-2026) - Fix package.json (ISC -> AGPL-3.0-or-later) and frontend manifest (license field was missing) - Update README badge, license section, and all doc references - Add commercial-license contact for enterprises needing alternative terms Aligns the repo with Plane's open-source PMS licensing model and protects against SaaS competitors rebranding the code under closed licenses. Permitted while contributor base is small (Alian Software employees only). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the βοΈ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
β¨ Finishing Touchesπ§ͺ Generate unit tests (beta)
Comment |
This was referenced Jun 8, 2026
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.
Summary
Relicenses AlianHub from MIT to AGPL-3.0-or-later, aligning with the licensing model used by similar open-source project management systems (e.g., Plane).
Why now: while the contributor base is small (Alian Software employees only), relicensing is straightforward. Once external contributors join, every contributor must consent to a license change, which is operationally hard at scale.
Why AGPL-3.0: protects against SaaS competitors rebranding AlianHub's code under closed licenses while keeping the project fully free and open for self-hosters. Enables future dual-licensing for enterprises that cannot use copyleft.
Files changed (9)
LICENSECOPYRIGHT(new)package.json"ISC"β"AGPL-3.0-or-later"+ author fieldfrontend/package.jsonlicensefield added (was missing) + author fieldREADME.mdREADME_DOC.mdCLAUDE.md.claude/FOLDER-STRUCTURE.md.claude/REFERENCES.mdWhat AGPL-3.0 means in practice
Test plan
npm installruns without license-related warnings (root andfrontend/)package.jsonandfrontend/package.jsonparse as valid JSONgrep -nE "MIT [Ll]icens|License-MIT|MIT-green")Notes for reviewers
LICENSE.txt(md547f46ca0044567a2cfb013881642454c).AGPL-3.0-or-laterchosen over the deprecatedAGPL-3.0for SPDX-modern compliance and future flexibility.Rollout
Step 1 of the open-source repo maintenance baseline initiative. Next steps (separate PRs): branching strategy, PR/branch name formats, release process, package publishing, README polish, discoverability.
π€ Generated with Claude Code