Repository navigation
Publish commercial licensing terms and permission status - #2180
Conversation
|
@kramlipi — thank you for your contribution to Mu. We're requesting your explicit permission to relicense your SQLite test-teardown contribution credited in commit 8300b24 (whose message references #1456; that PR is currently unavailable through GitHub), including the portions retained or modified in later Mu versions. The proposal is in #2180: future Mu runtime releases would be source-available, free for personal/internal use, with a paid licence required for commercial resale or hosting. Micro would also offer separate proprietary commercial licences. MUCP and the SDKs remain permissively licensed. Existing AGPL grants would remain valid. If you agree, please reply with the following confirmation (identifying the rights-holding entity if you are acting for one):
This request concerns only the identified contribution, not future contributions. Attribution will be preserved. If any portion belongs to an employer, co-author or another party and you cannot grant permission for it, please identify that limitation instead. If you would prefer a separate agreement or do not agree, please say so; silence will not be treated as consent. For reference, the current draft is Mu Runtime Licence draft 1.0. |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Publish US$10,000/month commercial terms separately from US$1,000/month support, including a versioned customer agreement and contributor permission status. The proposed source-available runtime licence remains inactive until the necessary rights are confirmed; current AGPL and Apache licences remain authoritative.
Per maintainer instruction, external legal review is not a merge prerequisite. No such review is claimed. The existing merged CLA and contribution process are preserved. Dev9269's scoped permission is recorded; other historical permissions remain pending.
Validation: documentation link checks, git diff --check and the existing proto licence-notice test passed. Documentation only; no runtime or effective licence change. Maintainer explicitly directed merging; no personal CLA acceptance has been fabricated.