Episode 133: Until Next Time  🔗 **Source:** [Episode 133: Until Next Time](https://www.youtube.com/watch?v=Ojfp6DK5B8w) > [!note]+ Document Notes > tags: [chaoss, open-source-community, community-health, community-metrics, open-source-governance, devrel] > author: [MISSING] > source: Chaos Cast (CHAOSS community podcast) > reference: https://www.youtube.com/watch?v=Ojfp6DK5B8w > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Episode 133: Until Next Time > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [CHAOSS project](https://chaoss.community/) - [Sustain OSS podcast](https://sustainoss.org/podcast/) — cited as the inspiration for Chaos Cast - [Open SSF Alpha-Omega Project](https://openssf.org/community/alpha-omega/) — AI-assisted vulnerability discovery, mentioned by Alice - [FreeBSD Foundation](https://freebsdfoundation.org/) — Alice's paid open-source work - [EU Cyber Resilience Act](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act) — regulation Alice now tracks ## 📝 Summary - Chaos Cast, the CHAOSS community podcast on open-source community health and metrics, records episode 133 as a deliberate, formal pause after more than six years and 132 prior episodes. - It matters because it's a candid post-mortem on a community-run content program: the organizers say they can't justify the time and money against the value delivered, so they're pausing indefinitely rather than quietly fading out. - Key stakeholders: hosts and organizers Harmony Elendo (newly elected CHAOSS board member, leads the technical writers focus group), Alice (FreeBSD Foundation), Mary Blessing (joining a Sloan-funded community management team), and "G" (a founding organizer, referred to as Gil/Georg, stepping off the CHAOSS board), plus editor Paul Barr of Peach Tree Sound. - Risks and tradeoffs: the back catalog stays online, but momentum, onboarding of new voices, and the community-connection ritual (the "value adds") all stop; restart is possible only "if a clear community need emerges." - Bottom line: a community podcast survives six years precisely because it was built as community-owned rather than one person's project — and it's being sunset with the same transparency that metrics-minded communities preach. ## 📖 Main Content - The episode is a farewell/reflection format. Rather than covering a single technical topic, the panel narrates the origin, operating model, metrics, and wind-down of Chaos Cast itself. - Origin story: CHAOSS (Community Health Analytics in Open Source Software) started around 2017 to pull together scattered efforts on measuring open-source community health. Working-group conversations were rich, but that knowledge lived only in meetings. Blog posts didn't work ("if you've ever tried to get people to write anything, it is really difficult"), so the organizers moved to recorded Zoom conversations, launching the podcast May 1st, 2020, inspired by and initially networked with the Sustain OSS podcast. - Operating model as the durable insight: it was deliberately made a *community* podcast, not a personal brand. Design choices that kept it alive — a community logo contest (episode 26 interviews the winner, Lewis Canastas), always more than one organizer (started with three), a rotating tradition of handing the baton to new hosts, and pulling in panelists from the community for unscripted conversation. - Recurring formats mentioned: "20 Minutes with CHAOSS Africa" (led by Harmony, surfacing African-continent contributions to metrics), the Practitioner Guides series (tied to Dr. D's blog posts), event recaps, and coverage of new working groups. A closing "value adds" segment let each guest share something adding value to their life — a deliberate humanizing ritual. - Metrics (with transcription caveats): ~37,000 total downloads across the run; ~28 downloads per episode average; episode 31 (marketing metrics for open-source foundations, a CHAOSS × GNOME × KDE collaboration with Sriram Krishna and Neofytos "Neo" Kronis) is the most-downloaded at 933; episode 1 (the "hello world" intro) is second at 586. New episodes get roughly 8–50 downloads day one, ~80–120 in the first 90 days. Geography skews ~60% United States, ~40% other, with Germany the second-ranked country at ~5%. Episodes generally ran 20–50 minutes. - Wind-down rationale: the team "has not been able to determine that the podcast is delivering enough value to the community to justify the time and financial resources required to sustain it." The catalog stays hosted; restart stays open if a clear community need appears. - Contested / uncertain claims: several numbers are garbled in the auto-transcript — "832 episodes" almost certainly means 132; "Chaos Castle" is "Chaos Cast"; the founding organizer's name renders inconsistently as G / Gil / GIO / GEOK (likely Georg Link, a CHAOSS co-founder, but the transcript does not confirm the surname). Treat exact figures as approximate. ### 🗒️ Notes #### 🎬 Opening — panel and premise - Host Harmony Elendo introduces the panel: herself, Mary Blessing, "G," and Alice; frames the listener as "on the panel today." - Harmony: project/product manager, newly elected CHAOSS board member, leads the CHAOSS technical writers focus group. - Alice states the news plainly: "We decided to do an episode to put a formal pause on the Chaos Card podcast by recording a special episode." #### 🕰️ History of Chaos Cast (told by "G") - "The first episode we published on May 1st, 2020." More than six years and (this being the 133rd) 132 prior episodes. - CHAOSS community began ~2017 to consolidate open-source community-health efforts; podcast was the answer to "how do we share the experiences… preserve it in a way that more people can join even when they're not in the meetings?" - Blog posts failed as a knowledge-sharing mechanism; recorded conversations worked. Inspired by Sustain OSS; joined then outlived a podcast network. #### 🤝 Why it survived — community ownership - Core claim: "By making it the deliberate community podcast, we were able to keep the podcast alive. If it had been mine, it would have fallen apart." - Mechanisms: logo contest (winner Lewis Canastas, ep. 26), "We also made sure to always have more than one organizer" (three at start), rotating hosts, unscripted community panelists. - Baton-passing: Alice took it over ~two years ago from Dawn, continuing a tradition of finding a replacement to share the work. #### 🎙️ What the format did for people - Recording forces preparation and clarity: being recorded "makes you really sort of focus on actually really preparing and getting your thoughts into a good order." - Value-add segment humanizes guests: "We purposely included a section value ads at the end where whoever was on the podcast could just share about what is currently adding value to their life." - Practitioner Guides cited as the favorite series for its depth. #### 📊 The stats segment - ~37,000 downloads; ~28/episode average; ep. 31 top at 933 (marketing metrics, CHAOSS × GNOME × KDE); ep. 1 second at 586. - First-90-days ~80–120 downloads; outliers ep. 31, ep. 103 (~281), ep. 30 (~258). Geography ~60% US / ~40% rest; Germany ~5%. Length mostly 20–50 min. #### 🙏 Thanks to the editor - Big shout-out to Paul Barr of Peach Tree Sound, who edited every episode; the running gag of "Paul just joined us" as the cue word for edits. #### 🚀 What's next for each panelist - Harmony: drive engagement, participation, diversity, and global expansion of CHAOSS chapters from the board; continue product/program management in open source and finance. - Alice: continues FreeBSD Foundation work; now tracking the EU Cyber Resilience Act (trips to Brussels) and AI-assisted vulnerability discovery via Open SSF's Alpha-Omega Project. - Mary Blessing: joining a newly renewed Sloan-funded community management team at CHAOSS; seeking a full-time open-source community/engagement role; pursuing a data science degree. - "G": role with "Petria" (likely a garble) ended; a new unannounced role combining tech, business, and community; term on CHAOSS board has ended — "it is time to pass on the baton." #### 💬 Value adds (closing ritual) - G: his husband occasionally listening and quoting the episodes — the personal encouragement that pulled him back to organizing. - Alice: international community — regular contact across Italy, Brazil, Ukraine, Canada, Finland, Nigeria, Taiwan, Japan; "time zone ninja." - Mary Blessing and Harmony: cross-cultural connection, travel, food, and experiencing cultures they've only read about. - Alice closes: "Until next time, your Chaos Community." ## 📚 References - [CHAOSS — Community Health Analytics in Open Source Software](https://chaoss.community/) - [Sustain OSS podcast](https://sustainoss.org/podcast/) - [Open SSF Alpha-Omega Project](https://openssf.org/community/alpha-omega/) - [FreeBSD Foundation](https://freebsdfoundation.org/) - [Alfred P. Sloan Foundation](https://sloan.org/) — funder of the renewed CHAOSS community management grant - [GNOME](https://www.gnome.org/) · [KDE](https://kde.org/) — collaborators on the top episode's marketing-metrics work ## 🗣️ Paraphrase - The CHAOSS podcast team is deliberately pausing Chaos Cast after six-plus years, framing it as a transparent decision: they can't justify the effort and cost against the value the podcast returns to the community, so they're stopping cleanly while keeping the archive online. - The lasting lesson they draw is about structure, not content — the podcast lasted because it was owned by the community (multiple organizers, rotating hosts, contest-chosen branding, unscripted community panelists) rather than by any single person, so it survived every individual's departure. - Alongside the reflection, the panel shares transparent listenership metrics and each organizer's next chapter, closing with the show's signature "value adds" ritual that connected people beyond the technical topics. ## 📰 Newsletter Community-run media is hard to keep alive, and Chaos Cast just modeled how to end one gracefully. After 132 episodes and six years, the CHAOSS community podcast is pausing — not with a quiet disappearance but with a candid episode explaining that they couldn't justify the time and money against the value delivered. For WordPress folks who run Meetup recaps, contributor podcasts, or a Make team's series, the takeaway is worth stealing: build it as a community property from day one (more than one organizer, a rotating-host tradition, community-chosen branding), publish your own listenership numbers honestly, and keep a humanizing ritual like their end-of-episode "value adds." Bonus links from the episode: the [Practitioner Guides](https://chaoss.community/) approach to turning working-group knowledge into shareable artifacts, and Open SSF's [Alpha-Omega Project](https://openssf.org/community/alpha-omega/) for AI-assisted vulnerability discovery in open source. The archive stays online — a reminder that sunsetting a program and preserving its knowledge aren't the same decision. ## ✅ Action Items #### DevRel - Developer advocacy: adopt the "recording forces preparation" insight — offer community members a recorded conversation slot as a lighter-weight alternative to writing a blog post, capturing tacit knowledge that would otherwise stay in meetings. - Education: model a Practitioner-Guide pattern — pair each written guide with a short recorded conversation where the author talks through their real experience, not just the doc. - Developer experience: document a "how to hand off a community program" runbook (baton-passing, multi-organizer minimum) so volunteer-run content survives individual churn. - Developer marketing: publish transparent program metrics (downloads/attendance, geography, top items) as a norm; use the value-vs-cost framing to decide when to sunset a channel. - Community management: institute a recurring humanizing ritual (the "value adds" segment) in community calls/podcasts to connect people beyond technical topics; run a periodic "is this still delivering value?" review before renewing effort. - Internal/external/cross-project: borrow the CHAOSS × GNOME × KDE collaboration model — co-produce content across projects to lift reach (their top episode came from exactly this). #### OSPO - Policy & Governance: use CHAOSS-style community-health thinking to set explicit sunset criteria for OSPO-run programs (a written "justifies time and financial resources" test). - License Compliance: N/A — not addressed in this episode. - Security Management: track Open SSF's Alpha-Omega AI-assisted vulnerability-discovery model and the EU Cyber Resilience Act as inputs to OSPO security policy (both surfaced via Alice). - Software Inventory: N/A — not addressed in this episode. - Developer Support: fund and formalize community management roles (the Sloan-grant community management team is the reference); treat community health as staffed work, not volunteer overflow. - Community Engagement: study CHAOSS chapter expansion (Africa, Asia chapters) as a template for global upstream engagement. - Strategic Alignment: adopt community-health metrics (CHAOSS) as OKR inputs for executive reporting on open-source program value. #### Community - Maintainers: require more than one organizer and a documented baton-pass for any recurring community program; it's the single practice most credited with the podcast's longevity. - Contributors: create low-friction on-ramps (recorded conversation instead of a blog post) so first-time contributors can share knowledge; the podcast was several panelists' first independent open-source contribution. - Sponsors: publish transparent program metrics and a value-vs-cost rationale so sponsors see honest impact reporting, including graceful sunsets. - Ecosystem: run cross-project co-productions (GNOME/KDE-style) to pool audiences and metrics work. #### WordPress - Core: N/A — episode is community-media focused, not core code. - Core Performance: N/A. - Core AI: N/A — general open-source AI security only, no WordPress-specific tie. - **Core Program Team:** borrow the multi-organizer + rotating-host model and the periodic value-vs-cost review for cross-team program rituals. - Mobile: N/A. - Playground: N/A. - Community: directly applicable — apply the community-ownership structure, transparent metrics, and "value adds" ritual to WordPress Meetup/WordCamp media and the Make community podcasts; document a program-sunset playbook. - Training: pair Learn WordPress lessons with short recorded practitioner conversations, Practitioner-Guide style. - Marketing: publish transparent reach metrics and adopt honest sunset communication as a norm. - Support: N/A. - Design: N/A. - Documentation: adopt the "recorded conversation captures what people won't write down" tactic to fill DevHub/HelpHub gaps. - Photos: N/A. - TV: relevant — caption quality and content indexing for WordPress.tv mirror Paul-the-editor's polish role; keep archives hosted even when a series pauses. - Polyglots: mirror CHAOSS chapter/global-voice model to widen locale coverage in community media. - Accessibility: ensure any community podcast ships captions/transcripts (see Accessibility Assessment). - Meta: N/A. - CLI: N/A. - Hosting: N/A. - Tide: N/A. - Openverse: N/A. - Themes: N/A. - Plugins: N/A. #### The WPCC - Programs: fund community management as staffed roles (Sloan-grant model); consider stipends so community media isn't purely volunteer-dependent and doesn't collapse on one person's exit. - Projects: use CHAOSS community-health metrics as the measurement layer for WPCC-funded governance/documentation projects. - Funding experiments: adopt transparent value-vs-cost review gates before renewing funding for any recurring program. ### FAIR - Technical independence: N/A — not addressed in this episode. - Policies and covenants: the transparent "justify time and financial resources or sunset" test is a reusable governance covenant for federated/independent projects. - Productized governance artifacts: package the multi-organizer + baton-pass + value-vs-cost-review pattern as a reusable community-program charter. ## 🧪 Hypotheses - Community-owned programs (multiple organizers, rotating hosts) outlast personality-led programs by surviving individual departures. - Offering a recorded conversation instead of a writing ask increases knowledge-capture participation from community members. - A humanizing closing ritual (the "value adds") increases guest willingness to return and increases listener parasocial connection. - Cross-project co-productions (e.g., CHAOSS × GNOME × KDE) produce higher-reach episodes than single-project ones. - Publishing transparent, modest listenership metrics does not reduce contributor participation and may increase trust. - A program's per-episode download curve (front-loaded in the first 90 days) means long-tail archive value depends on discoverability, not new releases. ### 📊 Methodology - Compare survival time and volunteer-continuity of community-owned vs. single-owner open-source media programs across a sample of projects. - A/B a "write a post" ask vs. a "record a 30-minute conversation" ask with the same contributor pool; measure completion rates. - Cohort-analyze guest return rates and listener retention for episodes with vs. without the value-adds segment. - Regress episode downloads on a cross-project-collaboration flag, controlling for topic and release date. - Interrupted time-series on contributor sign-ups before/after publishing transparent metrics. ### ❓ Questions - What concrete threshold would count as "clear community need" to restart Chaos Cast, and who decides? - Would a lighter format (short async clips, text digests) deliver the community-connection value at lower cost than a full podcast? - How much of the podcast's value was the artifact vs. the relationships formed while making it — and can the latter be preserved without the former? - Does the front-loaded download curve justify a "seasons" model over indefinite continuous publishing? ### 🔮 Future Research - Whether CHAOSS's own community-health metrics can be turned on the podcast itself to make the sunset decision quantitative rather than felt. - Portable "community program sunset playbook" validated across multiple OSS communities. - Impact of AI-assisted vulnerability discovery (Alpha-Omega) on small-project maintainer workload — a thread Alice opens but the episode doesn't explore. ### 💡 Implications - Practice: recurring community media needs a documented multi-owner structure and a periodic value review, or it dies with its champion. - Policy: transparent value-vs-cost sunsetting is a governance-positive move, not a failure; communities should normalize it. - Security: EU CRA and AI-assisted vuln discovery are becoming baseline concerns even for foundation-funded OSS work. - Education: pairing written guides with recorded practitioner conversations captures tacit knowledge writing alone misses. - Funding: community management deserves staffed, grant-funded roles (Sloan model) rather than volunteer overflow. ### 🧠 Learning Styles Assessment - Reading level estimate: conversational spoken transcript; approximate Flesch-Kincaid Grade ~7–8 (short clauses, everyday vocabulary, high redundancy typical of speech). #### 👀 Visual learners - Present: none — audio-only conversation, no diagrams or charts. - Improve: add a stats infographic (downloads over time, geography map) and a timeline of milestone episodes. #### 🔊 Aural learners - Present: strong — it's a professionally edited podcast with natural conversation. - Improve: publish a 2–3 minute audio recap of the metrics and the sunset rationale. #### 🗣️ Verbal learners - Present: strong — storytelling, personal anecdotes, defined program names. - Improve: a short glossary (CHAOSS, Practitioner Guides, value adds, Alpha-Omega, CRA) for newcomers. #### 🧩 Kinesthetic learners - Present: minimal. - Improve: a "start your own community podcast" checklist derived from the survival mechanisms discussed. #### 🧠 Logical learners - Present: the stats segment offers structured numbers. - Improve: a decision table for "continue vs. pause a community program" using explicit value/cost criteria. #### 🧑‍🤝‍🧑 Social learners - Present: strong — the whole episode is community and relationships. - Improve: a discussion prompt set for community managers to reflect on their own programs. #### 🧘‍♀️ Solitary learners - Present: reflective tone supports solo listening. - Improve: journaling prompts on sustaining volunteer work. #### 🌿 Naturalistic learners - Present: "community health" and "sustainability" framing throughout. - Improve: extend the ecosystem/lifecycle metaphor to program lifecycles explicitly. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: N/A for audio; depends on the YouTube/show-notes page structure. - Improve: provide a well-structured transcript page with headings and speaker labels. #### Keyboard navigation - Present: N/A (media artifact). - Improve: ensure the hosting player controls are keyboard-reachable. #### Contrast and readability - Present: N/A. - Improve: ensure show-notes and any stats graphics meet 4.5:1. #### Text resizing and reflow - Present: N/A. - Improve: responsive transcript/show-notes. #### Media and captions - Present: audio is professionally edited; captions/transcript availability unconfirmed. - Improve: ship a cleaned, speaker-labeled transcript and captions — the auto-transcript garbles names and numbers (e.g., "832 episodes," "Chaos Castle"), which harms comprehension for caption users. #### Forms and interactions - Present: N/A. - Improve: N/A. #### Standards reference - Primary gap maps to WCAG 2.2 AA 1.2.2 (Captions) and 1.2.1 (Audio-only alternative): provide an accurate transcript. ### 🌍 DEIB Assessment #### Cultural breadth - Present: strong — CHAOSS Africa and Asia chapters, panelists connecting across Nigeria, Italy, Brazil, Ukraine, Finland, Taiwan, Japan, Canada. - Improve: add multilingual transcripts/summaries to match the global listenership. #### Inclusive language - Present: warm, respectful, plain language; jargon mostly explained in context. - Improve: define acronyms (CHAOSS, CRA, Open SSF) on first use for newcomers. #### Neurodiversity support - Present: consistent, predictable segment structure (history → stats → what's next → value adds). - Improve: publish a chaptered transcript with clear headings. #### Representation - Present: diverse panel across geographies and roles, women prominent as hosts and organizers. - Improve: credit each speaker by full name and role in show notes (the audio alone leaves the founding organizer's surname ambiguous). #### Psychological safety - Present: high — appreciative, emotionally open ("it's quite emotional in the panel today"), generous crediting of contributors and the editor. - Improve: none needed; this is a model of respectful framing. ### ✅ Logical Validity #### Strong reasoning - Causal (community ownership → longevity): "If it had been mine, it would have fallen apart and been done long time ago." Strong because it's supported by concrete mechanisms (multiple organizers, rotating hosts, contest branding) rather than assertion alone. Clarify further with a counterfactual comparison to single-owner podcasts. - Inductive (recording → better preparation): drawn from repeated personal experience across many episodes; reasonable generalization. Clarify by noting it may not hold for reluctant or over-prepared speakers. #### Fallacies - Mild hasty-generalization risk in the value judgment: "we have not been able to determine that the podcast is delivering enough value" treats absence of measured value as insufficient value. Location: Alice's intro. Weakness: download counts may undercount real relationship value the panel itself celebrates. Fix: state the specific value metrics considered and their thresholds. - No other notable fallacies; the episode is reflective, not argumentative. #### Tone of voice - Warm, grateful, reflective, occasionally playful (the Paul-editor gag, "time zone ninja," Antarctica quip). Emotionally candid ("it's quite emotional in the panel today"). ### 🛡️ DARVO Analysis - Deny: none. The team openly owns the decision and its rationale rather than minimizing it. - Attack: none. No accusers, no credibility undermining; the tone is appreciative throughout. - Reverse victim/offender: none. No recasting; if anything the organizers take full responsibility for the pause. - Emotional cues are sincere gratitude and mild wistfulness, not defensive rhetoric. DARVO patterns are absent — this is a cooperative farewell, not a contested claim. ## 🎯 Conclusion - Bottom line: Chaos Cast lasted six years and 132 episodes because it was engineered as a community-owned program, and it's pausing with the same transparency CHAOSS preaches about community health — an honest value-vs-cost call, archive preserved, door left open. - Practical next steps for readers: if you run community media (WordPress Meetups, Make podcasts, DevRel series), copy the survival kit — multiple organizers, a baton-passing tradition, community-chosen branding, transparent metrics, and a humanizing ritual — and adopt an explicit sunset test so the program can end gracefully instead of collapsing on one person's exit. ## 🔄 Refactor Appendix — Episode 133: Until Next Time > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] Community ownership keeps a volunteer podcast alive > [!quote] ID:rw_h1 > By making it the deliberate community podcast, we were able to keep the podcast alive. **Context & use**: - History segment, told by founding organizer "G." - The single most load-bearing claim: structural community ownership, not a personal brand, is what let the show survive six years. **Tags**: #xref #aphorisms **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H2] Sunset when value no longer justifies cost > [!quote] ID:rw_h2 > At this time, however, we have not been able to determine that the podcast is delivering enough value to the community to justify the time and financial resources required to sustain it. **Context & use**: - Alice's opening statement announcing the pause. - A reusable governance test for any community program: pause transparently rather than fade out. **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H3] Always staff more than one organizer > [!quote] ID:rw_h3 > We also made sure to always have more than one organizer. **Context & use**: - Survival-mechanisms list in the "why it survived" segment. - Concrete, copyable practice that prevents single-point-of-failure collapse in volunteer programs. **Tags**: #xref #share **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H4] A closing ritual humanizes technical guests > [!quote] ID:rw_h4 > We purposely included a section value ads at the end where whoever was on the podcast could just share about what is currently adding value to their life. **Context & use**: - Format discussion; the "value adds" segment. - Design pattern for community media: a deliberate humanizing ritual builds connection beyond technical content. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Community-owned programs outlast personality-led ones **Claim** (one sentence, Courtney's voice): A recurring community program survives its founders only when ownership is structurally distributed across rotating organizers rather than tied to one person's brand. **Evidence pointer**: [[#H1]] > [!quote] > If it had been mine, it would have fallen apart and been done long time ago. **Scope & conditions**: Holds for volunteer-run media and community rituals; breaks when a program requires deep single-owner expertise that can't be rotated. **Links**: - [[Open source community health]] — because extends - [[Bus factor]] — because contrasts on single-point-of-failure - [[WordPress Make team programs]] — because applies-in community media <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Draft a "community program sunset test" — transparent value-vs-cost criteria before renewing effort. — from ep. 133 #fleeting #inbox - [F2] Confirm founding organizer's identity (likely Georg Link) and correct garbled stats (132 not 832 episodes) before citing. — transcript QA #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Write up the CHAOSS "survival kit" (multi-organizer, baton-pass, transparent metrics, value-adds ritual) as a reusable community-media checklist — DevRel/Community #things - [ ] Add captions/transcript-quality note to WordPress.tv + Make podcast guidance, citing the auto-transcript garble problem — Accessibility #things ``` Processed: Episode 133: Until Next Time - Literature atoms: 4 / 5 cap - Permanent candidates: 1 / 3 cap - Fleeting items: 2 - Things 3 actions: 2 / 2 cap - Konik tags used: [#xref, #aphorisms, #articleseed, #share] - Triage callouts populated: [Cross Reference, Article Ideas, Aphorisms/inline, Share] - Quality gates: [verbatim ✓, atomicity ✓, link-annotation ✓, YAML-hygiene ✓, Konik-triage ✓, view-highlight ✓] - Override conditions triggered: [4th Literature atom — strong distinct claim on ritual design] ``` <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Episode 133 Until Next Time.md|Episode 133: Until Next Time by youtube.com]] ## Highlights - determine that the podcast is delivering enough value to the community to justify the time and financial resources required to sustain it. But if there is ([View Highlight](https://read.readwise.io/read/01kwj98mnpy1x0daadqy4555nt)) - Note: Sunsetting rationale: value to community vs. time/financial cost to sustain - Tags: atom/literature/h2 - something like that." By making it the deliberate community podcast, we were able to keep the podcast alive. ([View Highlight](https://read.readwise.io/read/01kwj98cccksa68c9z536ayjp9)) - Note: Framing it as a deliberate COMMUNITY podcast (not one person's) kept it alive - Tags: atom/literature/h1 - If it had been mine, it would have fallen apart and been done long time ([View Highlight](https://read.readwise.io/read/01kwj98vg39r4k4k30qwn1vyqe)) - Note: Community ownership outlasts solo ownership — the durability argument for shared stewardship - Tags: atom/zettel/z1 - made sure to always have more than one organizer. So we started with three ([View Highlight](https://read.readwise.io/read/01kwj98pjy0myfms59kagchhcn)) - Note: Resilience practice: always more than one organizer (bus-factor for community projects) - Tags: atom/literature/h3 ## Links - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — Project endings expose how much community work consists of maintenance and continuity. - [[3. Resources/MOCs/Commons & Community Governance MOC]] — A closing reflection on sustaining and ending an open-source community program.