Perspectives with Sé Reed (Crossword S11E06)

Perspectives with Sé Reed (Crossword S11E06) ![rw-book-cover](https://crossword.fm/og-image.jpg) 🔗 **Source:** [Perspectives with Sé Reed (Crossword S11E06)](https://crossword.fm/s11/e06/) > [!note]+ Document Notes > tags: [wordpress-governance, wpocc, contributor-economics, open-source-accountability, community-leadership, five-for-the-future] > author: Jonathan Wold & Luke Carbis (hosts), with Sé Reed > source: Crossword (crossword.fm) S11E06 > reference: https://crossword.fm/s11/e06/ > date created: 2026-08-22 09:15 > > > [!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. > > # 🏷️ Title: Perspectives with Sé Reed (Crossword S11E06) >  ## 🧭 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 - [Crossword S11E06 — Perspectives with Sé Reed](https://crossword.fm/s11/e06/) - The WP Open Community Collective (referenced throughout as "WPCC" / "WP Community Collective" — the pre-rebrand name in use at recording time) - WP Watercooler podcast (12-year run, now concluded) - WordPress.org `/contribute` page and the Get Involved dashboard tab (Sé's marketing-team work) - Five for the Future; WPCS (WordCamp Community Support) as the for-profit entity running WordCamps - The Automattic / WP Engine litigation (ongoing, referenced as the pending variable) > [!note] Naming: the episode predates or ignores the 2026-07-24 rebrand and says "WPCC" > throughout. Quotes preserve that verbatim; this analysis uses **The WPOCC** elsewhere. > Sé herself argues the "WP" is deliberate — untrademarkable, and standing for the wider > ecosystem rather than the WordPress mark. ## 📝 Summary - **What happened.** Sé Reed — WordPress contributor, former Marketing team rep, 12-year WP Watercooler host, and now CEO of The WPOCC — talks with Jonathan Wold and Luke Carbis about being named in Matt Mullenweg's "JK Press" post and having her WordPress.org Slack account deactivated (January 2025), her reactivation in the May 2025 "Jubilee," and her current status: unable to attend WordCamps and, she says, instructed not to discuss why. The conversation widens into contribution economics, whether leadership can exist without accountability, and what The WPOCC is actually building. - **Why it matters.** This is a rare first-person account from someone directly sanctioned in the 2024–25 governance conflict, paired with a working theory of how to fund open-source contribution sustainably. Two ideas do real work: contribution standardization as a *precondition for corporate participation*, and the WPOCC's AI fellowship reframed as **"DevRel for AI"** — a community-facing translation layer for what the Core AI team is shipping. - **Key stakeholders.** Sé Reed and the other deactivated contributors (Joost de Valk, Karim Marucchi, Heather Burns, Morten Rand-Hendriksen); The WPOCC's members and board; Matt Mullenweg / Automattic / the WordPress Foundation; sponsoring companies (Elementor and GoDaddy Pro named positively); every contributor deciding whether and how to keep contributing while the litigation is unresolved. - **Risks and tradeoffs.** This is one side of a live, litigated dispute, told by a person who says she was harmed by it and who is legally constrained in what she can say — she states explicitly that she cannot explain her WordCamp exclusion. No response from Mullenweg, Automattic, or the Foundation appears. The hosts push back at several points (Luke on accountability, Jonathan on altruism-vs-ROI), which keeps it from being purely one-voiced, but it remains a partisan account and should be cited as testimony rather than established fact. - **Bottom line.** The durable content isn't the conflict narrative — it's the structural argument: that contribution failed to scale not because companies lacked goodwill but because **unstandardized contribution can't survive a boardroom**, and that a member-governed intermediary can supply the standard, the pay scale, and the corporate-legible credit that individual contributors can't produce for themselves. ## 📖 Main Content - **The deactivation, in her account.** Her `.org` Slack account was deactivated roughly two days *before* the JK Press post named her, with no notification — she noticed a warning icon in Slack's sidebar. She was reactivated in May 2025 as part of the "Jubilee" and attended WordCamp Europe that year. She is not attending WordCamps now and says she was told that explaining why would create "additional issues." She denies the substance of what she was accused of: not collaborating with Joost and Karim, not planning a fork, not in contact with them at all. - **Why WP Watercooler ended after twelve years.** Not audience decline — an integrity problem. The show's premise was "contribute, get involved," and the hosts found themselves unable to make that pitch without caveats. Her framing: they didn't want to be haters, but couldn't honestly promote contribution while attaching a warning that you might be treated badly. "We knew too much." - **The WPOCC's legal and economic structure.** Founded 2022 as a fiscally-sponsored project; became an independent California **mutual benefit organization** in December 2024, working toward **501(c)(6)** status. Sé explains the choice: 501(c)(3) public-charity status is a poor fit because the IRS has not accepted open source as a valid public good, and you can't straightforwardly pay people to write code under that designation. A (c)(6) can advocate for members and the industry. - **The AI fellowship, framed as DevRel.** Members are being consulted via a members-only GitHub repo on the fellowship's framework, pay scale (their "open source pay contributor standard"), and expected outputs. The rationale: practitioners outside the insular contributor community can't track everything — connectors, MCP framework, what's in or out of a release — and need someone both translating it *and* representing community interests. Her assessment of the AI team's own posts is pointed: "of arguable use, arguable benefit," and (per Luke, agreed to) largely AI-written. - **The stewardship→ownership "bait and switch."** She recounts asking Mullenweg years ago about his post-life plan for WordPress and being told it was in his will — which she read as stewardship. Her claim is that the WP Engine conflict revealed ownership instead, converting volunteer labor from a contribution to a commons into a contribution to an individual who is already "post-economic." - **The contribution-pipeline guilt.** As Marketing team rep she built the Get Involved dashboard tab and the `/contribute` page with a team-recommendation quiz. She now says she feels "personally guilty" for it — having built a better funnel into what she characterizes as exploited labor, including toward WordCamps run by WPCS, a for-profit entity, not the Foundation. - **Leadership vs. accountability (the episode's sharpest exchange).** Sé: accountability is constitutive of leadership; without it you have dictatorship. Luke disagrees on definitions — dictators do have followers — but concedes he wouldn't *follow* an unaccountable leader. Both land on a shared point about visibility: feature "blessings" happen, the term is literal and real, but not in public. Luke's specific complaint is that the release lead's role changed to big-picture-only without any public memo. - **Standardization vs. serendipity.** Luke argues for leaning into contribution that doesn't make financial sense — altruism as the basis. Jonathan argues you can't rely on altruism and must connect contribution to a bottom line. Sé's synthesis is the WPOCC's actual model: occupy the gray area — pay contributors standard rates with clear deliverables, then supply the sponsoring company the public credit and accolades, so the contributor isn't also doing marketing for their funder. ### 🗒️ Notes - The most transferable insight is organizational, not political: companies that *want* to contribute often can't, because a sponsored contributor has no team, no ROI story, and no consistent reporting. Sé's diagnosis is that variability is the blocker — "how do you make it make sense in a boardroom, or in a monthly report." The WPOCC exists to absorb that variability and emit something corporate-legible. - Her point about single-person dependency is worth extracting on its own: corporate contribution programs frequently rest on one internal advocate, and vanish when that person changes roles or leaves. She and Luke both cite Elementor as a positive case; Luke's WP Engine experience is offered as an example where the program worked while he held it and gapped after he left. - The "post-economic" exchange is a genuine disagreement worth flagging: Luke wants plain language ("very rich"); Sé insists the term points at something else — a coming condition where, for many people, there may be no economy to participate in. That's an AI-labor claim smuggled into a governance conversation, and neither host follows it up. - Sé explicitly decouples herself from the organization — "I am not synonymous with the WPCC" — in response to the hosts' question about whether her persona-non-grata status contaminates other WPOCC people. That's a deliberate governance statement about the org surviving its founder's standing. - The episode is unusually candid about legal constraint. She repeatedly signals there is more she cannot say. Read the silences as structural, not evasive — but also as a reason this cannot be treated as a complete account. ## 📚 References - [Crossword S11E06 (primary)](https://crossword.fm/s11/e06/) — full transcript published alongside the audio. - The WP Open Community Collective — membership, fellowships, the open-source pay contributor standard; the contributor appreciation campaign run with GoDaddy Pro is named. - The WordPress.org `/contribute` page and Get Involved dashboard tab — Sé's own prior work, now the subject of her stated regret. - No opposing-party sources are cited or sought; claims about deactivation timing, instructions not to discuss WordCamp exclusion, and the will conversation are single-sourced to Sé. ## 🗣️ Paraphrase - Sé Reed was deactivated from WordPress.org Slack days before a post naming her, reinstated months later, and is currently unable to attend WordCamps for reasons she says she's not permitted to explain. - She ended a twelve-year podcast because she could no longer tell people to contribute without warning them about how they might be treated. - The WPOCC is a California mutual benefit organization heading for 501(c)(6), deliberately not a charity, because US nonprofit law doesn't treat open source as a public good you can pay people to produce. - Its next fellowship is on AI, designed with member input, and is essentially DevRel: translating what the Core AI team ships for practitioners who can't follow every post, while representing community interests in that process. - She argues the WP Engine conflict converted WordPress from something stewarded to something owned, which retroactively changed what volunteers had been donating their labor to. - She regrets building the contribution funnel, calling it a better pipeline for exploited labor. - On leadership: accountability isn't a nice-to-have, it's what distinguishes leadership from dictatorship — Luke disputes the definition but agrees he wouldn't follow one. - The WPOCC's economic bet is that contribution has to be standardized and credited to be corporately fundable — altruism alone can't carry it, but pure ROI-thinking misses it too. ## 📰 Newsletter - **Lead:** Sé Reed's first extended interview since the deactivation, and it's more useful than the conflict framing suggests. Yes, she walks through being named in the JK Press post and finding her `.org` Slack account already dead two days earlier — but the substance is what she's building now. - **The structural argument worth your time:** corporate contribution didn't stall because companies are indifferent. It stalled because a sponsored contributor doesn't fit anywhere — no team, no ROI story, no consistent reporting — and "make it make sense in a boardroom" is a real constraint. The WPOCC's model is to absorb that: pay contributors standard rates with defined deliverables, then hand the sponsor the public credit, so the contributor isn't also doing marketing for their funder. - **For anyone in DevRel:** their next fellowship is explicitly *DevRel for AI* — a translation layer between what the Core AI team ships (connectors, MCP, whatever lands next release) and practitioners who can't track it, plus someone representing community interests in that conversation. That's a job description a lot of us have argued should exist. - **The exchange to actually listen to** is Sé and Luke on whether leadership requires accountability. She says no accountability means dictatorship, not leadership. He pushes back on definitions, then concedes he wouldn't follow such a leader. They converge on the practical version: feature "blessings" are real and the term is literal, but they don't happen anywhere you can see them. - **Caveat worth stating:** this is one side of live litigation, from someone who says she's constrained in what she can say and who gets no counterpoint from Automattic or the Foundation in the episode. The hosts do push back, which helps. Cite it as testimony. ## ✅ Action Items #### DevRel - Developer advocacy: the "DevRel for AI" framing is directly usable — a named, fundable role translating Core AI output for practitioners *and* carrying community interests back upstream. Worth watching how the WPOCC scopes the fellowship, since it's close to a job spec. - Education: Sé's point that the AI team's posts are "of arguable use" to non-insiders is a concrete content gap — release-cycle explainers aimed at agencies and their clients, not at contributors. - Community management: the single-advocate fragility pattern (programs die when one internal champion leaves) is worth designing against explicitly in any program you build. #### OSPO - Policy & Governance: the 501(c)(3) vs 501(c)(6) reasoning is a genuinely useful reference — the IRS not treating open source as a payable public good is a structural constraint shaping what open-source orgs can legally do. - Community Engagement: the "open source pay contributor standard" is worth tracking as prior art for anyone standardizing sponsored-contributor compensation. - Strategic Alignment: the core claim — unstandardized contribution can't be justified in corporate reporting — is a direct argument for why OSPOs exist. #### Community - Maintainers: the WP Watercooler shutdown is a real case of advocacy becoming untenable when you can't honestly recommend participation. Worth sitting with before writing the next "get involved" push. - Sponsors: the credit-and-accolades model (contributor gets paid a standard rate; sponsor gets public recognition) is a concrete alternative to expecting contributors to market their funders. - Ecosystem: WPCS owning WordCamps rather than the Foundation is a factual point many contributors don't know; it changes what "volunteering for WordCamp" means. #### WordPress - **Community:** directly relevant — contributor onboarding, the `/contribute` funnel Sé built and now regrets, and what the team owes people it recruits. - **Core:** the release-lead accountability question (role changed to big-picture with no public memo; who "blesses" feature additions and where) is a live process-transparency gap the team could simply document. - **Core AI:** the sharpest actionable critique here — that the AI team's communications don't reach or serve practitioners outside the contributor bubble. An outside org is staffing a fellowship to fill that gap. - **Marketing:** the marketing team's dissolution is referenced in passing ("the now defunct marketing team") by its former rep; relevant context for anyone reconstructing that history. - **Training:** contribution onboarding material is downstream of the `/contribute` pipeline discussed here. - Not applicable to this source: Core Performance, Core Program Team, Mobile, Playground, Support, Design, Documentation, Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse, Themes, Plugins — the episode doesn't touch these. #### The WPOCC - **Highest-relevance section of this note.** Primary-source detail on structure (California mutual benefit org, Dec 2024; 501(c)(6) in progress), the member-governed model (members-only GitHub, input on fellowship framework and pay scale), the AI fellowship rationale, the pay standard, and the sponsor-credit model. If you're tracking or involved with the org, this is the most substantive public account of its operating theory to date. - Also note the governance signal: Sé explicitly separating her personal standing from the organization's, in direct response to whether her status endangers other members. #### FAIR - Adjacent rather than direct. The underlying question — what happens to contributed labor when the thing contributed to turns out to be owned rather than stewarded — is the motivating concern behind federation efforts. No FAIR-specific content in the episode. ## 🧪 Hypotheses - H1: Standardized contribution terms (defined rate, deliverables, reporting) increase corporate sponsorship of open-source contributors relative to ad-hoc arrangements, independent of company goodwill. - H2: Corporate contribution programs dependent on a single internal advocate have materially shorter lifespans than those with institutional mandate — testable against WordPress sponsor histories. - H3: Publicly crediting the sponsoring company (rather than expecting the contributor to promote them) increases sponsor retention and reduces contributor burnout. - H4: Contributors who learn that WordCamps are run by a for-profit entity rather than the Foundation report reduced willingness to volunteer — i.e. the structural facts, once known, change behavior. - H5: Communications written primarily for contributors systematically fail practitioners, measurable as a gap between release-note readership and downstream agency/client awareness of the same features. ### 📊 Methodology - **What this source is:** a single long-form interview, published with a full transcript. No documents, data, or corroborating sources are presented; the factual claims (deactivation timing, the instruction not to discuss WordCamp exclusion, the will conversation, WPCS ownership of WordCamps) rest on Sé's testimony. - **Strengths:** unusually specific on dates and legal structure; the hosts push back rather than accepting every framing; the transcript lets claims be quoted precisely. - **Limitations:** one-sided by construction — no response sought from Mullenweg, Automattic, or the Foundation; the subject states she is legally constrained, so the account is knowingly incomplete; and the litigation is unresolved, so several claims may be revised by its outcome. - **To test H1/H2/H3:** interview sponsored-contributor program managers across WordPress companies, coding each program for standardization, credit model, and dependence on individual advocates, then compare against program longevity and headcount stability. ### ❓ Questions - What exactly did the WPOCC's 501(c)(6) application require, and what does the "open source pay contributor standard" specify in numbers? - What are the fellowship's actual deliverables, and how will the org measure whether "DevRel for AI" worked? - Who does bless feature additions now, and is there any record of it? Luke's question appears to still be unanswered publicly. - If the release lead's role formally changed, where was that documented — Luke says he never saw a memo, and neither did Matthias. - How does the WPOCC's advocacy function survive if its CEO cannot attend the community's main gatherings? - What did the other named contributors (Heather Burns, Morten Rand-Hendriksen) experience — Sé says she doesn't know whether they were reactivated. ### 🔮 Future Research - A structural comparison of open-source funding intermediaries (WPOCC, Open Collective, tidelift-style models, foundations) on legal form, contributor pay standards, and corporate legibility — the (c)(3)/(c)(6) constraint Sé describes likely generalizes well beyond WordPress. - A study of contribution-pipeline ethics: what obligations does a project incur toward people it actively recruits through official onboarding surfaces, and what disclosure (e.g. who owns WordCamps) belongs in that funnel? - Longitudinal tracking of whether "DevRel for AI" as a funded role actually closes the practitioner-awareness gap, using release-feature awareness surveys before and after. ### 💡 Implications - **Practice:** if you run or fund a contribution program, the standardization and public-credit mechanics here are directly copyable, and the single-advocate fragility is a specific failure mode to design against. - **Policy:** the IRS's treatment of open source shapes what open-source organizations can legally do with money. That's an under-discussed constraint on the entire funding conversation, and it favors trade-association forms over charities. - **Security:** not applicable to this source. - **Education:** the practitioner-vs-contributor communication gap is an instructional-design problem as much as a DevRel one — same information, different audience model. - **Funding models:** the central bet is that altruism and ROI aren't opposites but need an intermediary to translate between them. Whether that holds is the WPOCC's actual thesis and is empirically testable over the next few years. ### 🧠 Learning Styles Assessment - Reading level estimate: conversational, roughly Flesch-Kincaid grade 8–10, but with high assumed context — the JK Press post, the Jubilee, Five for the Future, WPCS, and the litigation are all referenced without explanation. A newcomer would be lost; an insider will find it dense with signal. #### 👀 Visual learners - Present: none — audio plus transcript only. - Improve: a timeline graphic (2022 founding → Dec 2024 independence → Jan 2025 deactivation → May 2025 Jubilee → current status) would make the sequence legible at a glance; it currently has to be assembled from scattered mentions. #### 🔊 Aural learners - Present: strong — this is natively a podcast, and the interruptions, hesitations, and tonal shifts carry meaning the transcript flattens. - Improve: none needed; this is the format's home turf. #### 🗣️ Verbal learners - Present: strong — full transcript published alongside the audio, which is both an accessibility win and what made this deep-read possible. - Improve: speaker labels are present and consistent; nothing significant to fix. #### 🧩 Kinesthetic learners - Present: minimal — nothing to do or try. - Improve: the WPOCC's members-only GitHub is where the actionable participation lives, but it isn't linked or described concretely enough to act on. #### 🧠 Logical learners - Present: the accountability/leadership exchange is genuinely argumentative — a claim, a counter-definition, a concession, and a reframe — and rewards close reading. - Improve: the contribution-economics argument is scattered across the back half; it would benefit from being stated once as a premises-and-conclusion structure. #### 🧑‍🤝‍🧑 Social learners - Present: strong — three-way conversation with real disagreement, not an interviewer feeding prompts. - Improve: no listener discussion venue is surfaced in the transcript. #### 🧘‍♀️ Solitary learners - Present: self-contained if you already have the context. - Improve: a linked primer on the referenced events would make it navigable alone. #### 🌿 Naturalistic learners - Not applicable to this source — no ecological or environmental dimension. - Improve: not applicable. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: **a full published transcript with consistent speaker labels** — the single most important accessibility decision a podcast can make, and it's done here. - Improve: verify the transcript uses real heading structure rather than styled paragraphs on the live page (not determinable from the scrape). #### Keyboard navigation - Present: standard episode page with an audio player. - Improve: confirm the player's controls are keyboard-operable and labelled — a common failure point for custom podcast players. #### Contrast and readability - Present: not independently verifiable from scraped text. - Improve: check live page. #### Text resizing and reflow - Present: not assessable from scraped content; long transcript paragraphs should reflow without issue. - Improve: not assessable. #### Media and captions - Present: the transcript functions as the audio alternative (WCAG 1.2.1), which is the key requirement here and is satisfied. - Improve: no chapter markers or timestamps in the transcript — for a ~9,000-word conversation, timestamped sections would substantially aid navigation for everyone, and especially for anyone returning to a specific claim. #### Forms and interactions - Present: none evident in the scraped content. - Improve: not applicable. #### Standards reference - Strong on **1.2.1 Audio-only alternative** (full transcript provided). The main gaps to verify on the live page are audio-player keyboard operability and transcript heading semantics; the absence of timestamps is a usability rather than conformance issue. ### 🌍 DEIB Assessment #### Cultural breadth - Limited by scope — a US-centric conversation (IRS designations, California incorporation, WordCamp US), though it references WordCamp Asia and Europe in passing. #### Inclusive language - Present: no exclusionary language identified. Sé's aside about the "Get Involved" vs "Contribute" wording decision is a small, genuine example of inclusive-language work in practice — "contribute" reading as a request for money. #### Neurodiversity support - Present: the transcript allows self-paced reading rather than requiring audio processing. - Improve: no summary, chapter markers, or section headings within a very long transcript; that's a real barrier for anyone who needs structure to navigate long-form content. #### Representation - Present: the episode centers a woman describing sanction and reputational harm within an open-source community — a perspective that is frequently discussed *about* rather than *by* the affected person. The hosts largely let her frame her own experience. - Improve: the other named contributors' experiences are absent, and Sé notes she doesn't know what happened to two of them. #### Psychological safety - **The episode's central subject, in effect.** Sé's account of ending WP Watercooler — being unable to recruit contributors without warning them they might be mistreated — is a direct statement that the community was not psychologically safe to recommend. The hosts handle her legal constraints without pressing her past what she can say, which is appropriate. - Worth naming: a community where a contributor believes discussing her own exclusion will trigger "additional issues" has a psychological-safety problem independent of who is right about the underlying dispute. ### ✅ Logical Validity #### Strong reasoning - **The corporate-contribution argument is genuinely well-constructed.** Sé identifies a mechanism (sponsored contributors have no team, no ROI story, no consistent reporting), explains why goodwill doesn't overcome it (boardrooms and monthly reports require legibility), and proposes a fix that addresses the mechanism rather than the sentiment (standardize the terms, relocate the marketing burden to the org). It's the most transferable reasoning in the episode. - **The accountability argument survives its own counterexample.** Luke's objection — dictators do have followers — is a real hit on her definition, and rather than dig in she reframes: leadership-in-the-world clearly exists without accountability; leadership *worth following* does not. Luke then independently arrives at the same place. That's an argument improving under pressure. - **The single-advocate fragility claim is well-evidenced by both participants** from different vantage points (Sé from conversations with sponsor companies, Luke from his own WP Engine tenure and the gap after he left). #### Fallacies - **Motivated reinterpretation of a single data point.** The "it's in my will" exchange is doing heavy lifting as evidence that Mullenweg once held a stewardship rather than ownership posture — but a will is precisely an instrument of *ownership*, and she acknowledges "it could be just the impression that I got." The conclusion (a bait-and-switch occurred) may still be right on other grounds; this particular support doesn't carry it. **Fix:** rest the claim on public statements and structural facts rather than a private conversation's inferred tone. - **Loaded framing presented as description.** "A better pipeline for exploited labor" characterizes all contribution recruited through `/contribute` as exploitation, which doesn't follow from the specific grievance (that WordCamps are run by a for-profit and the project is individually owned). Many contributors get real, non-exploitative value from contributing. She's describing her own retrospective feeling, but it's phrased as a fact about the pipeline. **Fix:** scope it — the disclosure problem is real without the totalizing claim. - **Unfalsifiable-by-construction claims, honestly flagged.** Several key assertions (why she can't attend WordCamps, what she was told) cannot be checked because she says she's constrained from explaining. She flags this rather than hiding it, which is to her credit, but a reader should still register that these are load-bearing and unverifiable. #### Tone of voice - Candid, wry, self-deprecating, occasionally raw. She interrupts herself, jokes through difficult material, and volunteers unflattering self-assessments (the contribution-funnel guilt). The hosts are warm but not deferential — Luke actively disputes her framing twice. The overall register is a genuine conversation among people who disagree productively, not an advocacy interview. ### 🛡️ DARVO Analysis - **Partially applicable, and worth analyzing carefully.** DARVO describes how an *accused party* responds to accusation: deny, attack the accuser, reverse victim and offender. Here Sé is the accused party (named in a post, deactivated), so the framework is at least structurally relevant. - **Deny:** she does deny — specifically and narrowly. "I was not collaborating with Joost and Karim. I was not planning a fork. I wasn't even talking to Joost and Karim." These are falsifiable factual denials of specific allegations, not diffuse minimization, which is the opposite of the DARVO pattern. - **Attack:** she criticizes Mullenweg's accountability and the project's governance, but the criticism is about conduct and structure rather than an attempt to discredit the accuser's standing to accuse. She also repeatedly grants nuance ("there's certainly nuance"), credits changes she approves of (featured plugins), and Jonathan's counterpoint that Matt likely believes he's doing right goes unchallenged. - **Reverse victim/offender:** she does claim harm ("it has remarkably affected my reputation," "I don't deserve what happened to me"), but does not claim the other party is the true aggressor in a way that inverts roles — and notably she declines to extend her grievance to the organization she leads ("I am not synonymous with the WPCC"). - **Assessment: this does not fit the DARVO pattern.** The denials are specific and checkable-in-principle, the criticism is conduct-directed, and the harm claim is proportionate and self-limited. Worth stating plainly because the framework *could* be lazily applied to any sanctioned person defending themselves — the analysis has to distinguish "defending oneself" from "DARVO," and this reads as the former. ## 🎯 Conclusion - **Bottom line:** the conflict narrative will get the attention, but the durable content is a working theory of why open-source contribution didn't scale — not insufficient goodwill, but insufficient legibility. Companies that wanted to contribute couldn't fit a sponsored contributor into a team, a report, or an ROI story, and The WPOCC's bet is that a member-governed intermediary can supply the standard, the pay scale, and the corporate-facing credit. Its AI fellowship is that bet applied to the most urgent current gap: nobody is translating what Core AI ships for the practitioners who'll have to live with it. - **Practical next steps:** (1) if you fund or run contribution programs, steal the mechanics — standard rates, defined deliverables, sponsor gets the public credit, contributor doesn't do the marketing; (2) audit any program you run for single-advocate dependency, the failure mode both participants independently identified; (3) if you're in DevRel, treat "DevRel for AI" as a role spec worth arguing for wherever you are, not just at the WPOCC; (4) treat the factual claims as testimony from a constrained, partisan, uncontested source — the structural arguments stand on their own merits and don't require accepting the conflict narrative; (5) for anyone tracking The WPOCC specifically, this is the most substantive public account of its operating model so far and worth revisiting once the fellowship's outputs exist. ## 🔄 Refactor Appendix — Perspectives with Sé Reed > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Resonance filter applied — 4 atoms, 2 Permanent candidates. ### 📚 Literature Atoms (H3) #### Accountability is what separates leadership from dictatorship > [!quote] ID:rw_1 > No, you can't. It's dictatorship. Without any accountability, you do not have leadership, because leadership is about people choosing to follow you. **Context & use**: - The episode's sharpest exchange; Luke contests the definition and then independently concedes the practical version. - Reusable framing for any governance conversation where "leadership" is invoked without a mechanism for answering to anyone. **Tags**: #xref #aphorisms  #### The contribution funnel recruited into an ownership she didn't disclose > [!quote] ID:rw_2 > I feel personally guilty for that, because I just made a better pipeline for exploited labor. **Context & use**: - Said about the `/contribute` page and Get Involved dashboard tab she built as Marketing team rep. - The disclosure question underneath it is the durable part: what does a project owe people it recruits through official onboarding surfaces? Note the framing is loaded (see Logical Validity) — cite the mechanism, not the epithet. **Tags**: #xref #articleseed  #### The organization is deliberately separable from its sanctioned founder > [!quote] ID:rw_3 > I am not synonymous with the WPCC. I am working for my members and for the board of directors, who are active WordPressers and believe in the WordPress community. **Context & use**: - Direct answer to whether her persona-non-grata status contaminates other people in the org. - A governance design statement: the org's legitimacy is meant to derive from members and board, not from its CEO's standing. **Tags**: #xref  #### Unstandardized contribution cannot survive corporate reporting > [!quote] ID:rw_4 > it becomes really complicated when you have all of these different inputs happening, and then you have to make it make sense in a boardroom, or you have to make it make sense in a monthly report. **Context & use**: - The load-bearing economic claim of the whole episode, and the reason The WPOCC exists in its current form. - Generalizes past WordPress to any open-source project seeking sustained corporate contribution. **Tags**: #xref #wpocc  ### 🧠 Permanent Candidates (H4) #### [P1] Corporate contribution fails on legibility, not goodwill **Claim** (one sentence, Courtney's voice): Companies that genuinely want to fund open-source work are blocked less by unwillingness than by having no way to fit an unstandardized contributor into a team, a report, or a return story. **Evidence pointer**: [[#rw_4]] **Scope & conditions**: Holds where funding must be justified to boards, shareholders, or budget cycles; weakens for founder-led or privately-held sponsors who can act on conviction, and for individual donors who need no justification at all. **Links** (≥1 with annotation): - [[Open Source Governance MOC]] — because applies-in: this is the funding-mechanics half of the governance question that MOC tracks - [[Five for the Future]] — because extends: names the specific program whose uneven uptake this claim explains - [[DevRel MOC]] — because applies-in: the same legibility problem is why DevRel work is chronically hard to budget  #### [P2] Recruiting someone into a system obliges you to disclose who owns it **Claim** (one sentence, Courtney's voice): Building an official onboarding funnel creates a duty to tell the people it recruits what entity actually owns the thing they're donating labor to. **Evidence pointer**: [[#rw_2]] **Scope & conditions**: Holds wherever volunteer labor is solicited through official channels and the ownership structure is non-obvious — WordCamps run by a for-profit rather than the Foundation being the concrete instance here; weakens where ownership is already plainly disclosed at the point of recruitment. **Links** (≥1 with annotation): - [[Commons & Community Governance MOC]] — because applies-in: the commons-vs-owned distinction is exactly what this duty protects - [[Contributor onboarding]] — because applies-in: the funnel is where the disclosure would have to live  ### ✏️ Fleeting Queue - [F1] Check whether The WPOCC has published its "open source pay contributor standard" — if the actual rates and deliverable definitions are public, that's directly reusable prior art. #xref - [F2] Luke's unanswered question is worth tracking independently: who blesses feature additions now, and is it recorded anywhere public? He says he asked at WordCamp Asia and got only that the release-lead role "changed." #xref - [F3] The (c)(3)-can't-pay-for-open-source constraint deserves its own note — it likely explains the legal form of several open-source orgs beyond WordPress. #articleseed - [F4] Cross-link at next synthesis pass to the WPOCC State of the Community survey notes already in the vault — this is the CEO's own account of the org's operating theory, and the two should sit together. #xref ### → Things 3 (max 2 actions) - [ ] Look up The WPOCC's AI fellowship scope and pay standard, and note whether the "DevRel for AI" framing survives into the actual posting — DevRel research #things - [ ] Read the WPOCC State of the Community report alongside this episode and draft the connection note — vault synthesis #things  📄 **Full text:** [[Full Document Contents/Articles/Perspectives with Sé Reed (Crossword S11E06).md|Perspectives with Sé Reed (Crossword S11E06) by Jonathan Wold & Luke Carbis, with Sé Reed]] ## Highlights - **Sé:** Yeah, so we workshopped it, we worked on this thing. There was a GitHub issue about it — what is the language we’re using? But it went in there and then we created this page. We adapted a little program that they had made, I believe for WordCamp — I think it was originally WordCamp Asia, and then WordCamp Europe had modified it — which was basically to figure out which team you would want to contribute to during Contributor Day. It’s like, what are you interested in? And at the end it gives you a little recommendation for the team. So we modified that, updated it, got it all together. It’s a huge deal to get stuff on WordPress.org — apparently less now, but at the time it was a big deal. So we got a slash-contribute page with this little program on it that people could go to and pick their team. And I gotta tell ya, I feel personally guilty for that, because I just made a better pipeline for exploited labor. I’m like — so I’m just telling you to volunteer for this dude. And then also I’m telling you to volunteer for WordCamps, which are run by a for-profit organization — WPCS owns all of the WordCamps, does all the WordCamps, it’s not the foundation. So all of this has been made clear. And I think, just coming back to that tenacity or why I’m still around — I believe in what we were doing. And I feel like we’re all sort of in a wait-and-see place. We need to wait and see what happens with this lawsuit. We need to wait and see what the legal take is on what powers the dictator, if you will, has for the project. And it’s gonna be uncomfortable while we wait, but I feel like that’s what a lot of people [are doing] — a lot of people are branching off into Spotify or EmDash or whatever the heck, but a lot of the bigger hosts — ([View Highlight](https://read.readwise.io/read/01m0nmfqat6mcdwbaxbkac4dx7)) - Note: Her retrospective on building the /contribute funnel and Get Involved tab. Note the framing is loaded — the durable point is the disclosure question (WPCS, not the Foundation, runs WordCamps), not the epithet. - Tags: articleseed, contributor-economics, atom/literature/h2 - **Sé:** It’s Sé, that’s the problem. This is a question — it is, I guess, an open question that people have. And I think my answer to it is: I am not synonymous with the WPCC. I am working for my members and for the board of directors, who are active WordPressers and believe in the WordPress community. ([View Highlight](https://read.readwise.io/read/01m0nmf148nbnf0m4d770dx42m)) - Note: Governance design statement: the org's legitimacy derives from members and board, not the CEO's standing — answering whether her persona-non-grata status contaminates others. - Tags: wpocc, atom/literature/h3 - **Sé:** No, you can’t. It’s dictatorship. Without any accountability, you do not have leadership, because leadership is about people choosing to follow you. That’s what you’re leading, and people follow, yeah? ([View Highlight](https://read.readwise.io/read/01m0nmerej1hvrnkb00q0xjv9x)) - Note: The episode's sharpest exchange. Luke contests the definition, then independently concedes he wouldn't follow an unaccountable leader. - Tags: open-source-accountability, atom/literature/h1, aphorisms - **Sé:** Of course, but it makes it very difficult for companies that do not work on variability and randomness to contribute. And that’s specifically what we’re talking about. It’s not the beauty of contribution. It’s how do you get a company that doesn’t have that role, that has to report to shareholders, that has a board of directors that may or may not care at all — you have to standardize it for that. It’s not because people in the project should be contributing a specific way or have a specific standard. It’s to make this — I mean, we’re literally talking about how can these companies contribute, and why are they not contributing? That has been the problem that I have been trying to solve, because they want to contribute, a lot of them — or there’s a person there who wants to do it — but it becomes really complicated when you have all of these different inputs happening, and then you have to make it make sense in a boardroom, or you have to make it make sense in a monthly report. ([View Highlight](https://read.readwise.io/read/01m0nmga3dy865na4sym2rpbhf)) - Note: The load-bearing economic claim of the episode — corporate contribution fails on legibility, not goodwill. This is why The WPOCC exists in its current form. - Tags: wpocc, atom/literature/h4, contributor-economics