Skip to content

docs(community): 2026-09-30 meeting pages - #1279

Merged
LiamRandall merged 1 commit into
mainfrom
community-meeting-2026-09-30
Oct 2, 2026
Merged

LiamRandall merged 1 commit into
mainfrom
community-meeting-2026-09-30

Conversation

@LiamRandall

@LiamRandall LiamRandall commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

Landing and transcript pages for the September 30, 2026 wasmCloud community call (video). Replaces the agenda stub merged in #1277 (same video ID U04P5os6D_k).

Topics: Bailey Hayes previews the Q4 roadmap (discussion #5619; planning call Oct 7) after announcing the 2.10.2 patch and pointing to the 2.10 release blog. The four themes: the component ecosystem (Python SDK likely, C/C++ optional, Rust onto wstd with P3, aws-lc-rs#1239 as a "just flags" WASI recipe, Aditya Salunkhe's Lapin/Sentry/SQLx ports, "Are we componentized yet?" matrix, protocol + WIT design guidance), performance (customizable precompiled cache, exploded components, streamable data segments; Liam Randall asks what dedup means for Go/Python), Jeremy Fleitz's k6 harness (wasmCloud#5630) that found a local-routing bug, integration (object_store bucket-scoped ops upstream → S3 first; declarative Blob Store / Key-Value grants per wasmCloud#5498; integrations as sandboxed host component plugins), Frank Schaffa on agents building integrations, and workload identity + credential brokering as the biggest rock (RFC coming, stacked drafts landing next week).

Standards

  • Speakers: 5 slugs (bailey-hayes, liam-randall, aditya-salunkhe, jeremy-fleitz, frank-schaffa), all already in people.json. VideoObject.actor[] emits all five. Otter labeled Speaker 1/2/3/4. Speaker 1 = Aditya (Zoom name tag + active-speaker tile at 640s, 1440s, 1840s). Speaker 2 = Jeremy Fleitz (name tag at 1245s). Liam was named by Otter and is confirmed on video at 1020s. Speaker 4 = Frank Schaffa is camera-off (no tile). He is attributed because Bailey says "Yeah, Frank" immediately before his turn, and he is a returning participant. Please sanity-check: this is a single addresser, below rule 15's bar of two (same situation as 2026-09-23). Speaker 3 said only "sorry" and was dropped. Eric Gregory and Shreya were on camera but didn't speak.
  • JSON-LD: duration: 2250 (recording is 2249.99s, matching Otter's 37:30). That gives 25 Clips, all with endOffset (the last runs 2170→2250). about: wasmCloud + 8 mentions (no new entities needed).
  • Links: v2 routes from the link map only, plus /blog/wasmcloud-2-10-release/.
  • Primary-source checks: discussion #5619 and its three questions, the Q3 shipped list, the k6 PR's scenarios and profiles, aws-lc-rs#1239 (WASI SDK 34, Wasmtime 48.0.2), and the #5498 config keys were read from on-screen frames. Otter's "open bow" was unintelligible and is omitted rather than guessed.

SEO

Primary keyword wasm component model (🟢, KD 17; protected pos 16 → top 10), in the title (as "Wasm Components"), description (first 70 chars), TL;DR, and the Topic Deep Dive on exploded components. Secondary: python webassembly, rust webassembly, webassembly news (H2), ai sandbox (workload identity / credential brokering), webassembly kubernetes (k6 on kind via the runtime operator). The YouTube title is exactly 100 chars with the channel suffix.

Frames

8 WebP frames from the local recording in static/img/community/2026-09-30/, as raw <img> tags. No 0-byte frames. One screen share at ~480s that showed private Google Drive docs was deliberately skipped.

Verification

  • npm run build passes
  • node scripts/validate-structured-data.mjs: 897 HTML files, 5111 payloads, OK
  • Every [M:SS](…?t=N) satisfies N == seconds (32 landing, 31 transcript)
  • chapters: matches ## Chapters; duration > max(chapters)
  • Both pages have explicit slug:; no date-path references to fix
  • YouTube metadata + comment pushed as the wasmCloud channel (comment UgzwBhMX8Y4GOUlU7hB4AaABAg, still needs pinning in Studio)

@LiamRandall
LiamRandall requested a review from a team as a code owner October 1, 2026 20:52
@netlify

netlify Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for dreamy-golick-5f201e ready!

Name Link
🔨 Latest commit 9aa2219
🔍 Latest deploy log https://app.netlify.com/projects/dreamy-golick-5f201e/deploys/6ac00774dc77a10008c10d41
😎 Deploy Preview https://deploy-preview-1279--dreamy-golick-5f201e.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🔎 Structured data validation

  • Mode: PR-incremental (base: origin/main)
  • Files checked: 897
  • JSON-LD payloads: 5111
  • Errors: 0
  • Warnings: 0

✅ All checks pass and no authoring warnings to backfill.

⚙️ Generated by ci_structured_data.yml • structured-data spike

Landing + transcript pages for the September 30, 2026 community call
(Q4 roadmap preview: Python SDK, exploded components, k6 load testing,
S3 for WASI Blobstore, workload identity). Replaces the agenda stub.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Liam Randall <liam@cosmonic.com>
@LiamRandall
LiamRandall force-pushed the community-meeting-2026-09-30 branch from 7e28d1b to 9aa2219 Compare October 2, 2026 19:35
@LiamRandall
LiamRandall merged commit af7225c into main Oct 2, 2026
8 checks passed
@LiamRandall
LiamRandall deleted the community-meeting-2026-09-30 branch October 2, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants