Repository navigation
docs: state the Spine licence trigger in Credits the way core's NOTICE does - #6
Conversation
…E does Credits and licences said using rig-c's output in a product requires a Spine Editor licence, pointing at parts' Licence posture. That contradicted this guide's own On a web page section and rig-c/core's NOTICE: the terms turn on integrating a Spine Runtime. Quote the NOTICE instead and drop the pointer. Closes #5 Co-Authored-By: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
Codex Review SummaryThis 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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
HQ sign — the two quotes match core NOTICE at 352bb01 verbatim, the route split (web page / adapters: no Spine runtime, per their own sections at line ~221 and ~227; editor / official runtimes: their sections' terms) is read from the guide's own text, and the retired phrases are gone (grep exit 1). Merge. |
1 participant
Closes #5. This PR rewords Credits and licences only. Nothing else in the guide changes.
grep -n "Licence posture|as any Spine data" README.mdNOTICE.mdat origin/main352bb01word for word: what the terms turn on is the integration, and "If a product integrates a Spine Runtime to play rigc's output, that integration is subject to the terms above — rigc neither creates those terms nor removes them."The pointer to parts' Licence posture is gone; rig-c/parts#520 retires that wording.
🤖 Generated with Claude Code