Episode 30: Miriam Goldman  🔗 **Source:** [Episode 30: Miriam Goldman](https://www.youtube.com/watch?v=SXyG-AxjypU) > [!note]+ Document Notes > tags: [wordpress-community, drupal, wordcamp-organizing, open-source-sustainability, contributor-burnout] > author: Chris Reynolds > source: Community & Code > reference: https://www.youtube.com/watch?v=SXyG-AxjypU > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > > [!note] Re-upload > > The channel re-uploaded this episode on 2026-09-22 as https://www.youtube.com/watch?v=YBdBuBojH2Y (92–95% identical transcript). This original doc stays canonical. > > > # 🏷️ Title: Episode 30: Miriam Goldman > <!-- 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 - [Episode video](https://www.youtube.com/watch?v=SXyG-AxjypU) - [Pantheon](https://pantheon.io) — employer of both host and guest - [DrupalCon](https://events.drupal.org) — the event Miriam attended two weeks before recording - [WordCamp Central](https://central.wordcamp.org) — the WordCamp program discussed throughout ## 📝 Summary - What happened: Chris Reynolds interviews Miriam Goldman — senior solutions architect at Pantheon, 10+ year WordPress community member, and WordCamp organizer/speaker/volunteer — about her recent cross-pollination into the Drupal community via DrupalCon and Drupal Camp Ottawa, plus her origin story, community bands, and 19 years of martial arts. - Why it matters: the episode surfaces a concrete sustainability critique of the WordCamp model. DrupalCon charges roughly $1,000, funds a paid Drupal Association staff, and directs surplus to development; flagship WordCamps charge $50–$100, run on unpaid volunteers, and are stalling from organizer burnout and failed succession. - Key stakeholders: WordCamp organizers and volunteers, the WordPress Community Team, plugin/module developers in both ecosystems, Pantheon (multi-CMS host), and the Drupal Association as a governance model. - Risks and tradeoffs: raising WordCamp ticket prices could fund paid organizers and project grants but risks pricing out the accessibility that defines WordCamps; Drupal's collaborative module culture produces better shared solutions but is "at odds with making money on the thing." - Bottom line: WordPress and Drupal communities feel remarkably similar on the ground, and each holds the fix for the other's weakness — WordPress could adopt Drupal's funded-event and collaboration models; Drupal benefits from WordPress people showing up and vice versa. ## 📖 Main Content - Miriam has filled every WordCamp role — organizer, speaker, volunteer, attendee — over more than a decade, including co-organizing WordCamp Canada and volunteer team lead at WordCamp US. She's now deliberately "wetting her feet" in Drupal (DrupalCon two weeks prior, Drupal Camp Ottawa twice) because "I don't feel it's good just to limit yourself just to one CMS." - Her core DrupalCon takeaway is affective, not technical: the Drupal community shows "genuine excitement for the technology," in contrast to the "exhaustion in the WordPress community with some of the unfortunate drama over the past couple of years." Nobody gatekept her for being a WordPress person. - The main technical difference she identifies is dependency management. Drupal's Composer-based workflow forces version awareness — pinning issues, module conflicts — but keeps sites current: "as long as you run your composer update... it's easier to just stay relevant and modern." WordPress plugins invite set-and-forget: "You could just leave it on an old version for decades." - Chris frames the cultural difference: in Drupal, two SEO module authors are "more likely to collaborate and make a better SEO plugin"; in WordPress, competing plugin authors hold IP they may want to sell, which "creates more of this competition in the WordPress world and less collaboration." Drupal CMS recipes (SEO recipe, AI recipe) institutionalize that collectivism — but he notes it sits at odds with monetization, and the Drupal marketplace conversation Dries opened a year ago is the attempted reconciliation. - The sustainability argument: DrupalCon (~$1,000 ticket) and WordCamp US (~$50–$100) feel identical as events at the same 1,200–1,500-person scale. The Drupal Association exists because Dries didn't want to organize everything himself; DrupalCon revenue pays board positions and funds targeted Drupal development. Chris argues flagship WordCamps "can probably charge more" — a couple hundred dollars — to pay event organizers and direct surplus to community-priority projects. Miriam agrees from experience: volunteer organizing "just felt thankless." - Case study in fragility: Chris lead-organized WordCamp Salt Lake City for four years; when he stepped back, no one took the reins, then COVID hit, and local momentum never recovered. Miriam names the catch-22: "people burn out so easily when they put so much of themselves into this," and burnt-out organizers don't train the next generation. - Origin story: Miriam entered WordPress around the late 2000s building a self-updatable website for her friend's church band (she played clarinet in it), after evaluating Drupal 5/6, Joomla, and Moodle. Government work paused professional use; a private-sector WordPress job turned it into a career — "a happy accident." Both host and guest credit the Codex and Stack Overflow era: WordPress always had an answer findable somewhere, which smaller CMSes lacked. - Word camps as career infrastructure: her last two jobs — Canopy Studios and Pantheon — both came through WordCamp connections. - Beyond WordPress: 30 years of clarinet, three years as a community-band percussionist ("everything but drum kit"), two bands on different weeknights; a fourth-degree black belt 19 years into karate (origin: a sensei who resembled the Green Power Ranger actor). Her WordCamp talk ~7 years ago mapped martial arts to tech careers: katas are ordered, orchestrated sequences like procedural programming — done out of order, both "go belly up." - Teaching pre-teen karate students maps to debugging, but for people it's "finding the best solution for them" — repetition for some, four-moves-at-a-time for others. She "hates one-size-fits-all." Chris extends this to tech support: what people say with their words isn't always what they want or need; the skill is listening for clues to the underlying problem. - Uncertainty to note: attendance figures, ticket prices, and Drupal Association history are recalled conversationally, not cited; Miriam explicitly caveats that she saw DrupalCon mostly from the sponsor booth. ## 🗒️ Notes #### ⏱️ [00:00:19](https://www.youtube.com/watch?v=SXyG-AxjypU&t=19) Intro — every WordCamp hat, now watching Drupal - Chris frames Miriam as someone who has "filled every role a word camp has to offer" over 10+ years. - Episode agenda: dependency handling differences, module collaboration vs plugin competition, WordCamps "leaving money and organizer sustainability on the table," plus church band and Power Ranger origin stories. - Both host and guest work at Pantheon; matching hoodies unplanned. #### ⏱️ [00:02:08](https://www.youtube.com/watch?v=SXyG-AxjypU&t=128) Miriam's background and deliberate cross-CMS strategy - Developer, WordCamp organizer, speaker, volunteer, attendee — "you name it." - Attending DrupalCon and Drupal Camp Ottawa (twice) because limiting yourself to one CMS isn't good. - Her top takeaway: "more WordPress people need to be going to Drupalcon and vice versa." #### ⏱️ [00:03:24](https://www.youtube.com/watch?v=SXyG-AxjypU&t=204) Drupal vibrancy vs WordPress exhaustion - Developers, PMs, and agency owners at DrupalCon were "really passionate" — versus the "exhaustion in the WordPress community with some of the unfortunate drama over the past couple of years." - Quote: "I saw a genuine excitement for the technology and how they can really make it grow and make it better for everybody." - No gatekeeping toward her WordPress background — people were excited she was dipping her toes in. #### ⏱️ [00:05:18](https://www.youtube.com/watch?v=SXyG-AxjypU&t=318) Composer discipline vs set-and-forget plugins - Main difference "really comes down to the technology": Composer pinning issues and module versioning dominate Drupal troubleshooting. - WordPress plugins are easier to set and forget: "You could just leave it on an old version for decades." - Drupal: "as long as you run your composer update... it's easier to just stay relevant and modern." #### ⏱️ [00:06:20](https://www.youtube.com/watch?v=SXyG-AxjypU&t=380) Collaboration culture vs competition culture - Drupal norm: two SEO module authors collaborate on one better module. WordPress norm: hold the IP, maybe sell the plugin later. - Chris: "that creates more of this competition in the WordPress world and less collaboration" — good for commerce, "maybe not good for the solution." - Drupal CMS recipes (SEO, AI) institutionalize the collectivist pattern; the Drupal marketplace conversation (opened by Dries a year prior) tries to reconcile collectivism with making money. #### ⏱️ [00:08:48](https://www.youtube.com/watch?v=SXyG-AxjypU&t=528) Booth-level reality check - Miriam's DrupalCon conversations were mostly tech support: D10→D11 upgrades, Git workflow issues — not marketplace strategy. - Honest caveat that she saw the event as a sponsor, which bounds her observations. #### ⏱️ [00:09:22](https://www.youtube.com/watch?v=SXyG-AxjypU&t=562) WordCamp origin and career payoff - 2013: manager sends her to the first WordCamp Ottawa. Attends 2013–2015 (Montreal in 2015), first talk in 2016 on multilingual plugins "in the nation's capital which can be a very fiery thing." - Pivoted to organizing, then panels on women in WordPress (2017–2018). - "Word camps have gotten me two of my past jobs" — Canopy Studios and Pantheon — plus network and learning that pushes her. #### ⏱️ [00:11:54](https://www.youtube.com/watch?v=SXyG-AxjypU&t=714) DrupalCon vs WordCamp US as events - From the sponsor floor, DrupalCon looked like WordCamp US when she organized it — "very similar," but "a lot more organized." - Board members walked the floor handing out spare Drupal beers: "that wouldn't have flown" at a WordCamp. #### ⏱️ [00:13:21](https://www.youtube.com/watch?v=SXyG-AxjypU&t=801) The pricing and governance gap - Chris: a ~$1,000 conference and a $50–$100 conference feel identical at the same 1,200–1,500-attendee scale — so flagship WordCamps "can probably charge more." - Drupal Association origin: Dries formed a board so he didn't have to organize DrupalCons himself; DrupalCon revenue pays board positions and funds specific Drupal development. - Proposal: "bump the price up a little bit, pay people to actually event organize," with surplus directed to projects the community cares about. #### ⏱️ [00:16:10](https://www.youtube.com/watch?v=SXyG-AxjypU&t=970) Thankless volunteering and the growth question - Miriam agrees from volunteer-team-lead experience at WordCamp Canada and WordCamp US: "sometimes it just felt thankless." - Giving back feels good, "but if the community doesn't want to embrace it, then it's just going to be dead in the water." #### ⏱️ [00:16:55](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1015) WordCamp Salt Lake City: a succession failure case - Chris did four years of lead/co-lead organizing; after he stepped back, no successor emerged, then COVID — "there hasn't been momentum in the local community since." - Lesson: you need a chain of command and torch-passing, and the labor is "mostly invisible." #### ⏱️ [00:18:04](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1084) The burnout catch-22 - "People burn out so easily when they put so much of themselves into this. And if people are burnt out, they don't want to train the next generation." - Chris adds: long-tenured, cynical organizers are also the wrong trainers even when willing. - Miriam is sitting out organizing WordCamp Vancouver (November) this year — a live example of stepping back. #### ⏱️ [00:19:01](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1141) Church band website: the WordPress origin - Friend's church band (she played clarinet) wanted a site they could update themselves; she was 3–4 years out of college. - Evaluated WordPress, Drupal 5/6, Joomla, Moodle. WordPress won partly because she'd already blogged with it. - Canadian-government job blocked professional use for ~3–4 years; a private-sector WordPress job made it a career — "a happy accident." #### ⏱️ [00:20:39](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1239) Why WordPress stuck: there was always an answer - Chris chose WordPress when freelancing for teachability and because "there was always an answer" — Codex, blogs, somewhere — unlike Joomla and smaller tools. - Miriam: Codex and Stack Overflow were "clutch" as a junior dev; pre-AI, pre-good-Google, they cut trial and error from a week to a day. #### ⏱️ [00:22:20](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1340) Two bands, two instruments, one week - Clarinet ~30 years since grade seven; church band, musical-theater pit orchestras, community bands (joined current one in 2018). - Moved to percussion three years ago — "everything but drum kit": xylophone, vibraphone, crash cymbals, bongos. - Tuesdays percussion (rhythm, no breath control), Thursdays clarinet ("out of breath by the end of the night"). She found her band by Googling "community bands for adults." #### ⏱️ [00:29:21](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1761) Fourth-degree black belt with a Green Ranger origin - 19 years of martial arts; first-degree black belt 2010, started 2007 via cardio kickboxing. - One sensei resembled Jason David Frank (the Green Power Ranger), on whom she'd had a childhood crush — "that probably played a decision." #### ⏱️ [00:31:04](https://www.youtube.com/watch?v=SXyG-AxjypU&t=1864) Katas as procedural programming - Her WordCamp talk ~7 years ago: martial arts and instructing build tech-career confidence. - Katas: "It's in a specific order. It's an orchestrated fight against an imaginary opponent" — like procedural programming, wrong order means things "go belly up" (in karate, injuries). - Chris connects it to code katas and to Tai Chi/aerial arts forcing body awareness. #### ⏱️ [00:34:28](https://www.youtube.com/watch?v=SXyG-AxjypU&t=2068) Teaching adapts like debugging — but people aren't bugs - Teaching pre-teens weekly: read each student — age, learning speed, shy vs bombastic — and adapt. - "It's not so much debugging them. It's kind of like finding the best solution for them." Some need full-kata repetition, others four moves at a time. - "I hate one size fits all." #### ⏱️ [00:35:47](https://www.youtube.com/watch?v=SXyG-AxjypU&t=2147) Tech support as listening discipline - Chris's tech-support years taught empathy and listening that shaped his agency and product work: "The things that people are saying with their words is not always the things that they want or need." - The skill is hearing the clues that something else is going on beneath the stated request. - Miriam: "mad respect" for support staff, especially chat support; triage judgment (help vs escalate) is real work. #### ⏱️ [00:37:40](https://www.youtube.com/watch?v=SXyG-AxjypU&t=2260) Miriam's role at Pantheon - Solutions architect focused on performance improvement; WordPress subject-matter expert. - Episode ends mid-description at ~38:12. ## 📚 References - [Community & Code episode](https://www.youtube.com/watch?v=SXyG-AxjypU) - [Drupal Association](https://www.drupal.org/association) — the funded-governance model discussed - [DrupalCon](https://events.drupal.org) — Miriam attended two weeks before recording - [Drupal CMS recipes](https://www.drupal.org/project/drupal_cms) — the SEO/AI recipe collaboration pattern Chris cites - [WordCamp Central](https://central.wordcamp.org) — WordCamp program and ticket model - [Pantheon](https://pantheon.io) — employer of host and guest ## 🗣️ Paraphrase - Miriam Goldman has spent a decade-plus doing every WordCamp job there is, and she's now intentionally spending time in the Drupal world. What struck her there wasn't the technology first — it was the mood. Drupal folks are excited; WordPress folks, after years of drama, are tired. Technically, the split is Composer-driven currency versus WordPress's decade-old-plugin inertia, and culturally it's Drupal's collaborate-on-one-module instinct versus WordPress's hold-your-IP-and-maybe-sell competition. - The event economics are the sharpest point: DrupalCon and WordCamp US are the same size and feel the same, yet one costs $1,000 and funds a paid association that organizes events and finances development, while the other costs $50 and runs on volunteers who burn out, feel thankless, and don't train successors — which is how WordCamp Salt Lake City died. The back half of the episode traces Miriam's church-band WordPress origin, her two community bands, and her fourth-degree black belt, landing on a shared thesis: teaching karate, doing tech support, and building products all reduce to adapting to the person in front of you instead of one-size-fits-all. ## 📰 Newsletter - Community & Code episode 30 is a WordCamp organizer's field report from the other side: Miriam Goldman (Pantheon, WordCamp Canada organizer) went to DrupalCon and came back with notes WordPress should read. - The spicy take: flagship WordCamps could charge a couple hundred dollars, pay their organizers, and fund community-priority development the way the Drupal Association does — instead of running $50 events on thankless volunteer labor until whole cities lose their camps. - Also inside: why Composer keeps Drupal sites modern while WordPress plugins rot on old versions, why Drupal module authors collaborate where plugin shops compete, and a genuinely delightful digression from clarinet and community bands to how karate katas are procedural programming. - Watch it: https://www.youtube.com/watch?v=SXyG-AxjypU — and if you've ever organized a meetup or camp, the 13:21–19:00 stretch is the part to bring to your next community team conversation. ## ✅ Action Items #### DevRel - Developer advocacy: pitch a "what WordPress can learn from DrupalCon" lightning talk or blog post for the next WordCamp or community team channel, citing this episode's pricing/governance comparison. - Education: fold the "listening for clues beneath the stated request" support framing into DevRel office-hours training — it maps directly to triaging developer questions. - Developer experience: use the Composer-vs-set-and-forget contrast in content about WordPress update hygiene and why abandoned-plugin risk matters. - Developer marketing: cross-CMS presence is underused — evaluate sponsoring or attending a DrupalCon/Drupal camp booth as WordPress-adjacent DevRel, per Miriam's "more WordPress people need to be going to Drupalcon" takeaway. - Community management: invite Miriam Goldman as a guest for a community-sustainability panel or podcast segment — she has organizer-side data points (WordCamp Canada, WordCamp US volunteer lead) and cross-CMS perspective. - Internal/external/cross-project: brief internal stakeholders that organizer burnout and succession failure (the Salt Lake City pattern) is a concrete ecosystem risk, not an abstraction. #### OSPO - Policy & Governance: study the Drupal Association's paid-staff event model as a governance artifact; document the tradeoffs versus the volunteer WordCamp model. - License Compliance: not a focus of this episode; no action. - Security Management: the "leave it on an old version for decades" plugin pattern is a security posture argument — cite it in update-policy guidance. - Software Inventory: no direct action from this source. - Developer Support: none specific. - Community Engagement: consider whether employer sponsorship budgets should cover cross-CMS events, following Pantheon's multi-CMS example. - Strategic Alignment: track the Drupal marketplace conversation as a comparable for WordPress plugin-ecosystem monetization debates. #### Community - Maintainers: the SEO-recipe collaboration model is a template — where two competing WordPress plugins solve one problem, explore a shared-library layer even if products stay separate. - Contributors: document succession explicitly — every camp and meetup needs a named next-lead before the current lead's final year, per the Salt Lake City failure mode. - Sponsors: make the case that higher flagship ticket prices with transparent budgets (paid organizers, project grants) beat sponsor-dependence. - Ecosystem: propose a WordPress↔Drupal community-exchange (mutual ticket/booth swaps at flagship events). #### WordPress - Core: no direct action from this source. - Core Performance: none specific. - Core AI: note Drupal's AI recipe as comparative prior art when discussing bundled AI capabilities. - **Core Program Team:** this episode is direct input for flagship-event pricing and paid-organizer discussions; surface the DrupalCon comparison (same scale, ~10x price, funded association) in community team retrospectives. - Mobile: not applicable to this source. - Playground: not applicable to this source. - Community: pilot a "couple hundred dollar" ticket tier or paid-organizer stipend experiment at one flagship event; measure organizer retention against volunteer-only camps. - Training: build organizer-succession training ("passing the torch") into the WordCamp organizer handbook — burnout prevention framed as pipeline work. - Marketing: the "genuine excitement vs exhaustion" contrast is a warning sign worth qualitative tracking in community surveys. - Support: reuse the "what people say isn't what they need" listening framework in support-team onboarding. - Design: not applicable to this source. - Documentation: the Codex-era "there was always an answer" advantage is worth preserving — audit whether modern docs still deliver that always-an-answer coverage for common junior-dev questions. - Photos: not applicable to this source. - TV: caption quality on community podcasts like this one matters — auto-captions here garble names ("word cavs," "Dre note" for driesnote). - Polyglots: Miriam's first talk was on multilingual plugins in bilingual Ottawa — she's a candidate voice for multilingual community content. - Accessibility: not a focus of this episode; no action. - Meta: not applicable to this source. - CLI: not applicable to this source. - Hosting: Pantheon's multi-CMS positioning shows hosts benefit from staff fluent in both ecosystems; relevant to host-partner conversations. - Tide: not applicable to this source. - Openverse: not applicable to this source. - Themes: not applicable to this source. - Plugins: the competition-vs-collaboration framing belongs in any plugin-ecosystem health discussion, including marketplace/monetization debates. #### The WPCC - Programs: organizer stipends are exactly the microgrant/maintainer-stipend shape this episode argues for — WordCamp organizing is the unfunded labor pool. - Projects: a governance clinic comparing Drupal Association vs WordPress Foundation/Community Team event economics would be a concrete deliverable. - Funding experiments: model "ticket surplus → community project grants" using DrupalCon's flow as the reference implementation. ### FAIR - Technical independence: Drupal's Composer-first dependency model is a useful comparator for FAIR's provenance and update-hygiene arguments. - Policies and covenants: the Drupal Association's funded, chartered event body is prior art for anti-burnout governance structures. - Productized governance artifacts: an "event economics scorecard" (ticket price, paid staff, surplus destination, organizer retention) could make this episode's comparison reusable. ## 🧪 Hypotheses - Flagship WordCamps that raise ticket prices to $200–$300 will retain attendance within 15% while materially improving organizer funding. - Communities with paid event-organizing staff (Drupal model) show higher local-event survival rates after a lead organizer departs than all-volunteer communities. - Plugin ecosystems with strong resale markets (WordPress) produce more duplicated functionality per category than module ecosystems with collaboration norms (Drupal). - Composer-managed sites run currently-supported dependency versions at a significantly higher rate than WordPress sites with manual plugin updates. - Cross-community attendance (WordPress people at DrupalCon and vice versa) increases within-community contributor satisfaction by exposing members to alternative governance models. - Organizer burnout is the primary proximate cause of local WordCamp discontinuation, ahead of venue cost or attendance decline. ### 📊 Methodology - Pricing experiment: A/B a higher-priced ticket tier at one flagship WordCamp; compare registration conversion, demographic mix, and organizer-hours funded against a control camp. - Survival analysis: build a dataset of local WordCamps and Drupal camps 2015–2026 with organizer-transition events; model event survival by governance type (paid staff vs volunteer). - Ecosystem duplication count: sample the top 10 functional categories on WordPress.org and Drupal.org; count actively maintained competing offerings per category. - Update-currency scan: compare dependency freshness between Composer-managed Drupal sites and WordPress sites using host telemetry (e.g., Pantheon fleet data). - Survey: pre/post surveys of cross-CMS event attendees on satisfaction and governance attitudes. ### ❓ Questions - Would a meaningful WordCamp price increase violate the Community Team's accessibility-first ticketing philosophy, or can scholarships preserve it? - Who would employ paid WordCamp organizers — the Foundation, WPCC, a new association, or hosts? - Did the Drupal marketplace conversation Dries opened actually progress in the year since, and what does it decide about collaboration vs monetization? - Is the "exhaustion vs excitement" gap structural (governance, funding) or event-cycle noise following WordPress's public disputes? - What made WordCamp Salt Lake City's succession fail — process absence, or no bench of willing organizers? ### 🔮 Future Research - A comparative economics study of DrupalCon vs WordCamp US budgets (both are partially public) to quantify the "money left on the table." - Longitudinal tracking of local camp revival attempts post-COVID and which governance interventions correlate with success. - Interview series with former lead organizers who stepped away, mapping burnout drivers to fixable structure. ### 💡 Implications - Practice: WordPress community teams should treat succession planning and organizer compensation as sustainability engineering, not culture debates. - Policy: event surplus routing (tickets → paid staff → project grants) is a proven pattern one major CMS already runs; adopting it is an implementation question, not a research question. - Security: set-and-forget plugin culture is a fleet-wide risk argument for stronger update automation defaults. - Education: the katas/debugging/support-listening mappings are usable teaching metaphors for onboarding career changers into tech. - Funding models: collaboration norms and monetization pull in opposite directions; marketplaces (Drupal's proposal) are the current attempted synthesis worth watching. ### 🧠 Learning Styles Assessment - Reading level estimate: conversational transcript, roughly Flesch-Kincaid grade 7–8 (short clauses, informal diction, auto-caption artifacts). #### 👀 Visual learners - Present: nothing — talking-head video with no slides, charts, or screen shares. - Improve: a side-by-side WordCamp/DrupalCon comparison graphic (price, scale, staffing, surplus flow) would carry the core argument in one image. #### 🔊 Aural learners - Present: the entire source is audio-first conversation; strong fit. - Improve: chapter markers at the sustainability segment (13:21–19:00) for relisten targeting. #### 🗣️ Verbal learners - Present: concrete anecdotes (Salt Lake City, church band, Green Ranger) anchor each abstract point. - Improve: define insider terms on first use — driesnote, recipes, D10/D11, Composer pinning. #### 🧩 Kinesthetic learners - Present: nothing hands-on. - Improve: a companion checklist ("audit your local camp's succession plan") would convert the argument to action. #### 🧠 Logical learners - Present: the pricing argument has clean causal structure (same scale + same feel + 10x price → surplus → paid staff → sustainability). - Improve: actual budget numbers; the argument runs on recalled estimates. #### 🧑‍🤝‍🧑 Social learners - Present: podcast format models the cross-community conversation it advocates. - Improve: discussion prompts for community team meetings. #### 🧘‍♀️ Solitary learners - Present: reflective origin-story segments invite self-comparison. - Improve: journaling prompt: "what would make you volunteer to organize — and what would make you stop?" #### 🌿 Naturalistic learners - Present: the burnout/succession discussion is implicitly ecological (community as ecosystem needing regeneration). - Improve: make the ecosystem-health framing explicit — organizer pipelines as soil health. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: standard YouTube watch page semantics; episode framing spoken aloud. - Improve: a written show-notes page with proper heading structure and named links would help non-visual triage. #### Keyboard navigation - Present: YouTube player keyboard controls. - Improve: not applicable beyond the platform; no custom UI in the source. #### Contrast and readability - Present: not applicable to evaluate from transcript; no on-screen text reported. - Improve: any future comparison graphics should meet 4.5:1. #### Text resizing and reflow - Present: platform-managed. - Improve: none specific to this source. #### Media and captions - Present: auto-generated captions only, with meaningful errors ("word cavs" for WordCamps, "Dre note" for driesnote, "Tiffany" for timpani, "vibrophone" for vibraphone). - Improve: human-corrected captions and a downloadable transcript; name-dense community content is where auto-captions fail hardest. #### Forms and interactions - Present: not applicable — no forms in this source. - Improve: none. #### Standards reference - Caption accuracy gaps map to WCAG 2.2 SC 1.2.2 (Captions, Prerecorded); missing transcript maps to SC 1.2.1/1.2.3 (Media Alternative). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Canadian perspective (Ottawa, Calgary, WordCamp Canada) balances the usual US-centric WordPress lens; bilingual-Ottawa multilingual-plugin anecdote. - Improve: the cross-CMS comparison could extend beyond North American flagship events. #### Inclusive language - Present: conversational and respectful throughout; no othering of either community. - Improve: expand insider jargon for newcomers (driesnote, recipes, pit orchestra). #### Neurodiversity support - Present: clear segment shifts; anecdote-anchored structure aids retention. - Improve: chapters/timestamps in the video description; corrected captions. #### Representation - Present: a senior technical woman as the featured expert; she references organizing women-in-WordPress panels (2017–2018). - Improve: the sustainability discussion could name how volunteer-only models disproportionately exclude people without discretionary time. #### Psychological safety - Present: burnout is discussed candidly and without blame; Miriam's boundary-setting (sitting out organizing this year) is modeled positively. - Improve: none needed; this is a strength of the episode. ### ✅ Logical Validity #### Strong reasoning - Analogical (13:21–16:09): same scale + same event feel + 10x price differential → WordCamps underprice. The analogy is disciplined because Chris attended both and controls for event quality; clarifying with real budget figures would strengthen it. - Causal chain (16:55–18:45): departure without successor → stall → COVID → permanent momentum loss (Salt Lake City), generalized by Miriam's burnout catch-22. Concrete case plus mechanism is solid inductive form. - Inductive (05:18–06:19): Composer forces updates, plugin model permits decade-old versions — grounded in her direct support conversations at the booth. #### Fallacies - Hasty generalization risk (03:24–05:16): "vibrant Drupal vs exhausted WordPress" rests on one sponsored-booth visit; Miriam partly mitigates by flagging her limited vantage ("I was mainly just at the Pantheon booth"). Fix: triangulate with contributor surveys. - Anecdotal evidence (11:15): "WordCamps got me two jobs" supports the personal-value claim but can't establish the general career-value claim without base rates. Fix: cite community survey data on hiring via events. - Appeal to novelty/enthusiasm (mild, 07:45–08:11): recipes framed as better because collaborative and fresh; the monetization tension is acknowledged, which largely defuses it. #### Tone of voice - Warm, candid, self-deprecating ("I'm horrible at slides"), and mutually curious; critique of WordPress structures is delivered as insider concern, not attack ("sometimes it just felt thankless... to be perfectly honest"). ### 🛡️ DARVO Analysis - Deny: none observed — speakers volunteer their own limitations (booth-only vantage, unwatched driesnote) rather than minimizing. - Attack: none — the "WordPress drama" is referenced without naming or blaming individuals. - Reverse victim/offender: not applicable to this source — a collegial interview with no accusations or defensive posture to invert. - Emotional cues are earnest (excitement, exhaustion, gratitude toward band teachers); no manipulative rhetoric detected. ## 🎯 Conclusion - Bottom line: the WordPress and Drupal communities are near-twins in feel and scale but opposites in event economics and collaboration norms — and the WordCamp volunteer model is visibly failing its organizers via thankless labor, burnout, and broken succession, while the Drupal Association model shows a working alternative at the same scale. - Next steps for readers: bring the DrupalCon pricing comparison into WordCamp/community-team discussions; write a succession plan for any event you help run before you need it; attend one event outside your CMS this year; and steal the episode's people lessons — adapt to the learner, and listen past what people literally say. ## 🔄 Refactor Appendix — Episode 30: Miriam Goldman > 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] Drupal community radiates excitement while WordPress shows exhaustion > [!quote] ID:rw_pending > I saw a genuine excitement for the technology and how they can really make it grow and make it better for everybody. **Context & use**: - ~03:57, Miriam contrasting DrupalCon's mood with post-drama WordPress fatigue. - Community-health signal: affect is a leading indicator for contributor retention — useful in DevRel survey framing. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### [H2] WordPress plugin IP culture breeds competition over collaboration > [!quote] ID:rw_pending > that creates more of this competition in the WordPress world and less collaboration **Context & use**: - ~07:33, Chris contrasting Drupal's shared-SEO-module norm with WordPress authors holding sellable IP. - Core tension for any plugin-marketplace or ecosystem-health argument; pairs with Drupal CMS recipes as the counter-model. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ### [H3] Flagship WordCamps underprice tickets and underfund organizers > [!quote] ID:rw_pending > bump the price up a little bit, pay people to actually event organize **Context & use**: - ~16:00, Chris's proposal after noting DrupalCon (~$1,000) and WordCamp US (~$50–100) feel identical at the same scale. - The episode's sharpest actionable claim — direct input for community-team event-economics discussions. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### [H4] Organizer burnout blocks training the next generation > [!quote] ID:rw_pending > people burn out so easily when they put so much of themselves into this **Context & use**: - ~18:28, Miriam naming the catch-22 right after Chris's WordCamp Salt Lake City succession-failure story. - Explains why local camps die: the people best positioned to train successors are the least able to. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### [H5] Karate katas mirror procedural programming's ordered logic > [!quote] ID:rw_pending > It's an orchestrated fight against an imaginary opponent. **Context & use**: - ~31:25, Miriam's WordCamp-talk thesis that martial arts practice maps to tech thinking. - Reusable teaching metaphor for onboarding career changers; connects to the "code kata" tradition Chris cites. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Volunteer-run events die without funded succession structures **Claim** (one sentence, Courtney's voice): Community events that run entirely on unpaid labor collapse when a lead departs, because burnout removes both the organizer and the training of their successor. **Evidence pointer**: [[#H3]] and [[#H4]] — the DrupalCon funded-association contrast plus the Salt Lake City case. **Scope & conditions**: Holds for recurring volunteer-led events at meaningful scale; breaks where institutional sponsors or paid staff absorb continuity risk, or for one-off events with no succession need. **Links** (≥1 with annotation): - [[Open source sustainability]] — because extends - [[WordCamp organizing]] — because applies-in flagship and local event planning - [[Drupal Association model]] — because contrasts on funding structure <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Watch this year's driesnote for the Drupal marketplace follow-up Chris hadn't seen yet — https://events.drupal.org #fleeting #inbox - [F2] Check whether WordCamp Canada/Vancouver (November) publishes its organizer structure — live test of the succession discussion #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a WordCamp event-economics comparison note (DrupalCon pricing/governance vs flagship WordCamps) for community team conversations — from Community & Code ep. 30 #things - [ ] Watch the latest driesnote for Drupal marketplace progress before citing the collaboration-vs-monetization framing — https://events.drupal.org #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Episode 30 Miriam Goldman.md|Episode 30: Miriam Goldman by Chris Reynolds]] ## Highlights - the unfortunate drama over the past couple of years. I didn't see that in Drupal. I saw a genuine excitement for ([View Highlight](https://read.readwise.io/read/01kxsdy1dpk26pnvckebpfzg5r)) - Note: H1 (~3:57) — the episode's central contrast: DrupalCon radiates genuine excitement while WordPress shows post-drama exhaustion. - Tags: atom/literature/h1 - point. Um, so that creates more of this competition in the WordPress world and less collaboration, which is good for ([View Highlight](https://read.readwise.io/read/01kxsdy3qf0s59rm6ktj0nzx0r)) - Note: H2 (~7:33) — WordPress plugin IP culture breeds competition over collaboration, contrasted with Drupal's shared-SEO-module norm. - Tags: atom/literature/h2 - bit, pay people to actually event organize and then also maybe have some ([View Highlight](https://read.readwise.io/read/01kxsdy62xqv0fj6tn4t860422)) - Note: H3 (~16:00) — the funding proposal: raise WordCamp ticket prices and pay organizers (DrupalCon feels identical at ~10x the price). - Tags: atom/literature/h3 - what happens. But it's just people burn out so easily when they put so much of ([View Highlight](https://read.readwise.io/read/01kxsdy8fwjjthyf8n0a70k9e5)) - Note: (~18:28) — the burnout catch-22: burnt-out organizers can't train the next generation; follows the WordCamp SLC succession-failure story. - Tags: atom/literature/h3 - order. It's an orchestrated fight against an imaginary opponent. ([View Highlight](https://read.readwise.io/read/01kxsdyazmpkb3mf6ysqy90an1)) - Note: (~31:25) — Miriam's WordCamp-talk thesis: karate katas as procedural programming; a memorable teaching analogy. - Tags: atom/literature/h3