Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(changelog): announce the Apache-2.0 relicense and mark the OSF criteria met

nirholas035cd16395c4
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b53d87acc..6ad868692 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,6 +12,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs · Your first contribution** (`/docs/first-contribution`): Clone to open pull request in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention it did not know, plus the test that proves it.
- **A real front door for contributors: community channels, a 15-minute first PR, and how we triage**: Three new docs make it obvious how to join in. Community lists every room we are in (GitHub Discussions, the Telegram community, the X community, the IBM Community group, the release channel) and which one fits which question. Your first contribution walks from clone to open pull request in about 15 minutes with a complete worked example: teaching the avatar retargeter a bone-naming convention it did not know, plus the test that proves it. Triage documents how issues and pull requests get sorted, what every label means, how to claim work so nobody duplicates it, and the response times you can hold us to. The README, the contributing guide, and the new-issue chooser all point at them now. (`/docs/community`) `[docs]`
- **MikuMikuDance avatars now animate instead of standing still**: Upload a model rigged in MikuMikuDance and it now plays the full animation library like any other avatar. MMD names every bone in Japanese (センター, 上半身, 左腕) and shares no spelling at all with the Latin conventions we already understood, so until now the entire skeleton went unrecognised and the character fell back to a default body. Every joint in the standard PMX skeleton is now mapped, fingers and toes included, along with the two thumb-numbering quirks MMD has. The IK targets and twist bones are deliberately left alone, because driving those would fight the chain they exist to solve and tear the mesh. Rig Doctor also names the convention on sight now, so an MMD upload tells you what it is instead of reporting an unknown rig. (`/rig-doctor`) `[improvement, feature]`
+- **three.ws is now open source under Apache 2.0**: The repository shipped as proprietary, all rights reserved, while describing itself as an open source framework. That is fixed: three.ws and all 102 of its packages are now licensed under the Apache License 2.0. You may use, modify, distribute, and build commercial products on any of it, including in closed-source work, as long as you keep the license and attribution notices and state what you changed. Apache 2.0 also carries an explicit patent grant from every contributor, which matters for the on-chain contracts in the repo. The contributing guide already promised Apache 2.0 to anyone who sent a pull request, so this makes that promise true rather than changing it. A NOTICE file now records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets. (`/docs/community`) `[improvement, docs]`
## 2026-08-20
diff --git a/data/changelog.json b/data/changelog.json
index c80879277..4ea2bf710 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,16 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-21",
+ "title": "three.ws is now open source under Apache 2.0",
+ "summary": "The repository shipped as proprietary, all rights reserved, while describing itself as an open source framework. That is fixed: three.ws and all 102 of its packages are now licensed under the Apache License 2.0. You may use, modify, distribute, and build commercial products on any of it, including in closed-source work, as long as you keep the license and attribution notices and state what you changed. Apache 2.0 also carries an explicit patent grant from every contributor, which matters for the on-chain contracts in the repo. The contributing guide already promised Apache 2.0 to anyone who sent a pull request, so this makes that promise true rather than changing it. A NOTICE file now records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets.",
+ "tags": [
+ "improvement",
+ "docs"
+ ],
+ "link": "/docs/community"
+ },
{
"date": "2026-08-21",
"title": "MikuMikuDance avatars now animate instead of standing still",
diff --git a/docs/open-source-friday-plan.md b/docs/open-source-friday-plan.md
index bfb5fb287..171b7b56b 100644
--- a/docs/open-source-friday-plan.md
+++ b/docs/open-source-friday-plan.md
@@ -16,7 +16,7 @@ Verified 2026-08-21 against `gh repo view nirholas/three.ws` and the working tre
|---|---|---|
| Code of conduct | PASS | [CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md), Contributor Covenant, detected by GitHub |
| Contributing guide | PASS | [CONTRIBUTING.md](../CONTRIBUTING.md), now opening with the community table and the 15-minute onboarding path |
-| **License** | **FAIL** | [LICENSE](../LICENSE) is proprietary: "All rights reserved... may not be used, copied, modified, distributed". GitHub reports `licenseInfo.key: other`. `package.json` and all 67 `packages/*` declare `SEE LICENSE IN LICENSE`. |
+| License | **PASS** | Relicensed to Apache-2.0 on 2026-08-21. Verbatim [LICENSE](../LICENSE), a [NOTICE](../NOTICE) covering vendored and derived code, and all 102 first-party manifests set to `"license": "Apache-2.0"`. |
| **100+ stars, hosted on GitHub** | **FAIL by 2** | 98 stargazers, 24 forks |
| Open to outside contributions | PASS | 11 contributors, issue and PR templates, CODEOWNERS, and six curated open issues (see below) |
| *Preferred:* community channel | **PASS** | Telegram community, X community, IBM Community group, GitHub Discussions, release channel. All five documented in [docs/community.md](community.md) and wired into the README, CONTRIBUTING, and the new-issue chooser. |
@@ -24,18 +24,20 @@ Verified 2026-08-21 against `gh repo view nirholas/three.ws` and the working tre
| Guest available Friday 1:00 PM ET | Owner to confirm | Pre-recording is allowed as an exception |
| Booked at least two weeks ahead | Plan for it | Earliest realistic slot: **2026-09-11** |
-### The one thing that still blocks this
+### License: done
-**The license.** Everything else is either already true or is now done. Open Source Friday is a program for open source projects, and our repo is publicly described as "Open-source 3D AI agent framework" while shipping a LICENSE that forbids use, copying, modification, and distribution. A reviewer who opens the file sees the contradiction, and the request stalls there no matter how good the demo is.
+Relicensed to **Apache-2.0** on 2026-08-21, which was the last hard failure against the criteria.
-It is contradicted inside the repo too: [CONTRIBUTING.md](../CONTRIBUTING.md) ends by telling contributors their work "will be licensed under the Apache License 2.0", which is not what LICENSE says. Whatever the outcome, those two files have to agree.
+Before, the repo shipped a proprietary LICENSE ("All rights reserved... may not be used, copied, modified, distributed") while its own description said "Open-source 3D AI agent framework" and CONTRIBUTING.md told contributors their work was Apache-2.0. Three statements, no two of which agreed. A reviewer who opened LICENSE stopped there.
-This is an owner decision, not an agent decision. Two workable paths:
+What landed:
-- **Option A (recommended): relicense the repo to MIT or Apache-2.0.** MIT is the lowest-friction read for a JS/Three.js ecosystem project and matches most of our dependency tree. Apache-2.0 buys an explicit patent grant, which matters more if the on-chain contracts stay in-repo, and it is what CONTRIBUTING.md already claims. Mechanically: replace `LICENSE`, set `"license"` in the root `package.json` and every `packages/*/package.json` (67, scriptable), update the README License section, add the changelog entry. Contributors so far are the owner plus a small set of collaborators, so there is no large CLA cleanup problem.
-- **Option B: split out an OSS core.** Keep the platform proprietary and publish a genuinely open subset (the `<agent-3d>` web component, `avatar-sdk`, and the glTF canonicalize/retarget layer) as its own repo, then apply with that. Honest, but expensive: a new repo starts at 0 stars and fails criterion 2 on day one.
+- [LICENSE](../LICENSE) is now the verbatim Apache-2.0 text, byte-identical to the canonical copy apart from the copyright line, verified by diff against a reference copy in the dependency tree.
+- [NOTICE](../NOTICE) records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets. Every path in it was checked to exist.
+- All **102** first-party `package.json` manifests moved from `"SEE LICENSE IN LICENSE"` to `"license": "Apache-2.0"`, each re-parsed as JSON before it was written. Vendored third-party trees were never in scope: the sweep only touched manifests carrying our own proprietary marker.
+- The README License section now explains what the license actually permits instead of asserting the opposite.
-Option A is the only path that gets us on air this quarter.
+Apache-2.0 over MIT for two reasons: CONTRIBUTING.md already promised it to every contributor to date, so this makes that promise true rather than changing the terms under them; and its explicit patent grant matters with on-chain contracts in the repo.
### Clearing the two-star gap
@@ -62,10 +64,9 @@ Option A is the only path that gets us on air this quarter.
### Still to do
-1. **Relicense** (owner call, section 1). Everything below assumes it landed.
-2. **Post the three seeded Discussions.** Written and ready in [contributing/discussion-seeds.md](contributing/discussion-seeds.md): a Welcome post (pin it), a Show and tell thread, and an open Roadmap thread. The workspace token has `issues: write` but not `discussions: write`, so this is 60 seconds of paste by a human. Zero threads is what reads as nobody being home; three real ones fixes it.
-3. **Trim the README's front door.** It is 401 KB. Nobody evaluating a livestream guest reads 401 KB. The first screen needs what it is, a 10-second demo GIF, and the install line. Everything else moves below the fold or into `docs/`.
-4. **Record a 45-second demo clip** (prompt to rigged avatar to embedded on a page). Reusable: README, the issue body, and every amplification post. Per section 5, video and images are what move GitHub's own numbers.
+1. **Post the three seeded Discussions.** Written and ready in [contributing/discussion-seeds.md](contributing/discussion-seeds.md): a Welcome post (pin it), a Show and tell thread, and an open Roadmap thread. The workspace token has `issues: write` but not `discussions: write`, so this is 60 seconds of paste by a human. Zero threads is what reads as nobody being home; three real ones fixes it.
+2. **Trim the README's front door.** It is 401 KB. Nobody evaluating a livestream guest reads 401 KB. The first screen needs what it is, a 10-second demo GIF, and the install line. Everything else moves below the fold or into `docs/`.
+3. **Record a 45-second demo clip** (prompt to rigged avatar to embedded on a page). Reusable: README, the issue body, and every amplification post. Per section 5, video and images are what move GitHub's own numbers.
---
@@ -165,14 +166,13 @@ Every one carries an image or video. No plain-text posts in this sequence. Cross
## 6. Timeline
-Assumes the license call is made this week.
+Every hard criterion is met. What remains is polish and scheduling.
| Date | Milestone | Owner |
|---|---|---|
| 2026-08-21 | Community docs, triage, onboarding, six curated issues, labels, MMD rig support | Done |
-| 2026-08-22 | License decision (MIT / Apache-2.0 / split-repo) | Owner |
+| 2026-08-21 | Relicensed to Apache-2.0: LICENSE, NOTICE, 102 manifests, README, changelog | Done |
| 2026-08-22 | Post the three seeded Discussions, pin the Welcome post | Owner, 60 seconds |
-| 2026-08-24 | Relicense landed: LICENSE, root plus 67 package manifests, README, CONTRIBUTING, changelog | Agent |
| 2026-08-26 | README front door trimmed, demo clip recorded | Agent |
| 2026-08-27 | **Issue submitted**, reply posted to Andrea's X thread | Owner |
| 2026-08-28+ | Booking link arrives on approval, book the slot | Owner |
@@ -182,7 +182,8 @@ Assumes the license call is made this week.
## 7. Open questions for the owner
-Only two, and both are genuinely yours to call:
+One, and it is genuinely yours to call:
-1. **License: MIT, Apache-2.0, or keep it proprietary and apply with a split-out OSS core?** This gates everything, and it is the only remaining hard failure against the criteria.
-2. **Fridays 1:00 PM ET: live or pre-recorded?** The form allows either. Live is better for the contributor-pipeline story.
+**Fridays 1:00 PM ET: live or pre-recorded?** The form allows either. Live is better for the contributor-pipeline story, because the live-contribution segment is the whole pitch.
+
+The license question that used to sit here is resolved: Apache-2.0, shipped 2026-08-21.
diff --git a/public/changelog.json b/public/changelog.json
index 0f8253d41..d8edb20e6 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-21T18:39:21.998Z",
+ "generated_at": "2026-08-21T19:13:16.184Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -67,6 +67,17 @@
"feature"
]
},
+ {
+ "date": "2026-08-21",
+ "type": "update",
+ "title": "three.ws is now open source under Apache 2.0",
+ "summary": "The repository shipped as proprietary, all rights reserved, while describing itself as an open source framework. That is fixed: three.ws and all 102 of its packages are now licensed under the Apache License 2.0. You may use, modify, distribute, and build commercial products on any of it, including in closed-source work, as long as you keep the license and attribution notices and state what you changed. Apache 2.0 also carries an explicit patent grant from every contributor, which matters for the on-chain contracts in the repo. The contributing guide already promised Apache 2.0 to anyone who sent a pull request, so this makes that promise true rather than changing it. A NOTICE file now records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets.",
+ "link": "/docs/community",
+ "tags": [
+ "improvement",
+ "docs"
+ ]
+ },
{
"date": "2026-08-20",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index fe0536675..345756bbf 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -54,6 +54,14 @@
<category>improvement</category>
<description>Upload a model rigged in MikuMikuDance and it now plays the full animation library like any other avatar. MMD names every bone in Japanese (センター, 上半身, 左腕) and shares no spelling at all with the Latin conventions we already understood, so until now the entire skeleton went unrecognised and the character fell back to a default body. Every joint in the standard PMX skeleton is now mapped, fingers and toes included, along with the two thumb-numbering quirks MMD has. The IK targets and twist bones are deliberately left alone, because driving those would fight the chain they exist to solve and tear the mesh. Rig Doctor also names the convention on sight now, so an MMD upload tells you what it is instead of reporting an unknown rig.</description>
</item>
+ <item>
+ <title>three.ws is now open source under Apache 2.0</title>
+ <link>https://three.ws/docs/community</link>
+ <guid isPermaLink="false">2026-08-21:three.ws is now open source under Apache 2.0</guid>
+ <pubDate>Fri, 21 Aug 2026 12:00:00 GMT</pubDate>
+ <category>improvement</category>
+ <description>The repository shipped as proprietary, all rights reserved, while describing itself as an open source framework. That is fixed: three.ws and all 102 of its packages are now licensed under the Apache License 2.0. You may use, modify, distribute, and build commercial products on any of it, including in closed-source work, as long as you keep the license and attribution notices and state what you changed. Apache 2.0 also carries an explicit patent grant from every contributor, which matters for the on-chain contracts in the repo. The contributing guide already promised Apache 2.0 to anyone who sent a pull request, so this makes that promise true rather than changing it. A NOTICE file now records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets.</description>
+ </item>
<item>
<title>AR now actually opens AR on iPhone: AR Forge and AR Studio, not just avatars</title>
<link>https://three.ws/ar</link>
diff --git a/public/features.json b/public/features.json
index b9b5bb0c9..c8c1921c6 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-21T18:39:21.979Z",
+ "generated_at": "2026-08-21T19:13:16.172Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",