license: relicense to Apache-2.0 (full open source) - #59
Merged
Merged
Conversation
…or legal review) - LICENSE: replace proprietary source-available text with verbatim GNU AGPL v3.0. - Add LICENSING.md (dual-license overview + how to choose). - Add COMMERCIAL-LICENSE.md (commercial terms template; governed by Washington State law). - Add CLA.md (contributor license agreement enabling dual-licensing; WA law). - README: AGPL badge + 'commercial available' badge, dual-license notice, updated Security-and-license section. - CHANGELOG: note the relicense under Unreleased. All license docs are clearly marked as drafts pending the copyright holder's legal review; only the copyright holder (sole rights holder) can relicense.
X4Applegate
force-pushed
the
dual-license-agpl
branch
from
September 18, 2026 01:18
0c704d3 to
66c99b9
Compare
Per the author's intent to give back to the community with no monetization, license under the permissive Apache License 2.0 instead of AGPL + commercial. - LICENSE: Apache-2.0 (copyright 2026 Richard Applegate). - Add NOTICE. - Remove COMMERCIAL-LICENSE.md, CLA.md, LICENSING.md (dual-license machinery no longer needed). - README + CHANGELOG: Apache-2.0 open-source notice.
X4Applegate
changed the title
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.
Implements the dual-license proposal so the project can reach the biggest open-source / self-hosted channels (incl.
awesome-selfhosted) while retaining commercial rights. Since you are the sole copyright holder, you can relicense.Changes
LICENSE→ replaced the proprietary source-available text with the verbatim GNU AGPL v3.0 (OSI-approved).LICENSING.md— plain-language overview: AGPL by default (free to self-host/modify under its terms) or a commercial license for closed-source / SaaS use without source disclosure.COMMERCIAL-LICENSE.md— commercial-license template; governing law = State of Washington, USA, WA state/federal court venue, CISG excluded (county left for your lawyer to specify).CLA.md— Contributor License Agreement granting you the right to relicense contributions (required to keep dual-licensing viable); WA-law governed.README.md— AGPL badge + "commercial available" badge, dual-license notice, updated Security-and-license section.CHANGELOG.md— relicense noted under Unreleased.Why AGPL + commercial
awesome-selfhostedand the FOSS crowd (the biggest star drivers in this niche).Before merging
COMMERCIAL-LICENSE.md+CLA.md(fill county/venue, fees, warranty/liability).backend/*.js(optional; can be a follow-up).No code/runtime changes — docs and license only.