Automattic’s Anne McCarthy joins the PHP Foundation board  🔗 **Source:** [Automattic’s Anne McCarthy joins the PHP Foundation board](https://www.therepository.email/automattics-anne-mccarthy-joins-the-php-foundation-board) > [!note]+ Document Notes > tags: [php, php-foundation, open-source-governance, wordpress, automattic, foundation-governance] > author: The Repository > source: The Repository > reference: https://www.therepository.email/automattics-anne-mccarthy-joins-the-php-foundation-board > date created: 2026-08-05 > > > [!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: Automattic’s Anne McCarthy joins the PHP Foundation board > <!-- 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--automattics-anne-mccarthy-joins-the-php-foundation-board) - [🧰 Template Library](#-template-library) ### 🔗 References - [The Repository report](https://www.therepository.email/automattics-anne-mccarthy-joins-the-php-foundation-board) - [PHP Foundation announcement](https://thephp.foundation/blog/2026/08/04/anne-mccarthy-joins-the-board/) - [PHP Foundation sponsorship levels](https://thephp.foundation/sponsor/) - [Related report: Anne McCarthy named WordPress 7.1 release lead](https://www.therepository.email/anne-mccarthy-named-wordpress-7-1-release-lead) ## 📝 Summary - **What happened:** The PHP Foundation Governing Board unanimously appointed Anne McCarthy, Automattic’s Architecture and Open Source Director, as Automattic’s platinum-sponsor representative. - **Financial and governance context:** Automattic is a founding member and platinum sponsor. The Foundation publicly prices platinum membership at $100,000 per year. The Repository reports that the Foundation funds 12 developers working on PHP core. - **Why it matters:** WordPress depends on PHP, while WordPress organizations and contributors represent a large part of PHP’s user ecosystem. The appointment creates a formal governance channel between Automattic and the Foundation during a period when McCarthy is also leading WordPress 7.1. - **Stated intent:** McCarthy said they want to bring the PHP and WordPress communities closer, support people who maintain PHP, and help bring the next generation into the ecosystem. - **Stakeholders:** PHP core developers, Foundation board members and sponsors, Automattic, WordPress contributors, hosting companies, framework communities, application developers, and end users who depend on maintained PHP releases. - **Risks and tradeoffs:** Sponsor representation brings funding and operational knowledge, but it can raise questions about influence, conflicts, accountability, and whether community voices have comparable access. The article reports the appointment; it doesn’t evaluate board voting rights, recusal policy, term length, or measurable outcomes. - **Disclosure:** The Repository states that Automattic-owned Pressable sponsors the publication. That disclosure is material because the subject is an Automattic executive and sponsor representative. - **Bottom line:** The appointment can improve WordPress–PHP coordination, but its public value should be assessed through transparent board decisions, community consultation, and outcomes—not the appointment announcement alone. ## 📖 Main Content The PHP Foundation says its Governing Board includes people from the PHP community, core contributors, and sponsors. The board unanimously added Anne McCarthy as the representative attached to Automattic’s platinum sponsorship. The funding relationship is part of the role, not incidental background. Automattic is a founding member and platinum sponsor, and the Foundation’s published sponsorship page sets that tier at $100,000 annually. Sponsor representation can give the board product and user-ecosystem knowledge while helping fund paid PHP core work. McCarthy’s background connects several layers of the stack. They have 15 years of technical and open-source experience, joined Automattic in 2014, and now direct architecture and open-source work. They are also leading WordPress 7.1, scheduled for August 19 during WordCamp US 2026. The article frames the appointment as a bridge between PHP and WordPress. McCarthy said they want the communities closer together and pointed to WordCamp US as a place to begin conversations. They also described learning PHP as a student and wanting to bring newer contributors into the fold. The board context is broader than WordPress. The Repository names representatives from JetBrains, Symfony, Tideways, Private Packagist, Tighten, and Perforce, plus former WordPress Executive Director Josepha Haden. That mix makes the board a coordination forum among funders, tools, frameworks, language maintainers, and major user communities. The article closes with a sponsorship disclosure: Automattic-owned Pressable sponsors The Repository. The disclosure doesn’t invalidate the reporting, which links to primary sources and names the financial relationship, but readers should retain it when evaluating framing. ## 🗒️ Notes - Appointment method: unanimous Governing Board vote, according to the Foundation and The Repository. - Seat type: platinum-sponsor representative for Automattic, not an independently elected community seat. - Sponsor price: $100,000 per year on the Foundation’s current sponsorship page. - Foundation capacity: the report says 12 developers are funded to work on PHP core. - McCarthy’s roles overlap: Automattic architecture/open-source director, WordPress 7.1 release lead, and PHP Foundation board member. - McCarthy’s stated bridge goal matters because WordPress depends on PHP while sometimes diverging from current PHP practices and version adoption. - The news item doesn’t specify term length, committee assignments, voting scope, recusal rules, board minutes, or performance measures. - Funding and representation should be analyzed separately: sponsorship supports shared infrastructure; a board seat creates governance influence. - Cross-ecosystem representation can surface user needs, compatibility issues, adoption barriers, and contributor pipelines. - The appointment also concentrates responsibilities in one person, which may create time, role-conflict, and accountability pressures. - The Repository’s Pressable disclosure is clear and placed in the article; it should travel with summaries of the report. - The primary announcement provides praise and a welcome statement, not an independent governance assessment. ## 📚 References - The Repository. [“Automattic’s Anne McCarthy joins the PHP Foundation board”](https://www.therepository.email/automattics-anne-mccarthy-joins-the-php-foundation-board), August 5, 2026. - The PHP Foundation. [“Anne McCarthy Joins The PHP Foundation Board”](https://thephp.foundation/blog/2026/08/04/anne-mccarthy-joins-the-board/), August 4, 2026. - The PHP Foundation. [Sponsorship and company membership](https://thephp.foundation/sponsor/), listing platinum membership at $100,000 per year. - The Repository. [“Anne McCarthy named WordPress 7.1 release lead”](https://www.therepository.email/anne-mccarthy-named-wordpress-7-1-release-lead), relevant to role overlap and release timing. ## 🗣️ Paraphrase The PHP Foundation has added Anne McCarthy to its Governing Board. The board approved the appointment unanimously, and McCarthy fills the seat connected to Automattic’s highest sponsorship level. Automattic helped found the Foundation and contributes at least $100,000 per year as a platinum sponsor. The Foundation uses its resources to pay developers working on the PHP language. McCarthy brings long experience in WordPress and open source. They joined Automattic in 2014 and now direct architecture and open-source work while leading the WordPress 7.1 release. McCarthy wants the new role to strengthen ties between PHP and WordPress. They also connect the appointment to their own experience learning PHP and to supporting future contributors. The Foundation board includes people tied to sponsors, developer tools, frameworks, and major PHP communities. McCarthy’s appointment increases direct WordPress and Automattic representation in that group. The Repository reports the financial and organizational context and discloses that Pressable, an Automattic-owned company, sponsors its publication. ## 📰 Newsletter ### WordPress gets another seat in PHP’s governance room Anne McCarthy has joined [The PHP Foundation’s Governing Board](https://thephp.foundation/blog/2026/08/04/anne-mccarthy-joins-the-board/) as Automattic’s platinum-sponsor representative. That’s a useful bridge: WordPress depends on PHP, Automattic helps fund the Foundation, and McCarthy is also leading WordPress 7.1. The governance question comes after the welcome post. What decisions become clearer, which contributor pipelines improve, and how will the board show that sponsor representation serves the wider PHP ecosystem? [The Repository’s report](https://www.therepository.email/automattics-anne-mccarthy-joins-the-php-foundation-board) includes the sponsorship context and discloses that Automattic-owned Pressable sponsors the publication. ## ✅ Action Items #### DevRel - Publish a PHP–WordPress collaboration agenda with owners, milestones, and feedback channels. - Bring PHP maintainers into WordPress developer events and WordPress maintainers into PHP forums. - Measure contributor pathways, compatibility improvements, and resolved cross-project issues. #### OSPO - Document sponsor-seat expectations, conflicts, recusals, term limits, and reporting duties. - Track the public value created by cross-project funding and representation. - Support contributor mobility between WordPress, PHP core, tools, and frameworks. #### Community - Hold open listening sessions before setting cross-ecosystem priorities. - Include independent developers, hosts, agencies, framework users, and underrepresented contributors. - Publish minutes and follow-ups so participation produces traceable decisions. #### WordPress - **Core:** identify PHP compatibility and modernization issues needing Foundation coordination. - **Core Performance:** coordinate benchmarks and runtime-performance priorities with PHP maintainers. - **Core AI:** separate AI roadmap needs from language-governance priorities and disclose dependencies. - **Core Program Team:** track cross-project commitments, owners, and release dependencies. - **Mobile:** document server-side PHP constraints affecting app-backed WordPress experiences. - **Playground:** test PHP-version behavior and share reproducible cases upstream. - **Community:** host structured PHP–WordPress sessions at WordCamps and contributor days. - **Training:** create learning paths from WordPress development into modern PHP contribution. - **Marketing:** explain the relationship without presenting Automattic as the whole WordPress project. - **Support:** aggregate PHP-version and compatibility pain points with clear reproduction data. - **Design:** make cross-project proposals and decision records easier to scan. - **Documentation:** align PHP requirements, deprecations, migration guides, and examples. - **Photos:** Not applicable to this source; no direct action follows beyond normal governance transparency. - **TV:** record and caption PHP–WordPress governance and technical sessions. - **Polyglots:** translate high-impact PHP compatibility and migration guidance. - **Accessibility:** include accessibility consequences in runtime and compatibility decisions. - **Meta:** expose contributor, meeting, and decision data for cross-project work. - **CLI:** test commands across supported PHP versions and report upstream regressions. - **Hosting:** share version-adoption data and migration barriers without exposing customer data. - **Tide:** align scanner runtime coverage with supported PHP and WordPress versions. - **Openverse:** track PHP dependencies and upgrade paths for service components. - **Themes:** communicate PHP compatibility needs that affect theme development and review. - **Plugins:** provide maintainers with test matrices, migration help, and deprecation timelines. #### The WPOCC - Fund independent participation in PHP–WordPress coordination so sponsor voices aren’t the only resourced voices. - Support contributor fellowships that build modern PHP skills inside WordPress. ### FAIR - Require portable governance records, open minutes, conflict disclosures, and exit provisions. - Keep sponsor funding transparent while protecting technical decision-making from capture. ## 🧪 Hypotheses - H1: Formal WordPress representation on the PHP Foundation board reduces unresolved cross-project compatibility issues. - H2: Publishing board minutes and conflict disclosures increases community trust in sponsor-appointed representatives. - H3: Joint PHP–WordPress contributor programs increase first-time and retained PHP contributors from the WordPress ecosystem. - H4: Sponsor seats improve funding stability but increase perceived capture unless community seats have comparable transparency and access. - H5: Combining release leadership and foundation governance accelerates coordination but raises role-overload risk. ### 📊 Methodology - **For H1:** Track cross-project issues, time to resolution, release blockers, and regressions before and after the appointment. - **For H2:** Survey PHP and WordPress contributors under different transparency practices; compare trust and understanding. - **For H3:** Follow cohorts through training, first contribution, review, and six- or twelve-month retention. - **For H4:** Compare foundations with sponsor-appointed, elected, and mixed boards; measure funding concentration and perceived legitimacy. - **For H5:** Map commitments, meeting load, decision latency, and missed milestones while protecting personal workload data. ### ❓ Questions - What voting rights, term length, and recusal rules apply to the platinum-sponsor seat? - Which PHP–WordPress issues will McCarthy prioritize, and how will communities help set that list? - How will the board distinguish Automattic’s interests from WordPress community interests? - Are board minutes, attendance, votes, and conflict disclosures public? - What channel lets independent WordPress contributors reach the board without going through Automattic? - How will the Foundation assess whether the seat produces public benefit? - Does the board have enough regional, employer, project, and contributor-role diversity? ### 🔮 Future Research - Map the Foundation’s governance rules, board categories, terms, voting rights, and sponsor relationships. - Compare PHP Foundation governance with Python, Rust, Linux, Apache, and other language or project foundations. - Study whether major user ecosystems influence runtime roadmaps and adoption patterns. - Track PHP version adoption and modernization work across WordPress hosting and plugin ecosystems. - Interview community members about perceived legitimacy and access after sponsor appointments. - Follow McCarthy’s stated community-bridging goals through public artifacts and outcomes. ### 💡 Implications - **Practice:** Cross-project representatives need a published agenda, listening process, and results log. - **Policy:** Sponsor seats should have clear duties, conflicts rules, recusal procedures, and terms. - **Security:** Better PHP–WordPress coordination can improve supported-version adoption and vulnerability response. - **Education:** Contributor pipelines can connect WordPress developers with modern PHP and language-level work. - **Funding:** Platinum sponsorship supports paid maintenance, while independent participation may need separate funding. - **WordPress:** The seat creates access but doesn’t make Automattic synonymous with the open-source project. ### 🧠 Learning Styles Assessment - **Reading level estimate:** Approximately grade 9–11 by qualitative review of sentence length, governance terms, and linked context; no formal readability score was calculated. #### 👀 Visual learners - Present: a lead photograph with descriptive alt text. - Improve: add a board-composition diagram and a funding-to-governance map. #### 🔊 Aural learners - Present: Not applicable; the captured article has no audio. - Improve: offer a short narrated summary and recorded interview. #### 🗣️ Verbal learners - Present: concise reporting, quotations, role descriptions, and links. - Improve: define governing board, sponsor representative, and platinum tier. #### 🧩 Kinesthetic learners - Present: event and community links suggest places to participate. - Improve: include concrete steps for proposing an issue or joining a PHP–WordPress session. #### 🧠 Logical learners - Present: role, funding tier, experience, and board composition are stated. - Improve: add decision rights, term length, and governance process. #### 🧑‍🤝‍🧑 Social learners - Present: McCarthy identifies WordCamp US as a conversation venue. - Improve: add moderated discussion prompts and public follow-up notes. #### 🧘 Solitary learners - Present: primary-source links support independent verification. - Improve: add a governance reading list and a checklist for evaluating board appointments. #### 🌿 Naturalistic learners - Present: sustainability and contributor succession are central themes. - Improve: connect funding and governance to the lifecycle of shared infrastructure. ### 📊 Accessibility Assessment #### Screen reader semantics - The lead image has descriptive alt text; headings and link purpose depend on the page template. Verify WCAG 1.1.1, 1.3.1, and 2.4.6. #### Keyboard navigation - Links should remain reachable with visible focus under WCAG 2.1.1 and 2.4.7. #### Contrast and readability - Check text, link, caption, and disclosure contrast under 1.4.3 and 1.4.11. #### Text resizing and reflow - The article should reflow at 200% zoom and narrow widths under 1.4.4 and 1.4.10. #### Media and captions - Not applicable; no time-based media appears in the captured article. #### Forms and interactions - Subscription and support controls need labels, errors, and accessible status messages under 3.3.1, 3.3.2, and 4.1.3. #### Standards reference - Primary WCAG 2.2 AA mapping: 1.1.1, 1.3.1, 1.4.3, 1.4.4, 1.4.10, 1.4.11, 2.1.1, 2.4.6, 2.4.7, 3.3.1, 3.3.2, and 4.1.3. ### 🌍 DEIB Assessment #### Cultural breadth - Present: The article connects international open-source ecosystems and several organizations. - Improve: include regional and non-corporate perspectives on board composition and priorities. #### Inclusive language - Present: McCarthy’s they/them pronouns are used consistently and roles are described clearly. - Improve: define governance and sponsorship terms for readers outside foundation structures. #### Neurodiversity support - Present: short paragraphs, concrete facts, and links support scanning. - Improve: add a fact box separating appointment, funding, roles, and open questions. #### Representation - Present: The article names one new board member and several represented organizations. - Improve: report the board’s geographic, employer, gender, contributor-role, and community-seat composition. #### Psychological safety - Present: The report avoids personal attacks and keeps scrutiny on roles and structures. - Improve: provide a moderated channel for governance questions and disagreement. ### ✅ Logical Validity #### Strong reasoning - The report links the primary Foundation announcement and McCarthy’s statement. - It distinguishes the appointment from McCarthy’s background, stated goals, and sponsorship context. - The Pressable disclosure gives readers relevant information about the publication’s financial relationship. #### Fallacies - Not applicable to this source: the article is brief factual reporting and doesn’t make a broad causal or moral argument. Its main limitation is missing governance detail, not a clear logical fallacy. #### Tone of voice - Straightforward, contextual, and mildly celebratory through quoted source language, while retaining financial and disclosure context. ### 🛡️ DARVO Analysis - **Deny:** Not applicable; the article doesn’t deny an allegation or harm. - **Attack:** Not applicable; it doesn’t attack a critic or undermine credibility. - **Reverse victim/offender:** Not applicable; no accused party is recast as a victim. - This is an appointment report, so DARVO isn’t a fitting analytical frame. ## 🎯 Conclusion Anne McCarthy’s appointment gives Automattic a named representative on The PHP Foundation Governing Board at the platinum sponsorship level. The role can strengthen technical coordination, contributor pathways, and mutual understanding between PHP and WordPress. The meaningful test is what follows: a public agenda, accessible consultation, conflict handling, board transparency, and measurable cross-project outcomes. Readers should retain The Repository’s Pressable sponsorship disclosure when assessing the report’s framing. ## 🔄 Refactor Appendix — Automattic’s Anne McCarthy joins the PHP Foundation board ### 📚 Literature Atoms (H3) ### [H1] Platinum sponsorship creates formal board representation > [!quote] ID:rw_01kz90rskaq1fp1fk2t5jv1xhr > Anne McCarthy, Automattic’s Architecture and Open Source Director, has joined the PHP Foundation’s Governing Board as Automattic’s platinum sponsor representative. **Context & use**: - Opening paragraph. - The seat is explicitly tied to Automattic’s platinum sponsorship. **Tags**: #xref #articleseed **Highlight**: [view highlight](https://read.readwise.io/read/01kz90rskaq1fp1fk2t5jv1xhr) <!-- atomicity: 1 idea ✓ --> ### [H2] The board spans multiple PHP constituencies > [!quote] ID:rw_01kz90rtdspr450qhn8td9bph2 > The PHP Foundation’s 10-member board includes representatives from JetBrains, Symfony, Tideways, Private Packagist, Tighten, and Perforce, as well as former WordPress Executive Director Josepha Haden. **Context & use**: - Board-composition paragraph. - Governance draws input from sponsors, tools, frameworks, and user ecosystems. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01kz90rtdspr450qhn8td9bph2) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Sponsor funding and governance influence require separate accounting **Claim**: Open-source foundations should report sponsor funding separately from the governance influence attached to sponsor seats. **Evidence pointer**: [[#H1]] **Scope & conditions**: Applies when financial tiers provide representation; it doesn’t assume that sponsor participation is improper. **Links**: - [[Open-source governance]] — because extends financial transparency into decision rights - [[Foundation sustainability]] — because contrasts stable funding with capture risk - [[WordPress and PHP coordination]] — because applies-in shared infrastructure governance <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Map PHP Foundation board categories and voting rights — https://thephp.foundation/ #fleeting #inbox - [F2] Track public PHP–WordPress outcomes from McCarthy’s appointment — governance follow-up #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a sponsor-seat transparency checklist — open-source foundations #things - [ ] Collect PHP–WordPress collaboration priorities at WordCamp US — contributor feedback #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Automattic’s Anne McCarthy joins the PHP Foundation board.md|Automattic’s Anne McCarthy joins the PHP Foundation board by The Repository]] ## Highlights - Anne McCarthy, Automattic’s Architecture and Open Source Director, has [joined the PHP Foundation’s Governing Board](https://thephp.foundation/blog/2026/08/04/anne-mccarthy-joins-the-board/) as Automattic’s platinum sponsor representative. ([View Highlight](https://read.readwise.io/read/01kz90rskaq1fp1fk2t5jv1xhr)) - Note: The appointment is explicitly a platinum-sponsor representative seat, so funding and governance representation should be tracked separately. - Tags: foundation-governance, open-source-funding - The PHP Foundation’s 10-member board includes representatives from JetBrains, Symfony, Tideways, Private Packagist, Tighten, and Perforce, as well as former WordPress Executive Director Josepha Haden. ([View Highlight](https://read.readwise.io/read/01kz90rtdspr450qhn8td9bph2)) - Note: The board mixes companies, frameworks, developer tools, and WordPress experience; the article does not explain voting rights or seat categories. - Tags: open-source-governance, php-ecosystem