Skip to content

Who holds open source leadership when companies pay for the code?

In WordPress open source leadership, Automattic held the most placed team rep seats every year from 2018 to 2026. I found no cap; three of ten bodies have one.

Courtney
Nov 19, 202617 min read

f you’ve picked someone to speak for your team at work, you know who holds the mic. In WordPress, the open source software behind many websites, the closest seat in its open source leadership to that mic is the team rep. Still, one employer holds the biggest placed block of those seats. Automattic, the company behind WordPress.com and WooCommerce, held the most placed rep seats, or tied for the most, every year from 2018 to 2026, though never most of them.12 (A placed seat is one where I found the rep’s employer.) I found no written rule in WordPress that caps any one employer’s share.

🔗 My ties, before any verdict

I work at Pantheon, a WordPress and Drupal host that competes with WP Engine, another WordPress host. It also competes with WordPress VIP, the enterprise service from Automattic, the company behind WordPress.com. At GoDaddy, I started and ran its Five for the Future program, which pledges staff time to WordPress, until July 2026.

Separately, I chose which groups GoDaddy funded:

  • The PHP Foundation, which pays developers to work on the PHP language.
  • OpenJS, the foundation behind Node.js and other JavaScript projects.
  • W3C, the World Wide Web Consortium, a web standards body.
  • PHP_CodeSniffer, a tool that checks code style.
  • The WPOCC, a WordPress community collective where I’m a co-founding board member.

I’m also an active member of the Technical Steering Committee for FAIR, the FAIR Package Manager, which distributes WordPress plugins and themes. It’s a Linux Foundation project; the Linux Foundation is a nonprofit that hosts open source projects. Drupal is another open source content management system, and Pantheon is a platinum Drupal Certified Partner.3 I was a Training Team rep, and in 2022 GoDaddy sponsored those hours.4 My own seats are in this count.

Key takeaways

  • The big picture: Automattic’s share of WordPress rep seats ran from 13 to 26 percent a year from 2018 to 2026, counting placed seats.5
  • By the numbers: It never held a rep seat on every team. Its peak was 8 of 14 teams, in 2023.6
  • Why it matters: Three of the ten open source projects and standards bodies I read cap one employer’s share of a leadership body. That cap would bind any company that grew large.789
  • Yes, but: WordPress says its reps don’t decide alone, so rep seats are only one part of leadership in that open source project.10
