Repository navigation
docs(community): 2026-09-30 meeting pages - #1279
Merged
Merged
Conversation
✅ Deploy Preview for dreamy-golick-5f201e ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
🔎 Structured data validation
✅ All checks pass and no authoring warnings to backfill. ⚙️ Generated by |
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
force-pushed
the
community-meeting-2026-09-30
branch
from
October 2, 2026 19:35
7e28d1b to
9aa2219
Compare
jfleitz
approved these changes
Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
wstdwith 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_storebucket-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
bailey-hayes,liam-randall,aditya-salunkhe,jeremy-fleitz,frank-schaffa), all already inpeople.json.VideoObject.actor[]emits all five. Otter labeledSpeaker 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.duration: 2250(recording is 2249.99s, matching Otter's 37:30). That gives 25Clips, all withendOffset(the last runs 2170→2250).about: wasmCloud+ 8mentions(no new entities needed)./blog/wasmcloud-2-10-release/.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 buildpassesnode scripts/validate-structured-data.mjs: 897 HTML files, 5111 payloads, OK[M:SS](…?t=N)satisfiesN == seconds(32 landing, 31 transcript)chapters:matches## Chapters;duration > max(chapters)slug:; no date-path references to fixUgzwBhMX8Y4GOUlU7hB4AaABAg, still needs pinning in Studio)