chore: relicense MIT → PolyForm Noncommercial 1.0.0 (commercial reserved) - #28
Conversation
Switch the project license so noncommercial use is permitted while commercial use is reserved to the copyright holder (redsunjin), who can grant a separate commercial license. Kept minimal: LICENSE holds the authoritative text with a short header noting the commercial-use reservation, README swaps the (now inaccurate) MIT badge, and package.json declares "SEE LICENSE IN LICENSE". Note: this governs future versions; code already published under MIT keeps MIT rights for those snapshots. Third-party dependencies remain under their own (permissive) licenses. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 04d6a0d1f2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| (full text below). Noncommercial use is permitted; commercial use is not granted | ||
| by this license. A separate commercial license is available from the copyright | ||
| holder (redsunjin). |
There was a problem hiding this comment.
Match the stated prohibition to the license exceptions
For charitable organizations, educational institutions, public research organizations, and the other entities listed under “Noncommercial Organizations,” the terms below explicitly permit use regardless of funding or related obligations. The blanket statement here that commercial use is not granted therefore misstates the selected license for those users and does not implement the stated policy of requiring every commercial user to obtain a separate license; qualify this summary or select terms that actually impose that restriction.
Useful? React with 👍 / 👎.
| "name": "maestro-coding", | ||
| "private": true, | ||
| "version": "0.95.0", | ||
| "license": "SEE LICENSE IN LICENSE", |
There was a problem hiding this comment.
Give the relicensed release a new version
When consumers identify releases using the package version, this applies different license metadata to 0.95.0, even though repository history already designated that version as a release under MIT. That makes MIT and PolyForm snapshots share the same release identifier and undermines the commit's promise that only future versions are affected; bump the version as part of the relicensing change.
Useful? React with 👍 / 👎.
| "name": "maestro-coding", | ||
| "private": true, | ||
| "version": "0.95.0", | ||
| "license": "SEE LICENSE IN LICENSE", |
There was a problem hiding this comment.
Regenerate the lockfile after adding license metadata
The committed package-lock.json still omits packages[""]["license"], whereas npm-generated lockfiles mirror this root-package field. Tools that derive package or SBOM metadata from the lockfile will consequently report the application license as unspecified despite this manifest change, so the lockfile should be regenerated and committed with the new value.
Useful? React with 👍 / 👎.
목적
"참조·이용은 가능하지만 상업적 이용은 금지, 상업 라이선스는 소유자(redsunjin) 보유" 모델로 라이선스를 전환합니다. 공개 레포는 그대로 유지(source-available).
변경 (최소 footprint)
LICENSE: MIT → PolyForm Noncommercial 1.0.0 원문 + 상단 3줄(저작권 + 상업 유보 +Required Notice)README.md: 부정확한License: MIT배지 교정 + 눈에 안 띄는 HTML 주석 1줄(상업 라이선스 안내) — 별도 섹션 없음package.json:"license": "SEE LICENSE IN LICENSE"알아둘 점
🤖 Generated with Claude Code