WordPress Takes Its Turn Leading the Open Website Alliance

WordPress Takes Its Turn Leading the Open Website Alliance ![rw-book-cover](https://i0.wp.com/wordpress.org/news/files/2026/09/image-3.png?fit=1200%2C675&ssl=1) 🔗 **Source:** [WordPress Takes Its Turn Leading the Open Website Alliance](https://wordpress.org/news/2026/09/owa-president/) > [!note]+ Document Notes > tags: [open-website-alliance, open-source-governance, cyber-resilience-act, wordpress-foundation, cross-cms-collaboration, policy-advocacy] > author: Mary Hubbard > source: WordPress.org News > reference: https://wordpress.org/news/2026/09/owa-president/ > date created: 2026-09-21 09:00 > > > [!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: WordPress Takes Its Turn Leading the Open Website Alliance >  ## 🧭 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--wordpress-takes-its-turn-leading-the-open-website-alliance) ### 🔗 Byline provenance The published page shows no human byline. Both the visible author field on wordpress.org/news and the Readwise Reader author field read "wordpress.org". The author resolved here — Mary Hubbard, WordPress Executive Director — comes from the WordPress.org REST API record for the post, not from the rendered page. Treat the attribution as API-derived, and expect any citation manager pulling from the HTML alone to disagree. ## 📝 Summary - **What happened.** Mary Hubbard announced she is serving as president of the Open Website Alliance, representing the WordPress Foundation. The post is 239 words across three paragraphs and carries eight outbound links. - **What the Alliance is.** Per the post, the OWA gathers the community organizations behind Drupal, Joomla!, TYPO3, and WordPress to advocate for open source and share practices. The presidency rotates among members; the post does not say on what cycle. - **What the term actually is.** The post omits it. The linked OWA charter supplies it: a default one-year term, extendable in six-month increments by unanimous consent, rotating alphabetically, with eligibility limited to founding members and members holding at least 12 months of membership. Drupal, Joomla!, TYPO3, WordPress in alphabetical order puts WordPress last in the first cycle — which is what "takes its turn" describes. - **Why it matters.** This is the first named WordPress leadership position in a multi-project governance body. The only joint output the post cites is the 2023 response to the EU Cyber Resilience Act — real work with a documented artifact, but a single instance across roughly three years. - **Key stakeholders.** The WordPress Foundation (the member entity, distinct from Automattic and from WordPress.org), the Drupal Association, Open Source Matters (Joomla!), and the TYPO3 Association. Downstream: anyone in cross-CMS policy advocacy, hosting, agencies serving multiple CMSes, and contributor programs that could be run jointly. - **Risks and tradeoffs.** The charter states the Alliance is not a legal entity and cannot represent members or sign contracts on their behalf. Decisions require unanimous votes excluding abstentions. A four-member unanimity rule means any one project can block, so the Alliance's output ceiling is whatever all four agree on. Nothing in the post acknowledges these constraints. - **Bottom line.** A real institutional milestone with a thin announcement. The governance substance is in the charter, not in the post; the post's job is to point you there, and it does that in its last sentence. ## 📖 Main Content ### The claim set, stated precisely The post makes five checkable claims: 1. Mary Hubbard is now president of the Open Website Alliance. 2. She holds the role representing the WordPress Foundation. 3. The role rotates among the Alliance's members. 4. Members are the community organizations behind Drupal, Joomla!, TYPO3, and WordPress. 5. WordPress announced participation in 2024, building on prior joint work responding to the EU Cyber Resilience Act. Claims 3 and 4 are confirmed and expanded by the linked charter. Claim 5 splits: the CRA work is documented by a WordPress.org News post dated August 2, 2023; the 2024 participation announcement is documented only by a post on X. ### What "representing the WordPress Foundation" means The charter requires members to be legal entities, not individuals, and permits one organization per project. So the OWA seat belongs to the WordPress Foundation as a legal person, and Hubbard occupies it as its designated contact. This matters for a reader who tracks WordPress governance: the Foundation, not Automattic and not the WordPress.org site operation, is the entity on the roster. The post states the representation relationship but never distinguishes the Foundation from the other WordPress-adjacent entities, and a reader who does not already hold that distinction will not learn it here. The charter also specifies what the president does: serve as primary contact and handle meeting logistics. That is a coordinating role, not an executive one. The post says nothing about the duties, which leaves room for a reader to over-read the title. ### The membership bar Charter criteria for membership: free and open-source web CMS projects, represented by legal entities, licensed exclusively under OSI-approved licenses, and signatories to the Open Web Manifesto. That is a narrow gate. It excludes individual maintainers, projects under source-available licenses, and any CMS whose steward is a for-profit vendor rather than a community organization. The four current members are the four large PHP-era community CMSes. The gate explains both who is in and who structurally cannot be. ### The one demonstrated output The CRA response is the Alliance's proof of work, and the linked 2023 post gives it shape. WordPress, Drupal, Joomla!, and TYPO3 wrote jointly as the Inter-CMS Working Group. Two concerns: the Act's treatment of "unfinished software" cut against iterative open-source development, and the definition of "commercial activity" risked sweeping in not-for-profit community projects. The ask was a Brussels seminar with the EU Commission. The current post compresses all of that into one sentence about the economic role of CMS software: > [!quote] Source paragraph 2 > While many open source projects focus on underlying digital infrastructure, our content management systems power the websites where businesses reach customers and sell products and services. That is the group's distinctive argument, and it is the sharpest line in the post. Infrastructure-layer projects argue from dependency; CMS projects argue from commerce. The distinction gives regulators a different lever, and it is why a four-CMS bloc has a case to make that the Linux Foundation or the Apache Software Foundation would not make the same way. ### The Open Weights reference is thematic, not organizational Paragraph three pivots to WordPress signing the Open Weights and American AI Leadership letter. The linked post dates the WordPress signature to August 27, 2026, on a letter published July 24, 2026, with more than 270 signing companies and organizations. Nothing in either post connects that letter to the OWA. It is a US AI policy action; the OWA's documented work is EU product-security policy. The post links them by theme ("this commitment to openness builds on"), which is fair positioning, but a reader tracking institutional commitments should not record it as Alliance activity. ### Terms that need defining - **Open Website Alliance (OWA)** — a collaboration body, per its charter, not a legal entity. Four members. Unanimous decision-making. - **Open Web Manifesto** — a required signatory document for OWA membership, referenced in the charter. The post does not mention it. - **Cyber Resilience Act (CRA)** — EU regulation setting cybersecurity requirements for products with digital elements. The 2023 concern was scope and definitions, not the goal. - **Open weight models** — AI models whose weights can be downloaded, inspected, modified, and run independently. Distinct from "open source AI," which additionally implies training data and code disclosure. The post uses the letter's framing without defining the term. ### Contested and uncertain - Whether the rotation is strictly alphabetical in practice. The charter says alphabetical; the post says only that it rotates. If it is alphabetical and started at Drupal, WordPress's turn arriving in 2026 implies roughly one-year terms since 2023 or 2024, consistent with the charter default — but that is inference, not a stated fact. - Whether the Alliance has produced anything between the 2023 CRA letter and this post. Neither the post nor the charter says. - Whether a president can set an agenda. The charter's description — primary contact plus meeting logistics — suggests not much, and unanimity confirms it. ## 🗒️ Notes - Word count of the source: 239. Three paragraphs. No headings, no lists, no images described in the text. - Eight outbound links, all external or cross-site. Four are bare project homepages (OWA, Drupal, Joomla!, TYPO3) that function as identification, not evidence. Three are substantive citations. One is a social post standing in for institutional documentation. - The post opens in first person and stays there. Ten first-person pronouns in 239 words is a high density for a WordPress.org News post, which usually writes as the project rather than as a person. - The closing sentence is a call to read the charter. That is the single most useful line in the post for anyone doing governance work, because the charter answers the questions the post leaves open. - The mission line is boilerplate that does real work here: > [!quote] Source paragraph 3 > Our mission to democratize publishing means giving anyone a voice and welcoming everyone to contribute. It frames cross-project collaboration as mission execution rather than as a new initiative, which lowers the bar for justifying it internally. - The rotation sentence is the governance core of the post: > [!quote] Source paragraph 1 > I represent the WordPress Foundation in this role, which rotates among the Alliance’s members. Two facts in one clause: which entity holds the seat, and that the position is not permanent. - Absences worth logging, since absences in a governance announcement are findings: - No term length, no start date, no end date. - No description of presidential duties. - No named successor or predecessor. The post does not say which member held the presidency before WordPress. - No forward agenda. Nothing about what the Alliance will work on next. - No distinction drawn between the WordPress Foundation's role and Automattic's, in a year when that distinction is under scrutiny. - No mention that the Alliance cannot contract or represent members, which the charter states plainly. - No mention of unanimity, which shapes everything the Alliance can produce. - No contact path. A reader who wants to participate has nowhere to go except the charter page. ## 📚 References Eight links appear in the source markup. Assessed individually: 1. [Open Website Alliance](https://openwebsitealliance.org/) — the organization's homepage, used to identify the body on first mention. Identification, not evidence. Appropriate. 2. [Drupal](https://www.drupal.org/) — project homepage. Identification only. It points to the project site, not to the Drupal Association, which is the legal entity the charter's membership rule would actually require. Minor imprecision. 3. [Joomla!](https://www.joomla.org/) — project homepage. Same pattern; the member entity is Open Source Matters, not linked. 4. [TYPO3](https://typo3.org/) — project homepage. Same pattern; the member entity is the TYPO3 Association, not linked. 5. [announced its participation in the Alliance in 2024](https://x.com/WordPress/status/1755516866485707064) — a post on X standing as the sole documentation for WordPress joining a governance body. This is the weakest citation in the post. A social post is not a durable institutional record: it lives on a third-party platform, can be deleted or made unavailable, is not archived by the project, and carries no detail about terms of membership. For an announcement whose subject is institutional commitment, the citation should be a WordPress.org News post or a Foundation page. 6. [respond to the European Union's Cyber Resilience Act](https://wordpress.org/news/2023/08/concerns-over-the-european-unions-cyber-resilience-act-cra/) — the strongest citation. A first-party WordPress.org News post dated August 2, 2023, documenting the joint Inter-CMS Working Group letter from WordPress, Drupal, Joomla!, and TYPO3, its two named concerns (the "unfinished software" prohibition and the definition of "commercial activity"), and its ask for a Brussels seminar with the Commission. This link carries the claim it is attached to. 7. [Open Weights and American AI Leadership letter](https://wordpress.org/news/2026/08/open-weight/) — first-party, dated August 27, 2026. Documents WordPress signing a letter published July 24, 2026 with 270+ signatories, asking for compute access for startups and researchers, investment in shared infrastructure such as public datasets and evaluation tools, preservation of multiple model types, and permission for standard practices like using one model to improve another. Accurately supports the fact that WordPress signed. Does not support any OWA connection, and the post does not claim one explicitly. 8. [Open Website Alliance charter](https://openwebsitealliance.org/charter.html) — the governance document. It is the most informative link in the post and answers what the post omits: membership criteria (FOSS web CMS projects, represented by legal entities, OSI-approved licenses only, Open Web Manifesto signatories, one organization per project), a one-year default presidential term extendable by six-month increments under unanimous consent, alphabetical rotation, eligibility limited to founding members and members of at least 12 months, unanimous decision-making excluding abstentions, four weeks' notice for charter amendments, and the statement that the Alliance is not a legal entity and cannot represent members or enter contracts for them. Citation quality overall: six of eight links do the job. The four homepage links are thin but honest. The CRA and charter links are load-bearing and hold. The X link is the one that should be replaced. ## 🗣️ Paraphrase Hubbard reports that she now holds the Open Website Alliance presidency on behalf of the WordPress Foundation, describes the Alliance as the four community organizations behind Drupal, Joomla!, TYPO3, and WordPress working together on open-source advocacy and shared practice, and notes the role rotates among members. She traces WordPress's 2024 entry back to the four projects' joint response to the EU Cyber Resilience Act, where they argued that CMS software occupies an economic position distinct from lower-level infrastructure and asked regulators to weigh that when setting security rules without disrupting how volunteer communities build software. She closes by tying the Alliance to WordPress's signature on the Open Weights and American AI Leadership letter and to the democratize-publishing mission, then points readers to the Alliance charter. ## 📰 Newsletter **WordPress gets the gavel — and the charter is the better read** Mary Hubbard is now president of the Open Website Alliance, the four-project bloc that puts WordPress at the same table as Drupal, Joomla!, and TYPO3. The [announcement](https://wordpress.org/news/2026/09/owa-president/) runs 239 words, which is roughly the length of a WordCamp lightning-talk abstract, so plan to click through. Click to the [charter](https://openwebsitealliance.org/charter.html), specifically. That is where you learn the presidency runs a one-year default term, rotates alphabetically, and requires 12 months of membership to be eligible — and that every Alliance decision needs a unanimous vote. Four members, one veto each. That constraint tells you more about what the Alliance can ship than any announcement will. The track record so far is the [2023 Cyber Resilience Act letter](https://wordpress.org/news/2023/08/concerns-over-the-european-unions-cyber-resilience-act-cra/), where the four projects wrote to the EU Commission as the Inter-CMS Working Group and made an argument nobody else was making: CMS software is where businesses actually sell things, so security rules written for infrastructure libraries land differently here. That framing is worth borrowing the next time you testify, comment, or write to a regulator. Also linked: WordPress's August signature on the [Open Weights and American AI Leadership letter](https://wordpress.org/news/2026/08/open-weight/), alongside 270-plus other organizations. Different continent, different policy file, same argument about who gets to inspect and modify the tools they depend on. For contributors: nothing in this post tells you how to participate in the Alliance. If you run a team that would benefit from a cross-CMS counterpart — accessibility, polyglots, security, docs — the presidency year is the window to ask. ## ✅ Action Items #### DevRel - Developer advocacy: draft a 15-minute talk on the Inter-CMS Working Group's CRA argument — that CMS platforms carry commercial traffic and so need different regulatory treatment than infrastructure libraries — and pitch it to WordCamp US, DrupalCon, and the TYPO3 developer days in the same quarter. - Education: build a one-hour "how open-source projects engage regulators" session using the 2023 CRA post and the OWA charter as the two primary texts. Both are short enough to read live. - Developer experience: publish a plain-language explainer of what the CRA's "commercial activity" definition means for a plugin author who takes donations. That question is unresolved for most contributors and the 2023 post raises it without answering it for individuals. - Developer marketing: track referral traffic from this announcement to openwebsitealliance.org over 30 days. The post's only conversion ask is "read the charter"; measure whether a 239-word post moves anyone. - Community management: add an OWA line to the WordPress project governance FAQ, including the Foundation-not-Automattic distinction the post leaves implicit. - Internal/external/cross-project: open a standing quarterly sync with DevRel counterparts at Drupal, Joomla!, and TYPO3 during the WordPress presidency year, while WordPress holds the convening role. #### OSPO - Policy & Governance: file the OWA charter as a reference artifact for multi-project collaboration bodies. Its unanimity rule and its explicit "not a legal entity, cannot contract" clause are the two provisions worth copying or deliberately avoiding. - License Compliance: note the charter's OSI-approved-licenses-only membership requirement as precedent when evaluating any future alliance invitation. - Security Management: map the CRA's disclosure and vulnerability-handling obligations against the current WordPress security team intake process, and identify where the four projects could publish a shared coordinated-disclosure position. - Software Inventory: check whether SBOM expectations arising from CRA implementation are being tracked anywhere in the WordPress project. The 2023 letter argued about scope; implementation will arrive regardless of scope. - Developer Support: prepare a short internal brief for Foundation-adjacent staff on what the presidency does and does not authorize — the charter limits it to primary contact and meeting logistics. - Community Engagement: ask the other three members whether any of them publish meeting minutes. If none do, propose that the WordPress presidency year start. - Strategic Alignment: define two measurable outcomes for the presidency year before it is half over. "Rotating chair with no deliverable" is the default failure mode of a unanimity-governed body. #### Community - Maintainers: run one joint governance clinic with maintainers from all four projects on release cadence and security response, using the presidency as the convening excuse. - Contributors: publish a "how to participate in policy advocacy" onboarding path. Right now no such path exists, and the post gives an interested contributor no entry point. - Sponsors: ask whether the Alliance has a budget, and if so where it is reported. The charter describes governance but the fetched summary names no funding mechanism. - Ecosystem: propose a cross-CMS coordinated disclosure drill. Four projects sharing a PHP-shaped threat surface and a common regulatory environment is the strongest argument for one. #### WordPress subteams - Core: nothing in this post changes Core priorities. Log it as context, not as a backlog item. - Core Performance: no action. - Core AI: read the Open Weights letter's four asks and check whether any WordPress AI feature work depends on open-weight model availability. If it does, the signature has practical stakes beyond positioning. - **Core Program Team:** add the OWA presidency to the project's public timeline so the term's start and end are recorded somewhere the project controls, rather than only on X. - Mobile: no action. - Playground: build a Playground blueprint that demonstrates the same content-management task across the CMSes where possible, as a teaching artifact for cross-CMS audiences. Low priority, high demo value. - Community: brief WordCamp organizers on the OWA so that "what is WordPress's relationship to Drupal and Joomla?" has a consistent answer at the contributor table. - Training: add a Learn WordPress lesson on open-source policy advocacy, using the CRA response as the worked example. - Marketing: the post under-sells a genuine first. Prepare a longer follow-up with the term dates, the duties, and at least one concrete goal. - Support: no action. - Design: no action. - Documentation: document the WordPress Foundation's institutional memberships in one place. Today a reader has to reconstruct it from news posts and a social post. - Photos: no action. - TV: if any OWA session is recorded during the presidency year, caption it and index it under governance. - Polyglots: translate the CRA position summary and this announcement into the locales most affected by EU regulation. - Accessibility: propose accessibility as a candidate for the first shared-practice deliverable. All four projects ship admin UIs and all four face the European Accessibility Act. - Meta: create a governance page on wordpress.org listing the Foundation's alliance memberships with dates, so future announcements can cite a first-party record instead of a social post. - CLI: no action. - Hosting: brief hosting partners on CRA implementation timelines, since hosts will field the compliance questions before the projects do. - Tide: no action. - Openverse: no action. - Themes: no action. - Plugins: assess whether CRA obligations reach plugin authors distributing through the directory, and prepare guidance before the question becomes urgent. #### The WPOCC - Programs: The WPOCC should treat the OWA charter as a governance reference when designing fellowship and stipend structures — specifically its eligibility clock (12 months of membership before a member can hold the presidency), which is a simple, auditable anti-capture mechanism. - Projects: propose that The WP Open Community Collective document its own rotation and term rules with the same specificity the OWA charter uses, including what happens on resignation mid-term. - Funding experiments: compare the OWA's unanimity requirement against The WPOCC's own decision rules. Unanimity protects small members and caps ambition; note which tradeoff each body has chosen and why. #### FAIR - Technical independence: a four-project alliance is a natural constituency for federated, independently verifiable distribution. Ask whether any OWA member has an interest in shared provenance and signature tooling. - Policies and covenants: the OWA charter's "not a legal entity, cannot enter contracts" clause is a useful model for a body that wants coordination without capture. Add it to the covenant reference set. - Productized governance artifacts: the charter is a short, readable, copyable governance artifact. Add it to the charter library alongside existing examples, with the alphabetical rotation and unanimity provisions annotated. ## 🧪 Hypotheses 1. The OWA presidency will produce no new joint public artifact during the WordPress term. Basis: unanimity among four members plus a president whose charter duties are limited to contact and logistics. 2. The Alliance's next joint output, if any, will respond to EU regulation rather than US policy. Basis: the only documented output is the CRA letter; the Open Weights letter was signed by WordPress alone. 3. The 2024 participation claim has no first-party WordPress.org record. Basis: the post links to X rather than to its own news archive, which it does for the other two substantive claims. 4. Cross-CMS collaboration measured in shared contributors is near zero. Basis: the Alliance operates at the organizational layer; nothing in the charter or the post describes contributor-level programs. 5. The term runs one year by default, meaning it ends around September 2027. Basis: the charter default, plus the post's silence implying no negotiated extension. 6. Readers of this post will not be able to state the presidency's duties afterward. Basis: the post never states them and the duties only appear in a linked document. ## 📊 Methodology Each hypothesis is cheap to test and none requires original research. - H1 and H2: watch openwebsitealliance.org and the four projects' news feeds for 12 months. One joint statement settles both. - H3: search the wordpress.org/news archive for 2024 posts mentioning the Alliance. A null result confirms it. - H4: ask the four member organizations whether any shared contributor program exists. A four-question email is the whole study. - H5: read the charter's rotation clause and ask the president for the term dates. One email. - H6: a five-person comprehension check — have readers read only the post, then ask what the president does. No statistical design applies here. The source is an announcement, not a study, and pretending otherwise would manufacture rigor the material does not support. ## ❓ Questions - Who held the OWA presidency before WordPress, and what did that term produce? The post names no predecessor, which makes the rotation unverifiable from first-party sources. - What has the Alliance done between August 2023 and September 2026? Three years with one cited output is either under-reporting or under-activity, and the post does not distinguish. - Does the WordPress Foundation's OWA seat come with any funding obligation or staff time commitment, and is that disclosed anywhere? - Under unanimity, what happens when one member's commercial steward disagrees with a policy position the other three want to take? - Does the Alliance have a position on the European Accessibility Act, which reaches all four projects' admin interfaces? The CRA work suggests the capability exists. - The charter says membership is limited to one organization per project. Which WordPress entity is on the roster in the charter's own records — the WordPress Foundation as the post states, or another? The post asserts the Foundation; nothing in the charter summary names it. - Is the Open Weights signature a WordPress-only action or a signal of a future Alliance position on AI policy? The post's sequencing invites the second reading without supporting it. - Would a shared cross-CMS security disclosure process be in scope for the Alliance, or does "share practices that benefit their projects" stop short of operational coordination? - What would make this presidency worth reporting on at its end? Name the deliverable now or the term is unfalsifiable. - Why is a governance milestone documented at 239 words? Is this a deliberate low-key register, or a signal that there is not yet more to say? ## 🔮 Future Research - Pull the full charter text rather than a summary, and check the rotation and resignation clauses word for word against how the presidency has actually moved since founding. - Trace the CRA from the 2023 letter to the final adopted text, and assess whether the Inter-CMS Working Group's two concerns — the "unfinished software" prohibition and the "commercial activity" definition — were addressed. That is the only available measure of whether the collaboration worked. - Compare the OWA charter against the governance documents of other multi-project bodies (Linux Foundation project charters, the Eclipse Foundation working group model, the Open Source Initiative's affiliate structure) on decision rules, term limits, and capture resistance. ## 💡 Implications ### For cross-CMS collaboration A rotating presidency with unanimity is designed for parity, not speed. For someone running WordPress DevRel, the practical read is that the Alliance will not initiate ambitious joint programs, but it lowers the cost of a bilateral one. The president is the primary contact for the other three organizations, which means the presidency year is the cheapest twelve months to get a counterpart on a call at Drupal, Joomla!, or TYPO3. Anything requiring all four to agree should be scoped as something no member could reasonably veto — a shared accessibility statement, a joint security disclosure norm, a co-signed regulatory comment — rather than a shared roadmap. The four projects also share a specific constituency: agencies and hosts that run more than one CMS. Content aimed at that constituency currently comes from vendors, not from the projects. A joint artifact aimed there would be new. ### For policy advocacy The CRA letter established the group's distinctive argument, and it transfers. CMS projects sit at the commerce layer, so security and product regulation written for infrastructure dependencies lands differently. That framing works for the CRA, the European Accessibility Act, product liability directives, and any future data or AI rule that reaches website operators. Having a four-project bloc means a regulator hears the same argument from four communities rather than one vendor's users. The presidency gives WordPress the convening seat for a year, which is the seat that decides what gets on the agenda even when it cannot decide the outcome. If there is a regulatory file worth a joint comment in the next twelve months, this is when to put it in front of the other three. The limit is real: the charter says the Alliance cannot represent members or enter contracts. Any joint filing is four signatures, not one entity's statement. Plan the timeline around four legal reviews. ### For contributor programs Nothing in the post or the charter describes contributor-level activity, which is the gap and therefore the opportunity. Contributor programs are where the parity problem disappears: a shared accessibility audit sprint, a joint translation glossary effort, or a cross-project security triage rotation does not require unanimity at the board layer, only two willing team leads. The presidency is cover to propose them. For the WordPress contributor experience specifically, the honest implication is small. This announcement changes no team's work this quarter. What it changes is the plausibility of a request: "the WordPress Foundation currently chairs the Alliance" is a better opener for a cross-project proposal than anything available last month, and it expires in roughly a year. ### For the governance record The post documents an institutional commitment with a link to a social platform. For a project that maintains its own news archive, that is a records-management gap worth closing. Anyone who needs to cite WordPress's 2024 OWA entry in three years will find either a live X post or nothing. ## 🧠 Learning Styles Assessment **Reading level estimate.** Flesch–Kincaid Grade Level ≈ 12.8 (approximately college freshman) and Flesch Reading Ease ≈ 39 (difficult), computed by hand over the 239-word source: roughly 12 sentences, about 19.9 words per sentence, and an estimated 1.75 syllables per word. The score is driven by sentence length and by policy vocabulary — "Cyber Resilience Act," "content management systems," "participation," "infrastructure." Both figures are manual estimates on a sample too small for a stable score; treat them as directional. #### 👀 Visual learners - Present: nothing. No diagram, chart, table, image, or code block. The post is three unbroken paragraphs. - Improve: a four-node diagram of the member organizations with the rotation order marked; a timeline showing 2023 CRA letter, 2024 WordPress participation, 2026 presidency; a simple table of what the president does versus what requires unanimity. #### 🔊 Aural learners - Present: nothing. No audio version, no podcast, no narration. - Improve: a two-minute audio summary would cover this post completely. A five-minute version could add the charter's governance rules, which is where the substance lives. #### 🗣️ Verbal learners - Present: reasonably well served. The prose defines the Alliance in its second sentence and explains the CRA argument in plain language without acronym soup. - Improve: define "Open Weights" and "Cyber Resilience Act" inline rather than relying on links; the CMS-versus-infrastructure distinction deserves one concrete example. #### 🧩 Kinesthetic learners - Present: one action — read the charter. - Improve: give a reader something to do. A link to Alliance meeting notes, a way to submit a policy concern, a contact address, or a call to join a cross-project channel. #### 🧠 Logical learners - Present: the causal chain from CRA work to 2024 participation to 2026 presidency is implicit and traceable. - Improve: state the term dates, the rotation rule, and the decision rule. All three are facts, all three are in the charter, and all three are what a logical reader will want. #### 🧑‍🤝‍🧑 Social learners - Present: the framing is collective throughout — "our work," "we share a belief," "welcoming everyone to contribute." - Improve: name the counterpart representatives at the other three organizations, and point to a forum where cross-project conversation happens. #### 🧘‍♀️ Solitary learners - Present: the charter link supports independent follow-up. - Improve: a short reading list — the Open Web Manifesto, the CRA text, the 2023 letter — would let a solitary reader go deep without asking anyone. #### 🌿 Naturalistic learners - Present: nothing. No sustainability or ecosystem-health framing. - Improve: "ecosystem" is the natural metaphor for four interdependent projects sharing a regulatory environment, and it is unused. Long-term maintenance and stewardship framing would fit the material. ## 📊 Accessibility Assessment Assessed against WCAG 2.2 AA, for the wordpress.org/news article page as a web document. The captured source is plain text, so page-level findings are inferred from the standard WordPress.org News template and flagged as such. #### Screen reader semantics - Present: the news template supplies an H1 post title, a main landmark, and a published-date element. The three-paragraph body maps to three `<p>` elements with no structural ambiguity. - Improve: the visible byline reads "wordpress.org" while the underlying record names Mary Hubbard, so a screen reader user hears an organization where a person is the author. That is not a WCAG failure but it is an information-parity gap. Relevant criteria: 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA). #### Keyboard navigation - Present: eight inline text links, all standard anchors, all reachable in reading order. No custom widgets, no modals, no scripted controls in the article body. - Improve: verify the visible focus indicator on inline links meets 2.4.11 Focus Not Obscured (Minimum) and 2.4.13 Focus Appearance, both new or strengthened in WCAG 2.2. Confirm the skip link lands on the article region. Criteria: 2.1.1 Keyboard (A), 2.4.7 Focus Visible (AA), 2.4.11 (AA). #### Contrast and readability - Present: the WordPress.org News theme uses dark text on white for body copy, which clears 4.5:1. - Improve: inline link color against white must clear 4.5:1 as text and the link must be distinguishable from surrounding text by more than color alone. Criteria: 1.4.3 Contrast (Minimum) (AA), 1.4.1 Use of Color (A), 1.4.11 Non-text Contrast (AA). #### Text resizing and reflow - Present: the template is responsive and the content is three paragraphs of flowing text, which is the easiest possible reflow case. - Improve: confirm no clipping at 200% zoom and at 400% in a 320 CSS-pixel viewport, and confirm text spacing overrides do not break the layout. Criteria: 1.4.4 Resize Text (AA), 1.4.10 Reflow (AA), 1.4.12 Text Spacing (AA). #### Media and captions - Present: not applicable — the post contains no audio, video, or images. Nothing to caption. - Improve: if a future follow-up adds a diagram of the Alliance structure, it needs alt text conveying the rotation order, not just "diagram." Criteria: 1.1.1 Non-text Content (A), 1.2.2 Captions (A) if media is added. #### Forms and interactions - Present: no forms in the article body. Site-level search and any comment form are template-supplied. - Improve: where the template offers search or subscription, confirm visible labels, programmatic association, and that no interaction depends on a drag gesture. Criteria: 3.3.2 Labels or Instructions (A), 2.5.8 Target Size (Minimum) (AA), 2.5.7 Dragging Movements (AA). #### Standards reference - Content-level gaps map to 1.3.1 (byline/author parity), 2.4.4 Link Purpose (In Context) (A) — four of the eight link texts are bare project names, which is adequate in context but tells a link-list user nothing about destination — and 3.1.3 Unusual Words (AAA, aspirational) for "Cyber Resilience Act" and "Open Weights," both used without definition. The single clearest AA-relevant content fix is making link text describe destinations: "Open Website Alliance charter" does this well, "Drupal" does not. ## 🌍 DEIB Assessment #### Cultural breadth - Present: the post spans two regulatory regions — an EU regulation and a US AI policy letter — and names four projects with different national centers of gravity (TYPO3 is German-rooted, Joomla! and Drupal have distinct international communities). It names "translators" explicitly among contributor roles. - Improve: no locale beyond the EU and US appears. The CMS market outside those two regions is large and unmentioned. Publishing translations of this announcement, and citing any non-Western policy engagement, would widen it. #### Inclusive language - Present: gender-neutral throughout. First-person singular for the author, first-person plural for the project. No idioms that would resist translation. "Freedom to use, change, and share" is plain-language framing of software freedom without the jargon. - Improve: "Cyber Resilience Act," "Open Weights," and "Alliance charter" are used as known terms. A reader outside policy work will not know them, and the post asks them to click to find out. #### Neurodiversity support - Present: short. 239 words is a low-load read, and the three paragraphs follow a clean announce-then-context-then-invite structure. - Improve: no headings, no lists, no bolded key facts. Three dense paragraphs of policy prose with no visual anchors is harder to scan than its length suggests. One bolded sentence carrying the core fact, or two subheadings, would cost nothing. #### Representation - Present: the contributor roles named — "developers, translators, educators, and other contributors" — deliberately extend past developers, which is a meaningful inclusion given how often open-source advocacy collapses to code. - Improve: one voice speaks here. No counterpart from Drupal, Joomla!, or TYPO3 is quoted in a post about a four-project collaboration. A single sentence from each would make the collaboration visible rather than asserted. #### Psychological safety - Present: the framing is welcoming and non-defensive. "Welcoming everyone to contribute" and the freedom-to-use-change-share line set an open tone. No adversarial framing of any party, including regulators — the CRA is described as something to inform, not fight. - Improve: no entry point is offered. A post that says everyone is welcome to contribute, in the context of a body with no public participation path, creates a small gap between invitation and access. Naming where to raise a concern would close it. ## ✅ Logical Validity This is an official announcement, not an argument. It asserts a fact about a role, supplies context, and issues an invitation. Assessed on that basis: does each claim have support, and does the post's connective tissue outrun its sources? #### Strong reasoning - **The causal chain is well-formed and documented.** Paragraph 2 argues: the four projects collaborated on the CRA response, that collaboration led to formal participation in 2024, and participation now yields the presidency. Each step is plausible, the order is chronologically consistent (the CRA post is dated August 2023, participation 2024, presidency 2026), and the strongest step carries a first-party citation. This is sound inductive support for the implicit claim that the Alliance is a working relationship rather than a letterhead. - **The CMS-versus-infrastructure distinction is a genuine analytical move**, and it does real work: > [!quote] Source paragraph 2 > We asked policymakers to account for that economic role when setting security requirements The premise — CMS platforms carry commercial activity in a way infrastructure libraries do not — supports the conclusion that they warrant distinct regulatory treatment. The reasoning is valid and the premise is defensible. It would be stronger with a figure attached: any share-of-web or share-of-commerce number would convert an assertion into evidence. - **Mission language is positioning, not fallacy.** "Democratize publishing" and "the freedom to use, change, and share" are stated values, framed as values. They explain motive rather than substituting for evidence, which is the legitimate use of mission language in an announcement. No appeal to emotion is doing argumentative work here. - **The invitation is honest.** The post ends by directing readers to the primary document rather than characterizing it. Given how much the post omits, pointing at the charter is the right move. #### Fallacies No formal fallacies. Three genuine weaknesses, in descending severity: - **Weak documentation for an institutional claim.** "WordPress announced its participation in the Alliance in 2024" links to a post on X. A social post is thin evidence for an institutional commitment: it is third-party hosted, deletable, unarchived by the project, and carries no membership detail. The claim is very likely true — the charter's 12-month eligibility rule is consistent with a 2024 entry preceding a 2026 presidency — but the citation does not establish it. The fix is a first-party record on wordpress.org. Stated plainly: the link is inadequate for the claim, not evidence that the claim is false. - **Association presented as continuity.** "This commitment to openness builds on efforts such WordPress's recent signing of the Open Weights and American AI Leadership letter" places a WordPress-only US AI action in a paragraph about a four-project EU-focused alliance. Both linked posts are accurate about their own facts, and neither connects the two efforts. The sentence does not claim an Alliance role, so it is not false — but the adjacency invites a reader to record an OWA position on AI policy that does not exist. (The sentence also contains a typo: "efforts such WordPress's" is missing "as.") - **An unsupported gap where the material is load-bearing.** The post states the role rotates but gives no term, no duties, and no start date. A reader cannot evaluate what has been announced. This is an omission rather than an error, and the charter link mitigates it, but in a governance announcement the omission is itself the finding. #### Tone of voice Warm, institutional, and deliberately low-key. It opens with "I'm happy to announce," which is personal, then settles into the collective register WordPress.org News usually uses. It is non-adversarial toward regulators — the CRA is something to inform, not resist — and non-triumphal about the presidency, which is consistent with a rotating role that everyone eventually holds. The closing shifts to invitation. Across 239 words the register moves from personal to institutional to communal without a jarring seam, which is competent announcement writing. ## 🛡️ DARVO Analysis Not applicable in substance. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response to accusation, and there is no accusation, defense, or adversarial party here. - **Deny:** none. The post denies nothing and minimizes nothing. Its omissions — term length, duties, forward agenda — read as brevity rather than avoidance, and the charter link points at the very document that fills them. - **Attack:** none. No party is criticized. Proprietary CMS vendors, regulators, and other open-source foundations all go unmentioned or are treated neutrally. The 2023 CRA position was framed as an ask, not a grievance, and this post preserves that framing. - **Reverse victim/offender:** none. No victim is claimed. The economic-role argument asserts relevance, not injury. - Emotional cues are limited to "happy to announce" and the closing invitation. No urgency, no threat, no grievance rhetoric. ## 🎯 Conclusion WordPress holds the Open Website Alliance presidency through Mary Hubbard, representing the WordPress Foundation, in a role that rotates among the four member organizations behind Drupal, Joomla!, TYPO3, and WordPress. The post confirms the fact and little else. Everything a governance reader needs — a one-year default term extendable by six-month increments, alphabetical rotation, 12-month eligibility, unanimous decision-making, and the Alliance's explicit inability to contract or represent its members — comes from the charter the post links in its last sentence. The Alliance's single documented output remains the 2023 Inter-CMS Working Group letter on the EU Cyber Resilience Act, and its most transferable asset is the argument that letter made: CMS platforms sit at the commerce layer, so rules written for infrastructure dependencies land differently on them. That argument will apply again. Practical next steps for a reader working in DevRel, community, or open-source governance: - Read the charter before citing the post. The governance facts are only in the charter. - Treat the presidency year as a convening window, not an authority. Unanimity caps what the body can produce; the primary-contact role is what makes a bilateral call easy to schedule. - Propose a small joint deliverable now. Accessibility or coordinated disclosure are the two candidates no member could reasonably veto. - Push for a first-party record of the Foundation's alliance memberships on wordpress.org. Documenting institutional commitments on a social platform is a records gap that will cost someone a citation later. ## 🔄 Refactor Appendix — WordPress Takes Its Turn Leading the Open Website Alliance > 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 Split Pad (H3) #### [L1] OWA presidency rotates among four CMS member organizations > [!quote] Source paragraph 1 > I represent the WordPress Foundation in this role, which rotates among the Alliance’s members. **Context & use**: - Paragraph 1, the post's core governance claim. - Establishes that the WordPress Foundation — not Automattic, not WordPress.org — is the member entity holding the seat. The linked charter adds that rotation is alphabetical with a one-year default term, which the post omits. **Tags**: #xref **Highlight**: https://wordpress.org/news/2026/09/owa-president/  #### [L2] CMS projects argue from commerce, not infrastructure dependency > [!quote] Source paragraph 2 > We asked policymakers to account for that economic role when setting security requirements **Context & use**: - Paragraph 2, summarizing the 2023 Inter-CMS Working Group position on the EU Cyber Resilience Act. - This is the Alliance's transferable argument. Infrastructure projects argue from dependency; CMS projects argue that their software carries commercial transactions. Reusable for the European Accessibility Act, product liability rules, and future AI regulation touching website operators. **Tags**: #xref #articleseed **Highlight**: https://wordpress.org/news/2023/08/concerns-over-the-european-unions-cyber-resilience-act-cra/  #### [L3] Cross-project collaboration counts as mission execution > [!quote] Source paragraph 3 > Our mission to democratize publishing means giving anyone a voice and welcoming everyone to contribute. **Context & use**: - Paragraph 3, tying Alliance work back to the WordPress mission statement. - Useful framing device: recasting external collaboration as existing-mission execution lowers the internal justification cost for cross-project work. Applies directly when proposing a cross-CMS accessibility or disclosure program. **Tags**: #xref #share **Highlight**: https://wordpress.org/news/2026/09/owa-president/  #### [L4] Alliance charter bars contracting and representation > [!quote] Source paragraph 3 > I invite you to read the Open Website Alliance charter to learn more about the commitments its members share and how the Alliance works. **Context & use**: - Paragraph 3, the post's only call to action — and the pointer that supplies everything the post omits. - Content sourced from the linked charter, not the post: the Alliance is not a legal entity, cannot represent members or enter contracts for them, and decides by unanimous vote excluding abstentions. That is the ceiling on what any presidency can deliver. **Tags**: #xref **Highlight**: https://openwebsitealliance.org/charter.html  ### 🧠 Atomic Split Pad (H4) #### [P1] Unanimity governance caps a coalition's output at its least ambitious member **Claim** (one sentence, Courtney's voice): A multi-party body that requires unanimous consent can only ship what every member would have been willing to ship alone, so its value is convening access rather than collective output. **Evidence pointer**: [[#L4]] — the OWA charter's unanimous-vote rule paired with a presidency limited to primary contact and meeting logistics. **Scope & conditions**: Holds for small coalitions of peer organizations with no shared budget or staff. Breaks down where a body has paid staff who can produce drafts members ratify, or where abstention is common enough that unanimity-excluding-abstentions functions as a majority rule in practice. **Links** (≥1 with annotation): - [[Open-source governance models]] — because extends - [[Consensus versus majority decision rules]] — because contrasts on veto distribution - [[Cross-CMS policy advocacy]] — because applies-in multi-project regulatory comment  #### [P2] Institutional commitments documented only on social platforms are not documented **Claim** (one sentence, Courtney's voice): An organization that records a membership, partnership, or commitment solely in a third-party social post has created no durable record, because the platform controls availability and the format carries no terms. **Evidence pointer**: [[#L1]] — this post cites a 2024 X post as the sole source for WordPress joining the Alliance, while citing first-party news posts for both other substantive claims. **Scope & conditions**: Holds wherever the organization operates its own archive and chose not to use it. Does not apply to genuinely ephemeral announcements, or to organizations with no publishing infrastructure of their own. **Links** (≥1 with annotation): - [[Project governance records]] — because extends - [[Link rot and citation durability]] — because evidence-for - [[WordPress.org news archive practices]] — because applies-in first-party documentation  ### ✏️ Fleeting Queue - [F1] Who held the OWA presidency before WordPress, and what did that term produce? No predecessor is named anywhere in the post — https://openwebsitealliance.org/charter.html #fleeting #inbox - [F2] Check whether the Inter-CMS Working Group's two CRA concerns — the "unfinished software" prohibition and the "commercial activity" definition — survived into the adopted regulation. That is the only real measure of whether the collaboration worked — https://wordpress.org/news/2023/08/concerns-over-the-european-unions-cyber-resilience-act-cra/ #fleeting #inbox - [F3] Confirm which WordPress legal entity appears on the OWA roster. The post says the WordPress Foundation; the charter requires one legal entity per project but the summary names no members — https://wordpress.org/news/2026/09/owa-president/ #fleeting #inbox - [F4] Does any OWA member publish meeting minutes? If none do, the WordPress presidency year is the moment to propose it #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Read the full Open Website Alliance charter and record the presidency term dates, rotation order, and decision rules in the WP governance wiki — openwebsitealliance.org/charter.html #things - [ ] Draft a cross-CMS accessibility collaboration proposal to raise during the WordPress presidency year, scoped so no member would veto it — OWA presidency window closes ~September 2027 #things  📄 **Full text:** [[Full Document Contents/Articles/WordPress Takes Its Turn Leading the Open Website Alliance.md|WordPress Takes Its Turn Leading the Open Website Alliance by Mary Hubbard]] ## Highlights - I’m happy to announce that I am now serving as president of the [Open Website Alliance](https://openwebsitealliance.org/) (OWA), representing the WordPress Foundation. The Alliance brings together the community organizations behind [Drupal](https://www.drupal.org/), [Joomla!](https://www.joomla.org/), [TYPO3](https://typo3.org/), and WordPress to advocate for open source and share practices that benefit their projects. I represent the WordPress Foundation in this role, which rotates among the Alliance’s members. ([View Highlight](https://read.readwise.io/read/01m34gb1bw86yndzyqt4fqrfkx)) - Note: The news: the WordPress Foundation now holds the OWA's rotating presidency, alongside Drupal, Joomla! and TYPO3. - Tags: atom/literature/h2 - WordPress [announced its participation in the Alliance in 2024](https://x.com/WordPress/status/1755516866485707064), building on our work with Drupal, Joomla!, and TYPO3 to [respond to the European Union’s Cyber Resilience Act](https://wordpress.org/news/2023/08/concerns-over-the-european-unions-cyber-resilience-act-cra/). While many open source projects focus on underlying digital infrastructure, our content management systems power the websites where businesses reach customers and sell products and services. We asked policymakers to account for that economic role when setting security requirements, while respecting how communities of developers, translators, educators, and other contributors build and maintain the software. We share a belief that everyone should have the freedom to use, change, and share the tools they rely on. ([View Highlight](https://read.readwise.io/read/01m34gazv8gtg57jd4xcrj87t2)) - Note: The Alliance's origin and policy argument: CMSes are economic infrastructure, and CRA-style security rules should account for volunteer contributor communities. - Tags: atom/literature/h1