/* Zine treatment for the Yoast AI summary (2026-11-06). Uses theme tokens so dark mode follows. Move to courtneyr-child once approved. */ .wp-block-yoast-seo-ai-summarize{position:relative;background:var(--cr-surface-elevated);color:var(--cr-ink);border:var(--cr-border-thick);box-shadow:var(--cr-shadow-hard);padding:2.1rem 1.5rem 1rem;margin:2.75rem 0 2.25rem;counter-reset:cr-takeaway} .wp-block-yoast-seo-ai-summarize>h2{position:absolute;top:-.95rem;left:1rem;margin:0;padding:.25rem .95rem;background:var(--cr-tape);color:var(--cr-tape-ink);font-family:var(--cr-font-accent);font-size:var(--cr-text-sm);font-weight:700;letter-spacing:.12em;text-transform:uppercase;line-height:1.3;transform:rotate(var(--cr-rotate-1));box-shadow:1px 1px 0 var(--cr-border-strong)} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list{list-style:none;padding:0;margin:0} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li{counter-increment:cr-takeaway;position:relative;margin:0;padding:.75rem 0 .75rem 2.6rem;border-top:1px dashed var(--cr-paper-rule);font-size:1rem;line-height:1.5} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child{border-top:0;padding-top:.2rem} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li::before{content:counter(cr-takeaway,decimal-leading-zero)!important;display:block!important;position:absolute!important;left:0!important;top:.95rem!important;transform:none!important;font-family:var(--cr-font-mono);font-size:var(--cr-text-xs);font-weight:700;letter-spacing:.05em;color:var(--cr-ink-muted);background:none!important;width:auto!important;height:auto!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child::before{top:.4rem!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list strong{font-family:var(--cr-font-accent);font-weight:700;box-shadow:var(--cr-shadow-marker);-webkit-box-decoration-break:clone;box-decoration-break:clone;padding:0 .1em}

🗣️ What I was told as a Training Team rep

I’ve been a WordPress Training Team rep more than once. I served in 2015, then again from 2019 to 2022. In 2019 and 2020, I was told that the aim was an Automattic employee in the rep role on every team, or on as many teams as possible. I won’t name who said it, because it was a private conversation.

And I watched it happen, or start to. I saw it in rep chats across many teams, and closest in Training, Community, Marketing and Docs. Automattic staff joined team after team. My own team was struggling then, and I was one of its reps. The Training Team wasn’t functioning.

As I saw it, the aim ended with Automattic’s January 2025 cut to its pledged hours, which I cover below. That’s my reading, not a statement anyone made, and my table shows Automattic’s seats already falling in 2024. In 2018, it held rep seats on 4 of 11 teams, in 2019 on 3 of 12, and in 2020 on 6 of 13.11 An aim is a claim about intent, so it stays my account. I didn’t ask Automattic about this aim.

🧮 How I counted WordPress team reps

In this open source project, the team rep is the elected leadership role that speaks for a team. The project calls it “a leadership role that is mostly administrative in nature; it is not a Lead role.”12 Anyone active on a team can stand, and elections happen every year.13 In 2026, 20 teams had reps.14

On November 15, 2026, I counted rep seats by employer, from 2018 to 2026.15 A seat is one person on one team in one year, so a handover adds a seat. That rewards turnover, so a long serving rep counts less than two short ones. Rep posts on the Make WordPress blogs, the project’s team news sites, name the reps. Archived WordPress.org profiles then show who sponsored their hours, and public LinkedIn histories fill some gaps. The count names no reps and uses no private channel. (The full table lives on the Merge Conflicts data page, and the methods page explains the labels.) Board seats are the level above, and my count of what sponsorship buys on foundation boards covers them. I also read the leadership rules of nine other open source projects and standards bodies, chosen like the rest of my series. I didn’t interview anyone.

📊 One tall column in WordPress team leadership

YearRep seatsAutomatticNo employer on fileTeams with repsTeams with an Automattic rep
2018286 (21%)3114
2019213 (14%)3123
2020398 (21%)4136
2021346 (18%)1135
2022437 (16%)1145
20233810 (26%)1148
2024478 (17%)0156
2025537 (13%)1165
2026476 (13%)3205
WordPress team rep seats by employer, 2018 to 2026, as of 2026-11-15. A seat is one person on one team in one year. Seat counts are floors, and shares can move either way.

Counting by employer, Automattic held 3 to 10 placed seats a year.16 However, no other employer held more than 3 in any year, and that includes GoDaddy and Pantheon.17 Unplaced seats set the limits. In 2018 and 2026, they could at most produce a tie, and in 2019 they could flip the lead.18 My published count doesn’t give the runner-up’s number for those years, so I can’t rule out a tie. (Pantheon employees have held rep seats on the Photos and Hosting teams.19)

🌐 The rest of WordPress team leadership is wide

The rest is wide. In 2025, for example, 46 seats went to someone other than Automattic. Of those, 43 went to other employers, 2 to self sponsored reps and 1 has no employer on file. Since no employer held more than 3, that’s at least 15 different employers.20 So rep seats, one layer of leadership in this open source project, are spread out, with one tall column in the middle.

🕰️ The team rep seats nobody can place

What surprised me most was how thin the early record is. From 2012 to 2017, it holds 35 rep seats, and 8 of them still have no employer on file.21 Automattic held 2 of 13 seats in 2012, and in 2013 DreamHost, a web host, led with 2 of 10.22 Then, from 2014 to 2017, the record holds only a handful of seats a year.23

Indeed, with numbers that small, one seat moves a share by about 8 points or more. Because of that, my table starts in 2018, when the rep posts get regular. For those 8 seats, I found no public page that names the employer. (I’d rather show a shorter series than a share built on guesses.)

🧢 Contributors aren’t reps

Two counts sit side by side here, and they’re easy to mix up. As of November 20, 2026, Automattic’s Five for the Future page reads 93 contributors and 2,138 hours a week across 22 teams.24 However, in 2026, it holds 6 of 47 rep seats, on 5 of 20 teams.25 So being on a team isn’t representing it.

Previously, Automattic’s pledge page listed 36 profiles in December 2019 and 112 by July 2022.26 In November 2021, a Marketing Team post relayed a wish, credited to “Josepha,” for “two to three Team Reps in each Contributor Team,” with “a mix of company sponsored and self sponsored folks.”27 Josepha Haden was named the project’s executive director in 2019.28 That wish doesn’t rule out the aim I was told about, and it doesn’t state it either.

In January 2025, Automattic cited “an imbalance in how contributions to WordPress are distributed” and the cost of WP Engine’s lawsuits. It said it would match pledges “made by WP Engine and other players,” and it cut its own to “about 45 hours a week.”29 It announced a return that May, to “return fully to the WordPress project.”30

What I still can’t answer is whether anyone wrote the aim down. I found no public message stating it, after 180 searches of public team chat channels. Unknown isn’t the same as absent, so if you know of one, send me the source.

🧱 Which bodies cap one employer

Here’s my take. A cap on seats per employer is fair because it binds any company that grows large. That makes it neutral. It’s worth having if one payroll holding many seats is a risk. The rest of this post makes that case.

Three of the ten open source projects and standards bodies I read cap one employer on a leadership body. Node.js is a tool for running JavaScript on servers. Its TSC charter caps one employer at a fourth of the Technical Steering Committee’s voting members, to ensure “adequate representation.”31 OpenJS sets the same fourth for its Cross Project Council (CPC), the body that speaks for its projects.32 W3C allows one elected seat per affiliation on its Technical Architecture Group (TAG) and its Advisory Board (AB).33

🏛️ Caps on boards, not team leads

Two more also limit employers, but only on their boards. The bylaws of the MariaDB Foundation, which backs the MariaDB database, stop an election from pushing any one sponsor above 25 percent of directors.34 Likewise, TYPO3, another open source content management system, allows one person per company on its board.35 None of these caps names a company, which is what makes them neutral. In WordPress, no other employer ever held more than 3 rep seats, at most about 14 percent of any year’s total.36

Finally, at the far end sits MySQL, the database Oracle owns. There, committers, the people allowed to merge code, and project leads are, at first, “nominated by Oracle.”37 So of the other seven, MariaDB and TYPO3 cap boards only, and Oracle nominates MySQL’s first leaders. I found no limit at WordPress, PHP, Drupal or Joomla, another open source content management system, whose bylaws set none for its department coordinators, the team leads.38

🔁 What happens when a leader changes jobs

A cap on open source leadership matters most on the day someone switches employers, because that’s when it acts. Node.js fixes an overflow “by the removal of voting member status” from members tied to the larger employer.39 OpenJS fixes it “by the resignation or removal of one or more voting CPC members.”40 On W3C’s TAG, the organization “must have returned to having at most one seat” by the next election. On its Advisory Board, “one participant must cease AB participation until the situation has been resolved.”41 Each rule moves a vote or a seat, and that’s the cost a neutral rule asks for.

Would a cap on leadership have bitten in WordPress, an open source project with many teams? Those caps each cover one body, while WordPress reps sit on many teams. On placed seats, a one fourth limit across all rep seats crossed only in 2023, at 10 of 38. Then again, if every unplaced seat were Automattic’s, 2018 to 2020 would cross too.42 Applied team by team, a one fourth cap couldn’t work on a team with fewer than four reps, since any one rep is already more than a fourth.

⚖️ The best case against a cap

The best case against a cap starts with what a rep is. The project says being a rep “doesn’t impart unilateral decision-making authority for the WordPress project.”43 So a rep count may overstate any employer’s share of open source leadership. Then there’s who does the work. The PHP Foundation says its developers “authored roughly 42% of all commits to PHP’s core” in 2025.44 Similarly, at MariaDB, 9 of the 10 stewards and maintainers list MariaDB plc, the company, as an affiliation.45 So cap that employer, and you may cap the people who know the code best. In WordPress, defenders could add that Automattic pledges 2,138 hours a week across 22 teams, so 13 to 26 percent of rep seats tracks the work.46 On a small open source team, a cap could also keep a willing volunteer out of a rep seat because of where they work.

Those are real costs. Still, pledged hours aren’t votes. Reps run the meetings and carry the team’s voice. That’s the seat a cap covers, and the caps above don’t remove anyone’s work. Instead, they move a vote or a seat. The PHP Foundation itself warns that “a 1-line commit and a 100-line commit are counted equally,” so a commit share isn’t a clean measure of who carries a project.47

🎯 Why a cap matters for team leadership

When one employer supplies many reps, one decision can land on many teams at once. The 2025 cut barely moved reps: 8 seats became 7.48 The risk, then, is what a larger share would have exposed. A cap limits how much of an open source project’s leadership one payroll holds when a cut comes.

🙋 Frequently asked questions

What happens on W3C’s Advisory Board if a job change isn’t resolved?

After 30 days, “the Chair will apply the verifiable random selection procedure” to pick who keeps a seat.49

Does TYPO3 limit companies on its teams?

I found no limit for team leads. Members voted in October 2026 on rules that regroup teams into Units.50

Who counts as tied to a sponsor under MariaDB’s 25 percent rule?

A director who is employed by the sponsor, or who holds a shareholder interest of more than 1 percent in it.51

Every relationship I disclose here
  • Automattic and WP Engine: Pantheon competes with WP Engine and with WordPress VIP, Automattic’s enterprise service.
  • Pantheon: my employer, a WordPress and Drupal host, a WP Engine competitor and a platinum Drupal Certified Partner. Its employees have held rep seats on the Photos and Hosting teams.
  • GoDaddy: my employer until July 2026. I started and ran its Five for the Future program, which pledges staff time to WordPress. It sponsored my Training rep hours in 2022.
  • GoDaddy funding: separately, I chose which groups GoDaddy funded: the PHP Foundation, OpenJS, W3C, PHP_CodeSniffer and The WPOCC.
  • FAIR Package Manager: an active member of its Technical Steering Committee.
  • The WPOCC: a co-founding board member.
  • Training Team: former rep. My own seats are in the count.

Count your own project’s reps by employer. What share would worry you, and would any written rule notice?

Footnotes (51)
  1. Automattic. “About.” automattic.com. https://automattic.com/about/. Accessed 2026-11-20. ↩︎
  2. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  3. Drupal Association. “Drupal Certified Partners.” Drupal.org. https://new.drupal.org/drupal-services. Accessed 2026-11-15. ↩︎
  4. WordPress.org. “Courtney Robertson (courane01).” WordPress.org profile, archived 2022. Internet Archive. https://web.archive.org/web/2022/https://profiles.wordpress.org/courane01/. Accessed 2026-11-15. ↩︎
  5. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  6. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  7. Node.js. “TSC Charter.” GitHub. https://github.com/nodejs/TSC/blob/main/TSC-Charter.md. Accessed 2026-11-15. ↩︎
  8. OpenJS Foundation. “CPC Charter.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md. Accessed 2026-11-15. ↩︎
  9. W3C. “W3C Process Document,” TAG and Advisory Board participation constraints. W3C. https://www.w3.org/policies/process/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  10. WordPress. “Team Reps.” Make WordPress Updates. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-20. ↩︎
  11. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  12. WordPress. “Team Reps.” Make WordPress Updates. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-20. ↩︎
  13. Make WordPress Core. “Project Organization.” Core Contributor Handbook. https://make.wordpress.org/core/handbook/about/organization/. Accessed 2026-11-15. ↩︎
  14. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  15. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  16. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  17. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  18. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  19. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  20. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  21. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  22. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  23. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  24. WordPress.org. “Automattic.” Five for the Future. https://wordpress.org/five-for-the-future/pledge/automattic/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  25. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  26. WordPress.org. “Automattic.” Five for the Future, archived captures of 2019-12-19, 2022-07-01, 2023-07-14, 2024-11-17, 2025-02-12, 2025-07-09 and 2025-12-08 (replace the date in the address to open each). Internet Archive. https://web.archive.org/web/20191219/https://wordpress.org/five-for-the-future/pledge/automattic/. Accessed 2026-11-15. ↩︎
  27. Make WordPress Marketing. “2022 team nominations for marketing.” WordPress.org. 2021-11-22. https://make.wordpress.org/marketing/2021/11/22/2022-team-nominations-for-marketing/. Accessed 2026-11-15. ↩︎
  28. Matt Mullenweg. “Expanding WordPress Leadership.” Make WordPress Updates. 2019-01-16. https://make.wordpress.org/updates/2019/01/16/expanding-wordpress-leadership/. Accessed 2026-11-20. ↩︎
  29. Automattic. “Aligning Automattic’s Sponsored Contributions to WordPress.” Automattic. 2025-01-09. https://automattic.com/2025/01/09/aligning-automattics-sponsored-contributions-to-wordpress/. Accessed 2026-11-15. ↩︎
  30. Automattic. “Returning to Core.” Automattic. 2025-05-29. https://automattic.com/2025/05/29/returning-to-core/. Accessed 2026-11-15. ↩︎
  31. Node.js. “TSC Charter.” GitHub. https://github.com/nodejs/TSC/blob/main/TSC-Charter.md. Accessed 2026-11-15. ↩︎
  32. OpenJS Foundation. “CPC Charter.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md. Accessed 2026-11-15. ↩︎
  33. W3C. “W3C Process Document,” TAG and Advisory Board participation constraints. W3C. https://www.w3.org/policies/process/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  34. MariaDB Foundation. “By-laws,” section 5.02. MariaDB.org. https://mariadb.org/bylaws/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  35. TYPO3 Association. “Statuten der TYPO3 Association.” TYPO3 Policy Guide. https://docs.typo3.org/m/typo3/guide-policy/main/en-us/Association/BylawsAndProceedingsGermanOriginal.html. Accessed 2026-11-15. ↩︎
  36. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  37. Oracle. “MySQL Community Governance Model.” MySQL. https://dev.mysql.com/community/governance-model/. Accessed 2026-11-15. ↩︎
  38. Open Source Matters. “By-Laws of Open Source Matters, Inc.” Open Source Matters. 2021-12-13. https://www.opensourcematters.org/images/documents/20211213-OSM-Bylaws.pdf [PDF]. Accessed 2026-11-15. ↩︎
  39. Node.js. “TSC Charter.” GitHub. https://github.com/nodejs/TSC/blob/main/TSC-Charter.md. Accessed 2026-11-15. ↩︎
  40. OpenJS Foundation. “CPC Charter.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md. Accessed 2026-11-15. ↩︎
  41. W3C. “W3C Process Document,” TAG and Advisory Board participation constraints. W3C. https://www.w3.org/policies/process/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  42. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  43. WordPress. “Team Reps.” Make WordPress Updates. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-20. ↩︎
  44. The PHP Foundation. “The PHP Foundation Impact and Transparency Report 2025.” The PHP Foundation. 2026-05-27. https://thephp.foundation/blog/2026/05/27/impact-and-transparency-report-2025/. Accessed 2026-11-15. ↩︎
  45. MariaDB. “Maintainers.” MariaDB governance repository, GitHub. https://github.com/MariaDB/governance/blob/main/lists/maintainers.md. Accessed 2026-11-15. ↩︎
  46. WordPress.org. “Automattic.” Five for the Future. https://wordpress.org/five-for-the-future/pledge/automattic/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  47. The PHP Foundation. “The PHP Foundation Impact and Transparency Report 2025.” The PHP Foundation. 2026-05-27. https://thephp.foundation/blog/2026/05/27/impact-and-transparency-report-2025/. Accessed 2026-11-15. ↩︎
  48. Courtney Robertson. “WordPress team reps by employer, 2012 to 2026.” Merge Conflicts data page, courtneyr.dev. My count from public Make WordPress rep posts, archived WordPress.org profiles and public LinkedIn histories, as of 2026-11-15. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
  49. W3C. “W3C Process Document,” TAG and Advisory Board participation constraints. W3C. https://www.w3.org/policies/process/. Accessed 2026-11-15 and 2026-11-20. ↩︎
  50. Stefan Busemann, TYPO3 Association. “TYPO3 Association Members to Vote on New Governance Structure.” TYPO3 News. 2026-10-15. https://news.typo3.com/article/typo3-association-members-to-vote-on-new-governance-structure. Accessed 2026-11-15. ↩︎
  51. MariaDB Foundation. “By-laws,” section 5.02. MariaDB.org. https://mariadb.org/bylaws/. Accessed 2026-11-15 and 2026-11-20. ↩︎

Did you enjoy this article?

Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.

Across the AtmosphereDiscussions