There Is No WordPress Open Source *Project*  🔗 **Source:** [There Is No WordPress Open Source *Project*](https://twitter.com/arunaswp/status/2097985488321655117/?rw_tt_thread=True) > [!note]+ Document Notes > tags: [wordpress-governance, open-source-governance, infrastructure-control, fair-project, project-independence] > author: Arūnas Liuiza > source: X (@arunaswp) > reference: https://twitter.com/arunaswp/status/2097985488321655117/ > date created: 2026-09-10 > > > [!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: There is no WordPress open source *project* > <!-- 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) - [🔄 Refactor Appendix](#-refactor-appendix--there-is-no-wordpress-open-source-project) ### 🔗 References - [Twitter/X thread](https://twitter.com/arunaswp/status/2097985488321655117/) — the captured reply. - [@elliottrichmond](https://twitter.com/elliottrichmond) — the account Liuiza is replying to; the original tweet he's answering is not present in this capture. ## 📝 Summary - **What happened.** Arūnas Liuiza (@arunaswp), replying to Elliott Richmond, posted a single 29-word sentence denying that a separable "WordPress open source project" exists. His claim: what exists is open source software (the GPL-licensed codebase) *hard coupled* to a privately owned infrastructure and distribution system. - **Why it matters.** This is a structural governance claim, not a personality dispute. It attacks the premise behind a distinction commonly used in the Automattic/WordPress.org controversy — that "the company" (Automattic) and "the project" (WordPress.org, the community, the GPL software) are separable, so a leadership or ownership problem at the company doesn't touch the project. Liuiza's claim, if accurate, removes the ground that distinction stands on. - **Key stakeholders.** Anyone relying on the company/project distinction to argue the software's openness is unaffected by who controls wordpress.org: plugin and theme authors, hosts, the FAIR project, and anyone evaluating WordPress's governance independent of Automattic or Matt Mullenweg personally. - **Risks and tradeoffs.** As a single unsupported sentence, it's an assertion, not a demonstration. It names a testable claim without providing the test. - **Bottom line.** The sentence reframes "is WordPress open source?" as the wrong question and substitutes "is WordPress's *distribution* open?" — a sharper, checkable question this note treats as a claim to verify, not a settled fact. ## 📖 Main Content Liuiza's reply responds to Elliott Richmond (whose original post is not captured in this document, so the prompting context — likely a defense of WordPress's open-source status during the Mullenweg leave-of-absence coverage — can't be reconstructed from this source alone). His full reply, in his own words: > [!quote] > There is no WordPress open source project. There is only a piece of open source software which is hard coupled with a privately owned infrastructure and distribution system. His argument has two parts, both asserted rather than argued for in the 29 words available: 1. **The software is open source.** He doesn't contest this — the GPL license on WordPress core isn't in dispute anywhere in the source text. 2. **The infrastructure and distribution system are privately owned, and the two are "hard coupled."** This is the load-bearing claim. "Hard coupled" is doing real work: it asserts not just that private infrastructure exists alongside the open software, but that the software's practical openness — the ability to get updates, discover plugins and themes, and reach users — depends on that private infrastructure with no independent path around it. From those two premises he draws the conclusion in the title: therefore there is no separable "project," only "a piece of open source software" running through privately controlled pipes. **What the source does and doesn't establish.** The claim about GPL licensing is uncontroversial. The claim about which entity legally owns wordpress.org's domain, plugin directory, theme directory, and update servers is a factual, checkable question that this single tweet does not itself answer — it asserts the coupling without citing who owns what. Separately, and outside what this source states: it's widely reported that the wordpress.org domain and its associated distribution infrastructure are registered to Matt Mullenweg personally, distinct from both the Automattic company and the WordPress Foundation (which holds the trademark) — a structural fact that predates and outlasts this specific tweet and that would substantiate Liuiza's coupling claim if confirmed against primary registration records, which this note does not do. This is why the CRITICAL HANDLING framing matters: Liuiza's sentence is an argument about *structure* (who controls the pipe), not an accusation against a person, and it should be read and cited as his claim, evaluated on the ownership facts, not adopted as established fact just because it's a clean formulation. ## 🗒️ Notes - Single-sentence reply; no thread, no follow-up from this account in the capture. - The phrase "hard coupled" is a systems/engineering metaphor applied to governance: two components (software license, distribution infrastructure) that in principle could be independent are, in his claim, bound together such that neither functions without the other. - The distinction the tweet implicitly targets — company vs. project — is the same distinction used defensively in most of the week's other coverage of the Automattic leave-of-absence story (see References). Liuiza's tweet is a direct rebuttal of that framing, not a comment on the leave itself. - No numbers, dates, or named entities beyond the reply target are given. This is an assertion of structure, not a documented case. ## 📚 References - [@arunaswp on X](https://twitter.com/arunaswp/status/2097985488321655117/) — this post. - [@elliottrichmond on X](https://twitter.com/elliottrichmond) — reply target; original post not captured here. - The WPOCC and FAIR project materials (outside this document) — relevant background on efforts to decouple WordPress metadata, provenance, and distribution from any single private owner; not cited by Liuiza, but the closest existing project attempting exactly the decoupling his tweet says doesn't exist yet. ## 🗣️ Paraphrase Liuiza says the phrase "WordPress open source project" is a misnomer. What actually exists, in his account, is licensed software whose real-world openness is contingent on infrastructure — the directories, update mechanism, and domain — that one private owner controls. Because the software can't reach users without that infrastructure, he argues there's no independent "project" to point to; there's only the software and the private pipe it runs through. ## 📰 Newsletter - A one-line claim worth sitting with if you work in WordPress governance: is "the project" real, or is it a name for software that happens to run through privately owned rails? Arūnas Liuiza (@arunaswp) put it sharply this week, replying to Elliott Richmond amid the Automattic leave-of-absence coverage — "There is no WordPress open source project. There is only a piece of open source software which is hard coupled with a privately owned infrastructure and distribution system." - It's an assertion, not a proof — but it names the exact question the FAIR project and similar decoupling efforts are trying to answer with code rather than rhetoric: what happens if the private infrastructure goes away? ## ✅ Action Items #### DevRel - No distinct action from this source; it's a governance framing claim, not a developer-facing change. #### OSPO - **Policy & Governance:** worth testing this claim directly — document, from primary sources (registrar records, .org terms of service, distribution-API ownership), who actually controls each layer Liuiza names (domain, plugin/theme directories, update servers) and whether "hard coupled" holds up as a technical claim (i.e., is there any sanctioned alternate distribution path today). #### Community - **Maintainers/contributors:** the company/project distinction gets invoked often in community discussion; this tweet is a citable counter-argument worth having on hand rather than a settled rebuttal. #### WordPress - **Core Program Team:** if the coupling claim is accurate, it's directly relevant to any governance-reform conversation about who can act on behalf of "the project" independent of the infrastructure owner. #### The WPOCC - **Governance clinics:** this is a clean one-sentence prompt for a clinic session on "what does independence from a single infrastructure owner actually require." ### FAIR - **Technical independence:** this tweet is effectively FAIR's founding premise stated as a negation — local metadata, provenance, and signature checks exist specifically to decouple what Liuiza says is coupled. Cite it as the problem statement FAIR is attempting to solve. ## 🧪 Hypotheses - **H1:** WordPress.org's plugin directory, theme directory, and core update servers are controlled by a single private entity (Matt Mullenweg personally, per public reporting), with no sanctioned alternate distribution path for a site running WordPress core. - **H2:** If that private infrastructure were withdrawn or restricted, most WordPress installations would lose the ability to receive plugin/theme updates and security patches through any currently sanctioned mechanism. - **H3:** The FAIR project's local-metadata and provenance-verification approach, if adopted at scale, would falsify Liuiza's "hard coupled" claim by providing a working alternate path. ### 📊 Methodology - For H1: pull current WHOIS/registrar records for wordpress.org and cross-reference against Automattic's and the WordPress Foundation's public statements about what each entity owns; compare against the .org Trademark Policy and any published Foundation-to-.org control documentation. - For H2: technical audit of a stock WordPress install's update mechanism (`wp-admin/update-core.php` and the plugin/theme update API) to confirm there's no built-in fallback distribution channel. - For H3: track FAIR's adoption numbers and whether any FAIR-enabled site has successfully received an update with wordpress.org infrastructure unreachable, as a real test of decoupling. ### ❓ Questions - Who is the legal owner of record for the wordpress.org domain and the servers behind the plugin/theme directories, today? - Has any WordPress site ever successfully updated plugins or themes through a channel other than wordpress.org's official API? - What did Elliott Richmond's original post (not captured here) actually argue, and is Liuiza's reply a direct rebuttal or a tangential point? ### 🔮 Future Research - A primary-source audit (domain registration, Foundation bylaws, Automattic public filings) settling exactly who owns each layer Liuiza names, published somewhere citable rather than asserted in a tweet. - Tracking whether FAIR or a similar effort ever reaches the point of being a real, usable alternate distribution path — the practical test of whether the coupling is truly "hard." ### 💡 Implications - **For governance debates:** if the coupling claim holds, "the project is fine, only the company is affected" arguments used during the Automattic leave-of-absence coverage need a harder look — the project's practical independence would be an open technical question, not a given. - **For funding models and covenants:** decoupling proposals (FAIR, WPOCC governance clinics) gain urgency if there is in fact no infrastructure-independent fallback today. - **For plugin/theme authors and hosts:** business continuity planning that assumes wordpress.org will always be reachable rests on an assumption this tweet directly challenges. - **For security:** a single point of control for the update pipeline is also a single point of failure for patch delivery, independent of who currently holds it. ### 🧠 Learning Styles Assessment - Reading level: a single, dense compound sentence; roughly Flesch-Kincaid grade 10–11 by ear (subordinate clause stacking — "which is hard coupled with a privately owned infrastructure and distribution system" — is the main complexity driver). No formula was run against the text; this is an estimate from sentence structure. #### 👀 Visual learners - Present: none — plain text only. - Improve: a simple two-box diagram (Software [open] → Infrastructure [private] → Users) would make the coupling claim legible at a glance. #### 🔊 Aural learners - Present: none. - Improve: N/A for a single tweet; not worth a dedicated audio treatment. #### 🗣️ Verbal learners - Present: the claim is definitional ("there is no X, there is only Y") — a clear verbal structure. - Improve: define "hard coupled" explicitly for readers unfamiliar with the systems metaphor. #### 🧩 Kinesthetic learners - Present: none. - Improve: a hands-on exercise — try disabling wordpress.org connectivity on a test install and observe what update paths remain — would make the claim testable rather than rhetorical. #### 🧠 Logical learners - Present: the tweet is structured as a syllogism (software is open; infrastructure is private and coupled to it; therefore no independent project). - Improve: spelling the syllogism out explicitly, with each premise's evidentiary status marked (asserted vs. verified), would strengthen it for a logical-learner audience. #### 🧑‍🤝‍🧑 Social learners - Present: it's a reply in a public thread, inherently conversational. - Improve: the missing context (Richmond's original post) breaks the social thread for a reader arriving cold; linking or quoting the parent tweet would restore it. #### 🧘‍♀️ Solitary learners - Present: a compact, quotable line suited to individual reflection. - Improve: none needed for this format. #### 🌿 Naturalistic learners - Present: none — no ecosystem or environmental framing. - Improve: not applicable; the "coupling" metaphor is systems-engineering, not naturalistic, and forcing an ecological frame would misrepresent the source. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: plain text, no markup to navigate. - Improve: not applicable at the source level; this is a platform (X) rendering concern, not an authoring one. #### Keyboard navigation - Present: not applicable — static text, no interactive elements in the captured content. #### Contrast and readability - Present: not evaluable from captured plain text (rendering is platform-dependent, not authored by Liuiza). #### Text resizing and reflow - Present: not applicable — no layout to test. #### Media and captions - Present: none — no media in this post. #### Forms and interactions - Present: none — no interactive elements. #### Standards reference - Not applicable: a single plain-text social post has no WCAG-relevant surface area beyond what the host platform controls. ### 🌍 DEIB Assessment #### Cultural breadth - Not applicable — no cultural or regional content in a single structural claim about infrastructure ownership. #### Inclusive language - Present: neutral, technical register throughout; no gendered or exclusionary language. #### Neurodiversity support - Present: the claim is compact but syntactically dense (one long subordinate clause); a reader would benefit from it being broken into two sentences. - Improve: split "There is only a piece of open source software which is hard coupled with a privately owned infrastructure and distribution system" into two shorter clauses for easier parsing. #### Representation - Not applicable — no people or groups are represented or described. #### Psychological safety - Present: the tone is analytical, not inflammatory; it critiques a structure, not a person. ### ✅ Logical Validity #### Strong reasoning - The core move is a clean conceptual distinction: "open license" and "open, independently controlled infrastructure" are not the same property, and conflating them is a real category error worth naming. That distinction is sound regardless of whether the specific ownership facts check out. #### Fallacies - **Unsupported premise:** the claim that software and infrastructure are "hard coupled" is asserted, not evidenced, within this text. It may well be true (see Main Content's note on public reporting about wordpress.org's ownership), but as written it's a bare assertion — the fallacy risk is treating a plausible, unproven claim as self-evidently settled because it's stated confidently. Fix: cite the specific ownership facts (registrar, control of the plugin/theme directory servers) that would substantiate "hard coupled." #### Tone of voice - Flat, declarative, unhedged — "There is no... There is only..." The certainty of the phrasing outruns the evidence actually supplied in the tweet itself. ### 🛡️ DARVO Analysis DARVO describes a move made by an accused party responding to an accusation against them. This source doesn't fit that shape: Liuiza isn't responding to an accusation made against him, and he isn't the subject of any allegation in this thread. He's making an unprompted structural argument about WordPress governance, replying to someone else's (uncaptured) post. - **Deny:** not applicable — no accusation exists here for him to deny. - **Attack:** not applicable — no critic or accuser is named or engaged; Richmond's original point, whatever it was, isn't characterized or attacked, just implicitly disagreed with. - **Reverse victim/offender:** not applicable — no victim/offender framing appears in the text. DARVO doesn't apply to this source; it's included here, as the spec requires, to state plainly that it doesn't and why, rather than skip the section. ## 🎯 Conclusion The sentence is short, but the question it poses is real and checkable: is WordPress's distribution layer independently controlled, or does its practical openness run entirely through one privately owned pipe? That's a factual question about domain registration and infrastructure control, not a matter of opinion — and this tweet asserts an answer without providing the primary-source evidence for it. The practical next step for a reader working in WordPress governance is the one this note flags twice: pull the actual ownership records for wordpress.org's domain and distribution infrastructure and check whether "hard coupled" is demonstrable rather than merely plausible. ## 🔄 Refactor Appendix — There is no WordPress open source *project* > Density: fewer than 2 strong, independently atomizable claims in this 29-word source — the tweet > makes one structural claim ("software and infrastructure are hard coupled, so no separable project > exists"), not two or more distinct ideas. Per the atom-density rule, that means **zero Literature > atoms** below, stated explicitly rather than split artificially to hit a quota. ### 📚 Literature Atoms Zero atoms. The source is a single 29-word sentence carrying one claim (software-infrastructure coupling negates an independent "project"). Splitting it further would fabricate distinctions the text doesn't make; padding to a 2-atom minimum would violate the density rule's explicit instruction to emit zero rather than pad. ### 🧠 Permanent Candidates (H4) #### [P1] License openness and infrastructure independence are separate properties **Claim** (Courtney's voice): Whether software is open-licensed and whether its practical distribution is independently controlled are two separate properties, and treating "the software is open source" as proof that "the project" is independent conflates them. **Evidence pointer**: this note's Main Content and Logical Validity sections; the source tweet is the prompting instance but the claim generalizes beyond it. **Scope & conditions**: applies to any open-source project where distribution (update servers, package/plugin directories, domain) is controlled by a single entity distinct from the license itself — WordPress via wordpress.org is the motivating case, but the pattern isn't WordPress-specific. **Links** (≥1 with annotation): - [[FAIR project]] — because applies-in: FAIR's local-metadata/provenance approach is a direct attempt to build the independent distribution path this claim says doesn't currently exist. - [[WPOCC governance clinics]] — because extends: a concrete prompt for a clinic session distinguishing license governance from infrastructure governance. <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Pull primary-source ownership records (registrar, control of update/plugin-directory servers) for wordpress.org and settle whether "hard coupled" is demonstrable, not just plausible. — #xref - [F2] Find and read Elliott Richmond's original post that this is a reply to; the missing parent context limits how much weight this single reply can carry. — #xref ### → Things 3 (max 2 actions) - [ ] Verify who currently controls the wordpress.org domain and the plugin/theme distribution servers, from primary sources, before citing Liuiza's "hard coupled" claim as fact in any governance writing — context #wp-governance #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/There Is No WordPress Open Source Project.md|There Is No WordPress Open Source *Project* by Arūnas Liuiza]] ## Highlights - [@elliottrichmond](https://twitter.com/elliottrichmond) There is no WordPress open source *project*. There is only a piece of open source software which is hard coupled with a privately owned infrastructure and distribution system. ([View Highlight](https://read.readwise.io/read/01m25knmyy18yz8ndr404gdg33)) - Note: Denies the premise everyone relied on this week. If the directories, update endpoints, and domain are privately held, "the project" has no separable existence to be insulated by a leave of absence. The FAIR argument stated as a negation — and testable: if the private infrastructure withdrew, could anything keep shipping updates? - Tags: infrastructure-control, atom/literature/h1, fair-project ## New Highlights added 2026-09-10 at 10:41 AM - There is no WordPress open source project. There is only a piece of open source software which is hard coupled with a ([View Highlight](https://read.readwise.io/read/01m25w0evkk52g22s0dmw1gfxh)) - Note: Liuiza (@arunaswp), not Mullenweg. The license-openness vs. infrastructure-independence distinction in one line. - Tags: wordpress-governance, xref