docs(charter): replace CLA with DCO; plugin exception becomes the module-boundary mechanism (HT-21) - #19
Merged
Conversation
…ule-boundary mechanism (HT-21) Charter §3/§7 amendment. Contributions move from CLA/consolidated copyright to DCO-only inbound — contributors keep their copyright. The consolidated-copyright rationale was incorrect: the plugin exception (AGPL-3.0 §7 additional permission), not core ownership, is what makes first-party commercial modules lawful. Consequences recorded in §3: dual-licensing the core is deliberately given up (worth little for an operator-run end application); the exception's counsel deadline moves from marketplace-open to before the first external contribution (under DCO its text cannot be broadened afterward without every contributor's consent); the exception is symmetric and travels with forks, so the name/marks, npm org, and marketplace are the commercial assets — trademark policy added to pre-launch counsel work. Resonant IQ is bound by the core's license like any licensee (AGPL §13 applies to its own hosted offerings). CONTRIBUTING.md: gating item changes from "CLA not finalized" to "exception text not counsel-final"; future requirement is a DCO sign-off only. CLAUDE.md: human-review rationale no longer cites dual-licensability. Basis: adversarial research pass 2026-07-10 (primary sources: vendor LICENSE/CONTRIBUTING files, FSF texts, GPLv3 §7 mechanics); findings summarized in HT-21 and the HT-5 rescope comment. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe documentation updates establish DCO-only contributions, revise the commercial plugin exception and governance status, adjust contribution timing guidance, and update Helpthread’s ownership and human-review wording. ChangesLicensing and governance
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 task
This was referenced Jul 19, 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.
What
Charter §3/§7 amendment (HT-21). Contributions move from CLA/consolidated-copyright to DCO-only inbound — contributors keep their copyright, permanently. The commercial-module model now rests where it always legally rested: on the plugin exception (AGPL-3.0 §7 additional permission), not on core ownership.
git commit -sand nothing else.Why
The old §3 claimed consolidated copyright "is what makes it lawful to also sell first-party commercial modules." That claim is wrong — verified 2026-07-10 against primary sources (vendor LICENSE/CONTRIBUTING files, FSF texts, §7 mechanics; e.g. Element's CLA exists solely to sell AGPL exceptions on its core). Meanwhile a single-vendor CLA is the exact trust signal the self-hosted audience screens against (HashiCorp 2023; Cal.com went fully closed via its CLA in April 2026). Exception-sale revenue is ~nil for an operator-run helpdesk, so the CLA's only real value was an option this project doesn't want to hold.
Full research basis and the counsel-work rescope are in HT-21 and the comment on HT-5.
Notes for review
🤖 Generated with Claude Code
Summary by CodeRabbit