chore(license): unify framework repo to single Apache-2.0#2353
Merged
Conversation
The repo was in a half-finished, self-contradictory BSL transition: 44 package
LICENSE files carried Business Source License 1.1 text while their package.json
already declared "license": "Apache-2.0", and a redundant root LICENSE.apache
lingered from the transition.
The framework is deliberately permissive Apache-2.0 to maximize adoption; value
capture lives in the separate closed-source cloud repo. This makes that
unambiguous:
- Replace all 44 BSL package LICENSE files with the canonical root Apache-2.0
text.
- Remove the redundant root LICENSE.apache (single canonical LICENSE at root).
- LICENSING.md already states the whole repo is Apache-2.0 (no change needed).
- All package.json license fields already Apache-2.0 (verified).
No BSL residue ("Business Source", "BUSL", "MariaDB", "Additional Use Grant",
"Change Date", "competitive offering") remains anywhere outside node_modules.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
Contributor
📓 Docs Drift CheckThis PR changes 29 package(s): 51 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
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.
Summary
The repo was in a half-finished, self-contradictory source-available transition. This unifies the entire repository to a single, consistent Apache License 2.0.
The framework is deliberately permissive Apache-2.0 to maximize adoption (goal: the de-facto standard for AI-built metadata apps). Value capture lives in the separate closed-source cloud repo, not here — so all restrictive licensing is reverted to Apache-2.0.
What changed (46 files)
LICENSEfiles — replaced restrictive dual-license text with the canonical root Apache-2.0 text (copied from rootLICENSE, byte-identical). Spannedcore,rest,runtime,objectql,metadata*,mcp, and allconnectors/*,plugins/*,services/*.LICENSE.apache— deleted (redundant duplicate of rootLICENSE); single canonicalLICENSEremains at root..changeset/unify-apache-license.md— added; single@objectstack/core: patchentry, which via thefixedgroup republishes all affected packages with the correctedLICENSE.Already correct (verified, no change needed)
package.jsonalready declared"license": "Apache-2.0".LICENSING.mdalready states the whole repo is Apache-2.0, no dual-license language, no dangling restricted-package list.LICENSEwas already clean Apache-2.0.Verification
Note: a whole-repo sweep also matches
MariaDBinservice-datasource/src/driver-catalog.ts— that's a legitimate'MySQL / MariaDB'DB-connection label, not license residue, left untouched.🤖 Generated with Claude Code