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.
Open Source Friday: application and stream plan
Goal: get three.ws booked on GitHub's Open Source Friday livestream (Twitch/github, Fridays 1:00 PM ET) with Andrea Griffiths (@AndreaGriffiths11 / @acolombiadev), who invited us to open the request issue on 2026-08-21.
Program page: https://github.com/githubevents/open-source-friday Criteria: admin/project-criteria.md Request form: https://github.com/githubevents/open-source-friday/issues/new?template=osf-guest-invite.yml Our request: https://github.com/githubevents/open-source-friday/issues/254 (opened 2026-08-25) Contribution menu and booking reply: marketing/growth/events/open-source-friday-menu.md (approved; all six August issues are closed, so the menu carries seven new verified issue bodies)
1. Where we stand against the criteria
Verified against gh repo view nirholas/three.ws and the working tree, not from memory. Last re-checked 2026-08-25.
| Criterion | Status | Evidence |
|---|---|---|
| Code of conduct | PASS | CODE_OF_CONDUCT.md, Contributor Covenant, detected by GitHub |
| Contributing guide | PASS | CONTRIBUTING.md, now opening with the community table and the 15-minute onboarding path |
| License | PASS | Relicensed to Apache-2.0 on 2026-08-21. Verbatim LICENSE, a NOTICE covering vendored and derived code, and all 102 first-party manifests set to "license": "Apache-2.0". |
| 100+ stars, hosted on GitHub | PASS | 104 stargazers, 26 forks as of 2026-08-25 (98 on 2026-08-21; the relicense closed the gap without a campaign) |
| 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 (seeded 2026-08-25: Welcome #122, Show and tell #123, Roadmap #124), release channel. All five documented in docs/community.md and wired into the README, CONTRIBUTING, and the new-issue chooser. |
| Preferred: triage team / contributor onboarding | PASS | docs/triage.md (labels, claiming, published response targets) and docs/first-contribution.md (clone to PR in 15 minutes, worked example) |
| 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 |
License: done
Relicensed to Apache-2.0 on 2026-08-21, which was the last hard failure against the criteria.
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.
What landed:
- 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 records attribution for the vendored and derived code that keeps its own license: the forked avatar builder, 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.jsonmanifests 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.
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.
The star gap: closed
On 2026-08-21 the repo sat at 98. The call was to treat that as noise rather than run a campaign, because a suspicious star curve reads worse to a reviewer than being two short. Four days and one relicense later it is 104, with no asks made. Every hard criterion in the table above now holds.
2. Pre-flight work
Done on 2026-08-21
- Community channels documented and wired. docs/community.md lists all five rooms with guidance on which fits which question, plus the house rules. Linked from the README (new Community section, in the table of contents), CONTRIBUTING.md, and the GitHub new-issue chooser (
.github/ISSUE_TEMPLATE/config.yml). - Contributor onboarding written. docs/first-contribution.md goes clone to open PR in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention, the test that proves it, and the two mistakes that cost a review round.
- Triage documented. docs/triage.md publishes response targets (2 business days for a new issue or a first-time contributor's PR, 24 hours for a security advisory), what every label means, how to claim work, and how someone becomes a maintainer.
- Six curated issues opened, every one with a named file and a verification command:
- #110 Rig: Apple / ARKit
_joint-suffixed skeletons (verified: 0 of 10 joints map today) - #111 Rig: Kinect trailing-side bone names (verified: 0 of 10)
- #112 Rig: Reallusion CC3/CC4 numbered spine (verified gap)
- #113 Animation: bake a real
bowclip (the repo's own trackedknown_issue) - #114 Tests: drift guard between supported and documented rig conventions
- #115 Rig: teach the retargeter any convention it does not know (open-ended,
help wanted)
- #110 Rig: Apple / ARKit
- Labels added:
area: rig,area: animation,area: docs,area: tests,triage. - MMD rig support shipped, so the worked example in the onboarding doc points at real merged code rather than a hypothetical. MikuMikuDance names every bone in Japanese and mapped zero joints before; the full PMX skeleton now maps (fingers and toes included), Rig Doctor fingerprints the convention on sight, and the IK and twist bones are deliberately left unmapped. 471 tests pass across the two affected suites.
Still to do
- Pin the Welcome discussion. The three seed threads are live (#122, #123, #124). GitHub exposes no API for pinning, so #122 needs one click from the Discussions tab.
- The README front door is better than its file size suggests. 8,402 of its 11,372 lines are one inline STL model that GitHub renders as an interactive 3D viewer, so a reader on github.com sees a widget, not 8,000 lines of vertex data. The prose is about 3,000 lines. The first screen now carries the license and good-first-issue badges and a contributor CTA alongside the user one. What is still worth doing is a 10-second demo GIF above the fold, since the current hero is a video attachment that does not autoplay in every context.
- 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.
3. The issue: exact field-by-field content (submitted as #254)
The form (osf-guest-invite.yml) auto-titles as Open Source Friday - [PROJECT NAME] - [MM-DD-YYYY], labels open-source-friday, open-source, twitch, pending, and assigns @AndreaGriffiths11, @KevinCrosby, @marlenezw, @madebygps. A date is not required to submit: check "Not yet" and they send the booking link on approval.
Title: Open Source Friday - three.ws - 09-11-2026
Name: Nich (owner to confirm the name they want on air)
GitHub Handle: @nirholas
Tell us about yourself:
Double bachelors in Marketing and Computer Science from UW. Provided security research services to Apple, AT&T, Microsoft, Google, the U.S. Department of Defense, and the State of California government. Prior to three.ws I worked in full-stack development for some of the largest companies and brands. I am also an author and contributor at Entrepreneur Magazine.
I build three.ws, an open source framework for 3D AI agents on the web. Background is full-stack and real-time graphics; most of my work now sits at the seam between Three.js rendering and agent runtimes, which is a place where very little tooling existed until recently. I maintain the project day to day: triage, reviews, releases, and docs.
Project Name: three.ws
Project Repo Link: github.com/nirholas/three.ws
Stream Date: "Not yet" (unless the owner already booked at https://gh.io/osf-booking)
Dates: leave blank unless booked
Twitter URL: @nichxbt
LinkedIn URL: https://linkedin.com/in/nixholas
Topic and Additional Information: the live issue is the record: open-source-friday#254. It carries a named topic ("Give your AI a body. Any rig, any page, one tag."), the rig problem in one sentence, a six-part outline in their Streaming Guide's order with the live-PR segment as the centrepiece, verified project facts with today's date on them, six links a reviewer can check in a minute, and logistics that pre-answer their prep checklist. Re-benchmarked against every approved request of the last year in section 4b.
Follow-up: reply to Andrea's thread on X with the issue link once it is open. She asked for the issue; closing that loop publicly is the point.
4. Stream runsheet (30 to 45 min, live at 1:00 PM ET, join 12:45 for tech check)
This follows the order and length in their own Streaming Guide rather than inventing a format. The guide says the whole stream should not exceed 30 to 45 minutes and lists the questions the host will ask, so the plan is built around answering those with pixels.
| Time | Their segment | What we do |
|---|---|---|
| 0:00-0:05 | Introduce yourself | Bio in two sentences, then the one-line pitch: every agent on the web is a text box, this gives it a body |
| 0:05-0:08 | What is your project? | Prompt to rigged avatar to embedded on a blank page, narrated, no slides |
| 0:08-0:18 | Demo | (a) generate an avatar live and watch it animate, (b) one <agent-3d> tag in an empty index.html, drive mood from the console, (c) upload an unsupported rig to Rig Doctor and show exactly which joints will not move. Fallback GLB staged in case a worker is slow |
| 0:18-0:23 | Motivation / how it started | Why "3D agent" was a dead end until rendering and runtime could talk; what broke the first three times |
| 0:23-0:33 | How can people contribute? | Done live: take the HumanIK issue (issue 1 in the contribution menu; #110 and #111, the original picks, were closed on 2026-09-15), write the mapping, write the test, run npx vitest run tests/glb-canonicalize.test.js, open the PR on air, merge it on air |
| 0:33-0:36 | Last thing pushed / next thing | Read it off the public changelog; it ships to Telegram on every release so the honest answer is the only one available |
| 0:36-0:42 | Audience questions | End with the good first issue list on screen, by number |
| 0:42-0:45 | Wrap-up questions | Best tip for new contributors: comment on the issue before you start, one line. They also ask favourite song, an emoji, and an ice cream flavour; have answers, do not improvise on air |
Their prep checklist, from the guide, done in advance: wired ethernet; separate mic and headphones; 1920x1080; browser zoomed to 125% or more; fresh browser profile with no bookmarks bar or plugins; signed in and MFA-cleared on everything the demo touches; notifications off; menu bar and Dock auto-hidden; a template repo for the demo so it can be repeated. Ours on top: workers warm, fallback GLB staged, no .env and no wallet UI on screen at any point.
Downplay on stream: the on-chain and payments surfaces. They are real and they are in the repo, but this audience is maintainers and contributors, and leading with crypto costs credibility with exactly the people we want opening PRs. If it comes up, one honest sentence: agents can hold a wallet and pay for their own compute, it is optional, here is where the code lives.
4b. What approved requests look like (read 2026-08-25)
Read every approved or scheduled issue on githubevents/open-source-friday from the last year, the comment threads after approval, and both rejections on record. What it says:
Approval is about the criteria, not the pitch. Big names get approved with one line of bio (Remotion: "I make Remotion!"; Mastra: a job title and a list of previous companies). Both rejections on record were for the same two reasons, neither of which applies to us: a project under the minimum criteria (#106), and a proposal about a personal contributor journey rather than a project (#87, told plainly that streams are "focused on the technical aspects, contributions and development of the projects themselves").
"Not yet" on the date is normal and does not slow approval. cq (#215), any-llm (#185) and isomorphic-git (#231) all submitted without a date and were approved; the bot sends the booking link on approval. The one date correction on record was a guest who put a Monday in the title. 09-11-2026 is a Friday (checked), as are the four after it.
The request that got the most engagement is the one to beat. Pollinations (#223, 15 comments, Andrea: "Really looking forward to this one") wrote a named topic, a numbered outline of what the stream would cover, and a demo list. Everyone else left Additional Information empty or dropped a few press links (cq). Ours now has all three, mapped to the segment order in their own Streaming Guide.
What happens after approval, so nothing surprises us: a bot posts the booking link; after booking, a bot posts the scheduled notice ("be ready with your demo, our audience strongly prefers technical demos"), generates a promo thumbnail as a workflow artifact, and opens a task list for the hosts (social card, StreamYard scheduling, social posts). Guests have had to chase the prep doc and the StreamYard link in the week of the stream (#215), so plan to ask on the issue the Monday before if nothing has arrived. The host's on-air questions are posted to the issue the day before; answer them in the thread so the host has them.
What we cannot match and should not try: press coverage helped cq; we have none to cite and did not invent any. LinkedIn, present on every approved request, is on ours as of 2026-08-25.
5. What GitHub's own account tells us about promotion
Analysis of 500 posts from @GitHubCommunity (GitHubCommunity_tweets_2026-08-21.json, scraped 2026-08-21). Engagement scored as likes + 3x retweets + replies.
Media is the single biggest lever.
| Format | Posts | Avg engagement | Median |
|---|---|---|---|
| Image | 73 | 31.0 | 13 |
| Link card | 30 | 27.4 | 12 |
| Video | 37 | 20.6 | 8 |
| Plain text | 360 | 10.5 | 8 |
An image post averages roughly 3x a plain text post on that account.
Their own OSF announcements are underpowered, and that is our opening.
141 posts mention Open Source Friday. 134 are the same bare template: Open Source Friday with <Project> plus a broadcast link, averaging 9.9 engagement. The 7 carrying an image or video average 16.4. The yearly trend on OSF posts is straight down: 16.6 (2023), 10.5 (2024), 8.7 (2025), 7.1 (2026 to date). Their whole account fell the same way, 27.5 in 2022 to 6.4 in 2026.
Read: do not rely on GitHub's post to carry the episode. Their announcement will be a plain link reaching a few hundred views. Reach has to come from our side, and our post is the one that should have the video.
What actually broke out for them (the top of the 500): projects with visible output. Game Off showcases with playable browser games (146 likes, 40 K views), Godot game roundups (126 likes, 73 K views), an open source game launch with a funding pool (90 likes, 23 RTs). Every one is "here is a thing you can look at, and then go run yourself". That is our shape exactly: a 3D avatar is a screenshot that explains itself. The second cluster is calls to action with a deadline (Git Merge CFP, conference booth applications, 30 to 48 engagement each).
Post plan around the episode (finals go in docs/x-posts/, one file each, per repo convention):
- T-14, application: "We just applied to be on GitHub's Open Source Friday" plus the issue link and the 45-second demo clip. Reply into Andrea's thread rather than posting cold.
- T-7, the ask: the
good first issuelist as a readable numbered image, CTA to claim one before the stream so we can review it live. This is the Git Merge CFP pattern, their best-performing non-showcase format. - T-1, reminder: short, image, exact time in ET plus one converted timezone, Twitch link.
- T-0, live: quote-post GitHub's announcement the minute it goes up, so our audience gets it with a face on it instead of a bare link.
- T+1, replay: the best 30 seconds of the stream as a standalone clip, plus the merged PR from the live contribution segment. The replay clip usually outperforms the live post because it is watchable on its own.
Every one carries an image or video. No plain-text posts in this sequence. Cross-post each to the X community and the Telegram community; the IBM Community group gets the T-7 and T+1 posts only, since it is an enterprise audience and reminder spam reads badly there.
6. Timeline
Every hard criterion is met, stars included. What remains is one click, polish, and scheduling.
| Date | Milestone | Owner |
|---|---|---|
| 2026-08-21 | Community docs, triage, onboarding, six curated issues, labels, MMD rig support | Done |
| 2026-08-21 | Relicensed to Apache-2.0: LICENSE, NOTICE, 102 manifests, README, changelog | Done |
| 2026-08-25 | Three seed Discussions posted (#122, #123, #124) | Done |
| 2026-08-25 | Pin #122 | Owner, one click |
| 2026-08-26 | README front door trimmed, demo clip recorded | Agent |
| 2026-08-25 | Issue submitted: open-source-friday#254 | Done |
| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: x-posts/osf-issue-reply.md) | Owner |
| 2026-08-28+ | Booking link arrives on approval, book the slot | Owner |
| 2026-09-01 | Approved; booking bot asked for a date | Done |
| 2026-09-17 | All six August issues closed; seven new issue bodies and the booking reply written (menu) | Done |
| Next | Book a Friday (earliest October 2), reply on #254, create the menu issues | Owner |
7. Open questions for the owner
One, and it is genuinely yours to call:
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.