Skip to content

Why pay for free software? Who decides the open source stack under WordPress?

Picking a host picks four of the six open source layers under WordPress. Each has its own rule for who approves a change, and sponsor money buys different things at each.

Courtney
Nov 10, 202613 min read

icking a host picks four of the six layers in the open source stack under a WordPress site: Linux, the web server, the database and the PHP versions on offer. Each layer has its own rule for who approves a change. Paying those projects buys developers’ time, and sometimes a board seat or vote. In the pages I read, it bought no path to a code decision.

Disclosure: I work at Pantheon, a WordPress host. At GoDaddy, I chose four of the sponsorships this post weighs. My other ties follow in the first section.

Key takeaways

  • The big picture: A WordPress site runs on separate projects, from Linux to the browser, and each one decides changes its own way.
  • By the numbers: A PHP language change needs two thirds of the votes cast. At Linux, one person, Linus Torvalds, merges into the main kernel.12
  • Why it matters: Your host decides which PHP versions you can pick, so it shapes the open source software in your stack before you log in.3
  • Yes, but: Sponsorship buys a board seat at the PHP Foundation and a board vote at OpenJS, though the rules I read give it no say over code.
/* 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}

🏠 Why I read the rules under my own WordPress stack

If you’ve opened Tools > Site Health > Info in WordPress, you’ve seen most of your stack: WordPress, the server and the database.4 (When I checked mine, it took less time than finding the coffee.)

For years, this stack of open source software was part of my job, not background noise. Over time, the question I heard most from budget approvers was short. Why pay for software anyone can download for free?

So in November 2026, I read each layer’s own governance page. I started from what WordPress’s requirements page recommends: PHP 8.3 or greater, a database (MariaDB 10.11 or MySQL 8.4 or greater) and a web server (Apache or Nginx).5 Then I added the browser your visitors use and the build tools you never ship. The projects come from Merge Conflicts, my series on who decides in open source. My post on how I picked them explains why.

🤝 My ties to this topic

My ties sit close to this one. 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. So this post touches my employer’s business. 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.

Four of those sponsorships appear below, so part of this post weighs my own choices. 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.

Here’s my take. Your host sets the menu. The rules I read give sponsors no code vote.

🧱 The stack under one WordPress page

Every page load passes through six open source layers in one stack, with build tools beside it. (The illustration below has a text description you can open.)

Every page load passes through six shelves someone else stocks. Illustration made with ChatGPT at my direction.
Text description of the illustration
  • A tall wooden pantry unit has six shelves. From the bottom up, their tape labels read LINUX, WEB SERVER, DATABASE, PHP, WORDPRESS and BROWSER.
  • Each shelf holds a few unlabeled jars and boxes, so the shelves look alike from a distance.
  • On the floor beside the unit, a closed toolbox carries one label: BUILD TOOLS. It sits outside the shelves, the way build tools sit outside the page load.
  • At the left, the developer sits in a manual wheelchair with a laptop on their lap and looks up at the bottom shelf.
  • At the right, the pantry coordinator holds a clipboard and points at the WORDPRESS shelf, near the top.
  • In other words, WordPress is one shelf among six, and every shelf has its own rule for who restocks it.

🐧 Linux and the web server

Linux, the open source kernel at the bottom of the stack, runs the server. Subsystem maintainers accept patches, which are proposed code changes, and pull from each other in what the kernel docs call a “chain of trust.” But only one person, Linus Torvalds, can merge patches into the main kernel repository. He chose only about 1.3 percent of the 2.6.38 kernel’s patches directly, an old figure that shows the design, not today’s count.6

Next, the web server takes each request and hands it to PHP. Both common servers review changes by committee, so start with what they share. At the Apache HTTP Server, a Project Management Committee governs, and its voting rules say, “No veto can be overruled.”78 Apache’s maintainers sign a contributor license agreement, a contract that grants the project rights to their code, with the nonprofit Apache Software Foundation. So does anyone making a large contribution.9

What surprised me most was that NGINX sends every contribution through F5’s Contributor License Agreement. No change enters “an F5 Open Source repository” until its author has agreed to it.10 F5, Inc. is the company named in the copyright notice on NGINX’s governance page. That page says “the technical committee for that project” reviews contributions, but not who sits on it.11 So both servers review by committee, but Apache’s agreement runs to a nonprofit and NGINX’s to a company. That matters, because a contributor agreement can move the power to relicense.

🗄️ The database and PHP

Then comes the database, the software stack’s memory, which stores your posts and settings. Oracle’s MySQL governance page says “Oracle is the project lead for MySQL community edition,” and its first committers are people Oracle nominates. A steering committee reviews changes to those rules, and it can “request revisions.”12

MariaDB splits the job differently. Its Foundation board “does not make technical decisions.”13 But a 2025 agreement says MariaDB plc, the company that sells MariaDB, “employs the developers who contribute more than 90% of the code of MariaDB Server.”14 Neither page I read says who approves a MariaDB change.

PHP runs every line of WordPress’s PHP code. Language changes go through requests for comments (RFCs). Each primary vote “requires a 2/3 majority.” Voters are people with php.net accounts who’ve contributed code, plus representatives they choose.15

I pointed budget approvers at PHP first. Fixing the language fixes it for every plugin, theme and site at once, which no single plugin budget can do. That fix still reaches a site only when its host offers the new version.16

📝 WordPress, the browser and the build tools

WordPress is the layer of the stack your client logs in to. Its Core Handbook says the project is “led by co-founder and lead developer Matt Mullenweg,” and lead developers hold “final authority on technical decisions.”17 Release squads, the teams that ship each version, form by open nomination. Then the WordPress project’s Executive Director or a designee confirms them.18

Your visitors’ browsers, the top layer, decide differently again. Chromium, the open source project behind Google Chrome, needs “a positive review from an owner of each directory your change touches,”19 while Firefox requires “a module owner’s OK.”20 At WebKit, the engine behind Safari, existing reviewers pick new committers and reviewers.21 And at W3C, the World Wide Web Consortium, Working Groups write the standards, while a W3C Council hears formal objections.22

Build tools sit outside the page load, but every site you build passes through them. WordPress’s docs call Node.js, a program that runs JavaScript outside the browser, “essential” for block editor work.23 The OpenJS Foundation, a nonprofit for JavaScript projects, hosts Node.js. The WordPress Coding Standards are “a collection of PHP_CodeSniffer rules,” and PHP_CodeSniffer is the tool that checks code against them.24 Since the original package was abandoned, it lives at PHPCSStandards, its “official continuation.”25

💸 What paying for free software buys

So, why pay for free? Funding reaches each of the open source layers differently. At PHP, money pays people. The PHP Foundation’s “primary task” is “to fund developers to work on PHP.” Language decisions, it says, “remain the matter of the PHP Internals community,” which votes on RFCs.26

Money also buys different access at each foundation. The PHP Foundation lists GoDaddy.com as a Gold sponsor.27 Its governance page gives up to three board seats “automatically” to qualified Platinum sponsors. Other sponsors can hold up to four more. Each director is “nominated by an existing Board member” and voted on yearly by the board and the Executive Director.28 OpenJS lists GoDaddy as a Silver member, so GoDaddy takes part when “Gold and Silver members vote among themselves to select their representatives” on its board.2930 PHP_CodeSniffer’s Open Collective page, a public donation page, lists “GoDaddy.com” as a corporate funder.31

W3C’s Diversity page names GoDaddy among the TPAC 2025 sponsors who “financially helped 26 of our attendees.”32 TPAC is W3C’s annual meeting. The fund aims to help underrepresented people “who are unable to attend TPAC” without it. To me, standards are only as good as who’s in the room.

⚖️ Does paying people shape the open source stack?

The best case against me is that paying people shapes code. MariaDB plc employs the developers behind over 90% of MariaDB Server’s code.33 Whoever pays for patches decides which ones get written. A vote isn’t the only lever. Still, that’s employment, not sponsorship. And where the rules I read name who approves a change, approval runs through reviewers and leads, not sponsors.

So sponsorship can buy a board seat at the PHP Foundation and a board vote at OpenJS. The governance pages I read across this open source stack give sponsors no path to a code decision. But they wouldn’t show informal influence. I didn’t look for it.

⚖️ You choose more of the WordPress stack than the host does

The best case against my claim is that you choose more of the open source in your stack than the host does. WordPress’s own page on PHP updates says “many hosters let you change this yourself.”34 WordPress’s requirements are recommendations, not hard minimums.35 Your visitors pick their browsers, and you pick your build tools. And if you rent a bare server and run it yourself, you pick every layer. Hiding the open source stack is also the point of a managed host, because it lets you work on the site instead of the server.

Still, the same page says your hosting company “determines which versions of PHP are available for your site.”36 So you choose from the host’s menu. And whichever version you pick, PHP’s RFC voters decided what’s in it. The host picks the menu for your stack, and each open source project’s own rules decide what’s on it.

❔ What I still can’t answer about the open source stack

What I still can’t answer is who approves a PHP_CodeSniffer release. Its README names no maintainers. Its contributing guide says failing pull requests “will likely be ignored by the maintainers or closed,” without naming them either.3738 If you know where that rule is written, please send me the page. I’ll add it.

🙋 Frequently asked questions

Does WordPress still run on older PHP and MySQL?

Yes, for now. The requirements page says it “also works with PHP 7.4+ and MySQL 5.5.5+,” but warns those versions have reached their official end of life.39

Do small Apache contributions need a contributor agreement?

No. The Apache Software Foundation says small contributions are made under clause 5 of the Apache 2.0 license itself.40

Who sits on MySQL’s steering committee?

At first, “a small group of 5-7 individuals,” with Oracle holding the majority.41 So open Site Health again and look at the open source layers in your stack. Which would you pay for first, and what would you expect back?

Footnotes (41)
  1. PHP. “Request for Comments: Voting on PHP features.” PHP RFC wiki. https://wiki.php.net/rfc/voting. Accessed 2026-11-09. ↩︎
  2. The Linux kernel development community. “2. How the development process works.” A guide to the kernel development process, The Linux Kernel documentation. https://docs.kernel.org/process/2.Process.html. Accessed 2026-11-09. ↩︎
  3. WordPress.org. “Get a faster, more secure website: update PHP today.” WordPress.org Support. https://wordpress.org/support/update-php/. Accessed 2026-11-20. ↩︎
  4. WordPress. “Site Health Screen.” WordPress.org Documentation. https://wordpress.org/documentation/article/site-health-screen/. Accessed 2026-11-09. ↩︎
  5. WordPress. “Requirements.” wordpress.org. https://wordpress.org/about/requirements/. Accessed 2026-11-09; reread 2026-11-20. ↩︎
  6. The Linux kernel development community. “2. How the development process works.” A guide to the kernel development process, The Linux Kernel documentation. https://docs.kernel.org/process/2.Process.html. Accessed 2026-11-09. ↩︎
  7. The Apache Software Foundation. “How the ASF works.” apache.org. https://www.apache.org/foundation/how-it-works/. Accessed 2026-11-09. ↩︎
  8. Apache HTTP Server Project. “Apache HTTP Server Project Guidelines and Voting Rules.” httpd.apache.org. https://httpd.apache.org/dev/guidelines.html. Accessed 2026-11-09. ↩︎
  9. The Apache Software Foundation. “ASF Contributor Agreements.” apache.org. https://www.apache.org/licenses/contributor-agreements.html. Accessed 2026-11-20. ↩︎
  10. NGINX. “CONTRIBUTING.md.” nginx/nginx repository, GitHub. https://github.com/nginx/nginx/blob/master/CONTRIBUTING.md. Accessed 2026-11-09. ↩︎
  11. NGINX. “NGINX Open Source Governance.” nginx.org. https://nginx.org/en/docs/governance.html. Accessed 2026-11-09. ↩︎
  12. Oracle. “MySQL Community Governance Model.” dev.mysql.com. https://dev.mysql.com/community/governance-model/. Accessed 2026-11-09; reread 2026-11-20. Sections 3.5, 14 and 15. ↩︎
  13. MariaDB Foundation. “About MariaDB Foundation.” mariadb.org. https://mariadb.org/about/. Accessed 2026-11-09. ↩︎
  14. MariaDB Foundation. “Board Meeting 2/2025,” minutes with Memorandum of Understanding (Attachment A). mariadb.org. 2025-03-12. https://mariadb.org/bodminutes/2025-03-12/. Accessed 2026-11-09. ↩︎
  15. PHP. “Request for Comments: Voting on PHP features.” PHP RFC wiki. https://wiki.php.net/rfc/voting. Accessed 2026-11-09. ↩︎
  16. WordPress.org. “Get a faster, more secure website: update PHP today.” WordPress.org Support. https://wordpress.org/support/update-php/. Accessed 2026-11-20. ↩︎
  17. WordPress. “Project Organization.” Core Handbook, Make WordPress Core. Last updated 2026-09-07. https://make.wordpress.org/core/handbook/about/organization/. Accessed 2026-11-09. ↩︎
  18. WordPress. “WordPress Release Team and Focus Leads.” Core Handbook, Make WordPress Core. https://make.wordpress.org/core/handbook/about/how-the-release-cycle-works/wordpress-release-team-and-focus-leads/. Accessed 2026-11-09. ↩︎
  19. The Chromium Authors. “Code Reviews.” chromium/src docs. https://chromium.googlesource.com/chromium/src/+/HEAD/docs/code_reviews.md. Accessed 2026-11-09. ↩︎
  20. Mozilla. “Module Ownership System.” mozilla.org. https://www.mozilla.org/en-US/about/governance/policies/module-ownership/. Accessed 2026-11-09. ↩︎
  21. WebKit. “Commit and Review Policy.” webkit.org. https://webkit.org/commit-and-review-policy/. Accessed 2026-11-09. ↩︎
  22. World Wide Web Consortium. “W3C Process Document,” sections 1, 2.1 and 3.3. 18 August 2025. https://www.w3.org/policies/process/. Accessed 2026-11-09. ↩︎
  23. WordPress. “Block Editor Handbook: Development environment.” Developer.WordPress.org. https://developer.wordpress.org/block-editor/getting-started/devenv/. Accessed 2026-11-09. ↩︎
  24. WordPress. “WordPress Coding Standards for PHP_CodeSniffer,” README. GitHub. https://github.com/WordPress/WordPress-Coding-Standards. Accessed 2026-11-09. ↩︎
  25. PHPCSStandards. “PHP_CodeSniffer,” README. GitHub. https://github.com/PHPCSStandards/PHP_CodeSniffer. Accessed 2026-11-09. ↩︎
  26. The PHP Foundation. “The PHP Foundation” (Foundation Activities). thephp.foundation. https://thephp.foundation/foundation. Accessed 2026-11-20. ↩︎
  27. The PHP Foundation. Home page, sponsor lists. thephp.foundation. https://thephp.foundation/. Accessed 2026-11-09. ↩︎
  28. The PHP Foundation. “Governance of the PHP Foundation,” sections 3.3.2 and 3.4. thephp.foundation. https://thephp.foundation/governance/. Accessed 2026-11-09; reread 2026-11-20. ↩︎
  29. OpenJS Foundation. “Members.” openjsf.org. https://openjsf.org/members. Accessed 2026-11-09. ↩︎
  30. OpenJS Foundation. “Meet Our 2026 OpenJS Foundation Board of Directors.” openjsf.org. https://openjsf.org/blog/meet-our-2026-openjs-foundation-board-of-directors. Accessed 2026-11-09. ↩︎
  31. Open Collective. “PHP_CodeSniffer.” opencollective.com. https://opencollective.com/php_codesniffer. Accessed 2026-11-09. ↩︎
  32. World Wide Web Consortium. “Diversity.” w3.org. https://www.w3.org/about/diversity/. Accessed 2026-11-09; reread 2026-11-20. ↩︎
  33. MariaDB Foundation. “Board Meeting 2/2025,” minutes with Memorandum of Understanding (Attachment A). mariadb.org. 2025-03-12. https://mariadb.org/bodminutes/2025-03-12/. Accessed 2026-11-09. ↩︎
  34. WordPress.org. “Get a faster, more secure website: update PHP today.” WordPress.org Support. https://wordpress.org/support/update-php/. Accessed 2026-11-20. ↩︎
  35. WordPress. “Requirements.” wordpress.org. https://wordpress.org/about/requirements/. Accessed 2026-11-09; reread 2026-11-20. ↩︎
  36. WordPress.org. “Get a faster, more secure website: update PHP today.” WordPress.org Support. https://wordpress.org/support/update-php/. Accessed 2026-11-20. ↩︎
  37. PHPCSStandards. “PHP_CodeSniffer,” README. GitHub. https://github.com/PHPCSStandards/PHP_CodeSniffer. Accessed 2026-11-09. ↩︎
  38. PHPCSStandards. “CONTRIBUTING.md.” PHP_CodeSniffer repository, GitHub, 4.x branch. https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/4.x/.github/CONTRIBUTING.md. Accessed 2026-11-09. ↩︎
  39. WordPress. “Requirements.” wordpress.org. https://wordpress.org/about/requirements/. Accessed 2026-11-09; reread 2026-11-20. ↩︎
  40. The Apache Software Foundation. “ASF Contributor Agreements.” apache.org. https://www.apache.org/licenses/contributor-agreements.html. Accessed 2026-11-20. ↩︎
  41. Oracle. “MySQL Community Governance Model.” dev.mysql.com. https://dev.mysql.com/community/governance-model/. Accessed 2026-11-09; reread 2026-11-20. Sections 3.5, 14 and 15. ↩︎

Did you enjoy this article?

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

Across the AtmosphereDiscussions