---
title: "Merge Conflicts data: the counts, rosters and tables behind the series"
date: 2026-11-20
author: "Courtney Robertson"
---

# Merge Conflicts data: the counts, rosters and tables behind the series

*By Courtney Robertson. Last updated November 20, 2026.*

This page holds the open source governance data behind Merge Conflicts, my series on who decides in open source. Each post now argues one point. The counts, rosters, comparison tables and evidence labels behind those points live here instead.

No count here is new. Every table, list and label comes from one of the 16 published posts, copied as that post printed it. Sections follow the series order, and each one opens with a link to its post and that post’s date. Tables keep their captions, read dates and footnotes. Each count keeps the post’s own words on what it measures, such as seats listed, members eligible or votes cast. Where a post printed a table without a caption or footnotes, it stays that way here.

Disclosures travel with the posts. I work at Pantheon, a WordPress and Drupal host. At GoDaddy, I started and ran its Five for the Future program until July 2026. I’m an active member of the FAIR Package Manager’s Technical Steering Committee. Each post lists every relationship in full.

Found a wrong number? Reply from your own site or in a post’s public discussion thread, or use the contact form. The last section explains what happens next.

## 🗺️ Governance procedures: which projects the series compares

This roster backs [the opening post on governance procedures nobody wrote down](https://courtneyr.dev/2026/11/02/open-source-governance-procedures/), published November 2, 2026.

**Season 2 asks 12 projects the same questions about their open source governance procedures.** In alphabetical order: Backdrop, the CSS and HTML standards bodies, Drupal, Ghost, Joomla, MariaDB, MySQL, Node.js, OpenJS, PHP, TYPO3 and WordPress. Three supplemental cases sit beside them: xz-utils, ClassicPress, and Ruby Central with RubyGems.[1](#9b53ea48-d620-4c04-8281-19bb5fb4d563) WordPress is one row in every table, sorted like the others, with no special color.

**Season 3 reads WordPress’s record through dated documents**, the way the room section did: a recap, a post, a capture, each dated.

**Seasons 4 to 8 turn to how projects work, grow, license, fund and measure themselves.**[2](#1ca85d81-3b6e-45cf-ac0b-60ca224a1fb0)

What the series doesn’t compare: Python, Apache and Kubernetes were in an older plan and stay out until someone researches them from primary documents.[3](#28cddfde-6792-4f7d-87ed-0ba633c34592) If you came for Kubernetes governance, I’m sorry. The research didn’t go there.

## 🧭 Four freedoms: the dates, the product questions and four forks

These dates and tables back [the post on the four freedoms and where WordPress uses them](https://courtneyr.dev/2026/11/03/four-freedoms-of-open-source/), published November 3, 2026.

### Ideas, licenses and projects: the dates behind the freedoms

The institutions and licenses behind the four freedoms of open source followed soon after, and then the projects that became WordPress:

- **October 4, 1985:** the Free Software Foundation incorporated.[4](#11a93f9a-a8bd-4fe4-9219-b08b1daa6bf0)
- **1986:** its first bulletin carried an early definition of free software, by the FSF’s own history page.[5](#5e04218c-322f-4d14-8dbf-c049296c87cc)
- **February 1989:** the GNU General Public License, version 1.[6](#7d778302-acc2-42d8-a4ce-1ed13866f0f1)
- **June 1991:** version 2.[7](#2ec2d08c-91df-4f70-b85d-f1bc34a3eef7) WordPress still ships under version 2 or later.[8](#ed128f1d-fddd-416d-9b1c-366ebc183422)
- **June 2001:** b2 began. That August its author wrote that “b2 isn’t released under the GPL yet.”[9](#ebb72b4a-9a4f-451f-aff7-9f8c51ebb94d)
- **November 2002:** a b2 readme dated that month says it was.[10](#0423aa1d-fa45-406d-bb05-dd3c81928b25)
- **May 27, 2003:** WordPress’s first release.[11](#bb746a3f-8f2a-40a8-882d-ad3357f75d4f)

“Open source” is younger still:

- It dates to a strategy session on February 3, 1998 in Palo Alto, “shortly after the announcement of the release of the Netscape source code.”[12](#d8eca607-c25b-416e-892d-d8579a6a8d7d)
- The [Open Source Initiative](https://opensource.org/history) formed that month.[13](#2bc0cb95-8cc5-490d-b84d-efe107e19da6)
- The OSI’s definition likewise lists ten criteria and opens with a warning: “Open source doesn’t just mean access to the source code.”[14](#e1c8a62b-f203-4e5f-9d41-0071ab933b4e)

### Do SaaS, proprietary software and AI built tools give you the four freedoms?

QuestionWhat to askWho answers itHow was it made?Written by hand, with AI help, or both? How was it reviewed?The maker’s process. The four freedoms don’t askHow is it delivered?A copy I run, or access to someone else’s service?The delivery modelWhat permissions do I hold?May I run, study, change and redistribute it? Where does it say so?The license. This is the four freedoms’ questionWho controls the project around it?Who changes the rules, runs the update server, hears complaints?Governance, which the rest of this series coversFour questions to ask about one product, and which one the four freedoms answer### How four forks used freedom 3

Parent projectForkWhat the fork keptWhat stayed behindLabel and claimb2/cafelogWordPress, 2003The code, as “the official successor of b2/cafelog”The b2 nameverified; WordPress.org version history[15](#e2727d1f-e296-40ba-8815-66ea0b56f7de)DrupalBackdrop, 2013The code, as “a fork of Drupal” and “Drupal 7 — modernized”A new name and domainverified; Backdrop’s about page and its GitHub repository record, created 2013-08-22[16](#edbcb4bf-a5cd-4f45-8ed8-54385a9a8bf4)MySQLMariaDBThe GPLv2 code and the peopleThe MySQL name; the MariaDB name sits with a company, and the Foundation uses it under licenseanalysis; C-MDB-201[17](#1f49b7b6-86c0-4e88-8e1f-bff077ca518c)RubyGemsgem.coop, 2025A gem server and mirror run by former maintainersThe rubygems.org registry and its namespacesource-derived; C-SUP-080[18](#9fc6c50d-5c7b-4735-8fed-19e1a551a4e5)What four forks kept under freedom 3, and what stayed behind, with the evidence label for each row## 🍺 Free as in freedom: two definitions side by side

This table backs [the post on which free open source promises](https://courtneyr.dev/2026/11/04/free-as-in-freedom/), published November 4, 2026.

### How do free software and open source differ if the programs are the same?

QuestionFree software, per the FSFOpen source, per the OSISame programs?The terms “stand for almost the same range of programs”[19](#4de94d3b-7e4f-4dee-88b5-3783069ef71f)“two terms for the same thing”[20](#3596c1f4-d80a-4f71-9953-0043240996a7)What the term stresses“a movement for freedom and justice”[21](#a05356ca-39af-4f34-81a5-c5d3293831c9)“the superiority of an open development process”[22](#cf71da39-05e7-4b24-8749-303a89e3791e)Why this wordThink of “free” as in “free speech”[23](#a68a5ce0-2acd-4342-a8fe-10c4fc093da4)“the ambiguity of the English word ‘free'” was given as “a reason”[24](#de4eafb0-455d-4b8b-abc5-0d78a5cda397)How it describes the other“the open source idea values mainly practical advantage”[25](#2b8530c9-46d5-41a9-9dc5-974a2d861ce2)“the philosophically- and politically-focused label ‘free software'”[26](#0a993036-9c1c-4d25-adc0-5798559d3038)What it says about price“a matter of liberty, not price”[27](#e0dbfc41-a13c-4d9d-a9b7-0a57bab9aed2)“You can even sell Open Source software.”[28](#5593b92b-f7e6-40b8-9763-0ac84d35d465)Free software and open source, each described by the organization that keeps its definition## 📜 Open source history: where WordPress code and tickets live

These records back [the post on what open source history says about who decides](https://courtneyr.dev/2026/11/05/history-of-open-source/), published November 5, 2026.

### Where does WordPress sit in the history of open source?

WordPress lives in two eras at once. Here’s the record, one document at a time:

- **When it starts:** WordPress.org says the project has “come a long way since 2003.” Its release list begins with version 0.7 on May 27, 2003.[29](#99d3d524-a531-4a9b-ba9e-331c8a44d29c)
- **Where core code lives:** “The canonical WordPress repository is managed using Subversion,” the core handbook says.[30](#df172fc1-3008-4836-b605-5fba2c8ffc48) Subversion, or SVN, is another version control system.
- **What the GitHub copy is:** “This repository is just a mirror of the WordPress subversion repository,” the wordpress-develop README says.[31](#3e3cd4e2-3267-483e-bc9e-a2740844657d) The handbook adds that “pull requests submitted to GitHub will not be merged there.”[32](#0617f838-6b67-4ef7-ae84-fec8b807f747)
- **How a GitHub patch counts:** patches can be reviewed in pull requests, the handbook says, “but they must be associated with a Trac ticket.”[33](#39b0ed9e-cb69-4f84-9970-e197e392d1d7) Trac is WordPress’s ticket tracker for core.
- **Where the block editor lives:** Gutenberg, the block editor project, calls its GitHub repository “the development hub for the WordPress Gutenberg project.”[34](#236332df-579f-442e-a0b4-85e3a331ca17)

### Why are there several Trac sites?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Core Trac:** tickets and patches for WordPress itself, the route the core handbook describes above.[35](#a2757ead-d23e-4e5b-bab1-d8ef9de33f61)
- **Meta Trac:** bug reports for the WordPress.org sites. Its home page explains: “We used to manage the WordPress.org site on the same Trac as WordPress core is developed.”[36](#305ac65f-c19c-4834-8050-4cb57f5b4ed4)
- **Themes Trac:** the review queue. “A ticket is automatically created when a new theme is uploaded,” the Themes Team handbook says.[37](#7a6072ae-eea1-4194-9e76-e3986dad67ec)







## ⚖️ Licenses: the criteria, the two families and who can relicense

These tables back [the post on how open source licenses work and what they leave out](https://courtneyr.dev/2026/11/06/how-open-source-licenses-work/), published November 6, 2026.

### What makes a license count as open source?

The OSI keeps the Open Source Definition, version 1.9.[38](#7f7fdafc-46dc-4023-bc4b-71db3b2b388a) It lists ten criteria a license must meet. To get on the OSI’s list, “a license must go through the Open Source Initiative’s license review process.”[39](#322f6629-fdf5-40ef-b54a-62ace5a78062)

Five of the ten criteria do most of the work for a site builder.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

CriterionWhat the definition saysWhat it means for you1. Free Redistribution“The license shall not restrict any party from selling or giving away the software”You can share it, or sell it2. Source Code“The program must include source code”You get the readable version, not only the compiled one3. Derived Works“The license must allow modifications and derived works”Your fork is allowed5. No Discrimination Against Persons or Groups“The license must not discriminate against any person or group of persons.”Nobody gets left off the list6. No Discrimination Against Fields of Endeavor“The license must not restrict anyone from making use of the program in a specific field of endeavor.”A business can use it, and so can a lab





### What’s the difference between permissive and copyleft licenses?

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

When you share a changed copyPermissive, such as MITCopyleft, such as GPLv2Keep the copyright noticeYesYesShare your changes under the same licenseNot requiredRequiredShip a closed versionAllowedNot allowed





### Who can change an open source license?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

PHP changed its license in 2025 and 2026, through a Request for Comments (RFC). The RFC “PHP License Update” says: “The Modified BSD License is adopted as the PHP License, version 4.”[40](#de3b3e2c-19ea-4235-bc2b-455a58e11dec) The vote passed 51 to 0, with 2 abstentions.[41](#18a9d187-530d-416a-a3e4-d7c8ddb3406b)







### How do six projects compare on who can relicense?

Other projects answer the same question differently. Here are six from the series’ comparison, sorted alphabetically, with WordPress as one row. I work at Pantheon, a WordPress and Drupal host, so two of these rows touch my employer’s business.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectCode licenseContributor termsWho could relicense (analysis)DrupalGPL-2.0-or-laterContributors keep copyright; no CLA or DCO mentionedThe project lead decides distribution; a legal change needs contributor consentGhostMITCLA lets the Ghost Foundation license contributions “on any licensing terms”The Ghost Foundation, for contributed codeMySQLGPLv2 plus a commercial licenseContributor agreement assigns joint ownership to OracleOracle, for its code and its joint shareNode.jsMITDCO sign-off; no CLAAll contributors, which is impracticalPHPBSD-3-Clause, since the RFC aboveContributors certify their rights; no CLAThe PHP Group and Perforce, after a voteWordPressGPLv2 or laterNo CLA or DCO foundEvery copyright holder; no single holder found





The license and contributor columns come from each project’s own files.[42](#9e60e13a-8d02-499a-babd-bd8fef762b76) The last column is analysis.

## 🎲 WordPress /random/: the record, the rulebooks and the next task

These tables back [the post on who pays when a random redirect becomes the default](https://courtneyr.dev/2026/11/07/wordpress-random-default-costs/), published November 7, 2026.

### How did random redirects go from optional to default?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

RecordWhat it says or changes[Ticket #64498](https://core.trac.wordpress.org/ticket/64498)‘s opening proposalProposes discussing whether a minimal, opt-in core implementation should exist.Comment 12Anne McCarthy attributes core inclusion to Matt’s repeated requests.Changeset r63906Reverts the first implementation for further work.Changeset r64402Reintroduces the feature using the existing rewrite and query systems.[November 5 dev note](https://make.wordpress.org/core/2026/11/05/your-content-is-going-to-get-more-random/)Describes the feature as enabled by default.





The ticket supplies the development history; the dev note supplies the announced default.[43](#22026c0f-10cb-47b9-b1b0-42cd96d74ba6)[44](#7cc2c106-4879-4834-842d-fce89b28112f)

### What would /random/ need in the projects we compare?

Disclosure: I work at Pantheon, which hosts Drupal and WordPress sites.

Same feature, six rulebooks. Each row comes from the project’s own governance page, and WordPress is one row. PHP’s rule covers language changes, so treat it as the strict end. These six were chosen for this post. The other projects in the comparison weren’t checked.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectWhat the written rules ask forWho can stop itBackdrop CMSIts Project Management Committee approves “proposed new features for each minor release”[45](#3b8d0138-8535-4bbb-b6b7-d2aaa672d281)The committee, by consensus or a majority voteClassicPress (extra case)Anyone suggests it in GitHub issues; volunteers build it[46](#7369795a-69ef-484a-90ae-cbe7dd97e5d0)Its rule: “No single person within ClassicPress has the power to force through a valid change”DrupalProduct managers approve “a significant new feature”; someone besides the author signs off[47](#61f90e4a-b982-466a-9459-6921012bd3be)Product managers; the Project Lead breaks tiesNode.jsTwo collaborators who didn’t write it approve, or one after seven days[48](#2262e7ab-7002-4ded-a96b-91f0b574ecf1)Any collaborator: “If a collaborator opposes a proposed change, then the change cannot land.” But “The exception is if the TSC votes to approve the change despite the opposition”[49](#dea4ca9f-f0c7-46f7-9184-c28d850a39b3)PHPAn RFC (Request for Comments), two weeks of discussion, then a vote of at least two weeks[50](#f67a691d-41c6-4ab8-b57d-32c33c99c98c)Voters: Yes must be at least twice NoWordPressFeatures as Plugins and a merge proposal, as the usual route[51](#926beebc-4fd9-46c0-b70d-46409ad03e09)“The Core team”; lead developers have “final authority on technical decisions”[52](#e73d0f42-9336-437c-8251-6da67508f450)What a new feature needs before it ships, by each project’s written rules





[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

In four of the six rows, someone besides the proposer can stop a feature in writing. It might be a committee, a product manager, one collaborator or a vote. In WordPress, the written stop is the core team’s judgment. None of these rules says whether /random/ is a good idea. They decide who has to be convinced.







### Who gets the next task after the merge?

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

WhoWhat they may need to decide or maintainCore contributorsQuery and routing behavior, compatibility, documentation and regression tests.HostsCache policy, database capacity, protection rules and upgrade procedures.Plugin and theme developersEligibility rules, existing URLs, query changes and understandable controls.Site owners and agenciesWhether the feature fits, which content qualifies and who can disable it.Authors and editorsWhether older material makes sense outside its original sequence, sometimes without access to site settings.VisitorsWhether the link’s label and destination give enough context to use it.





## 📋 Projects compared: names, licenses and who decides

These tables and rosters back [the post on which open source projects the series compares, and why](https://courtneyr.dev/2026/11/09/open-source-projects-compared/), published November 9, 2026.

The research brief named 13 items. CSS and HTML share one profile, so the research has 12 profiles. The table below has 13 rows, because the two web standards come from two separate bodies: W3C for CSS and WHATWG for HTML.

ProjectWhat kind of unitWho holds the nameLicenseLabelBackdrop CMSSoftware project in Software Freedom ConservancySoftware Freedom Conservancy[53](#737cc023-5d7c-421d-af27-ec59ff914ca7)GPL v2 or laterverifiedDrupalSoftware project, with the Drupal AssociationThe project’s founder, as an individual[54](#6cfe27b4-7aa1-434c-aa1e-0b9cf2d0b616)GPL 2.0 or laterverifiedGhostSoftware project; the hosted service funds the Ghost Foundation, which calls itself “a non-profit organisation” whose “legal constitution ensures that the company can never be bought or sold”[55](#1564e0fb-73ba-4585-9ef2-76f811c53167)Ghost Foundation[56](#15328991-707f-404a-a8ea-910b265b744e)MIT[57](#435f7116-13e8-4013-9884-9979e24a96d4)verifiedJoomlaSoftware project, with Open Source MattersOpen Source MattersGPL 2.0 or laterverifiedMariaDBSoftware project, with a foundation and a companyMariaDB Corporation Ab, per the published agreement[58](#25060c15-8e8f-426c-a286-54e3b10fb220)GPLv2[59](#55623318-5009-4b9c-8317-deb741361872)verifiedMySQLA company’s productOracleGPLv2, plus a commercial license[60](#f9551987-4fcb-48fe-9104-869fee89229a)verifiedNode.jsSoftware project at OpenJSOpenJS FoundationMITverifiedOpenJS FoundationFoundation (a membership corporation)OpenJS FoundationIts projects pick from five approved licensesverifiedPHPSoftware project; the PHP Foundation runs through a fiscal hostNo trademark foundBSD 3 Clause, as PHP License 4[61](#2e8b5b7d-518a-46c1-91e6-90445a5ed5a9)verified; name unknownTYPO3Software project, with the TYPO3 AssociationTYPO3 Association, which decides how the trademark is used[62](#cb7d4039-543b-436a-be6f-b4d119374f00)GPL 2.0 or laterverifiedW3C (CSS)Standards body (a nonprofit)W3C[63](#f00e708d-135c-48d0-b53c-96b28fb1c64a)W3C Software and Document LicenseverifiedWHATWG (HTML)A contract among four browser makersNot foundCC BY 4.0[64](#bc75bbf1-98d9-429f-86b2-ffabc3f4f0d0)verified; name unknownWordPressSoftware project, with the WordPress FoundationWordPress Foundation[65](#3dac79dc-ff79-49bf-ab49-8b19e27e6e32)GPLv2 or laterverifiedThe open source projects Merge Conflicts compares, A to Z: what each one is, who holds the name and which license it uses“Unknown” means I searched and didn’t find it. It doesn’t mean the thing doesn’t exist.

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

One row needs a note. The MariaDB Foundation’s trademark page names the owner as “MariaDB Corporation Ab,” a Finnish company. The company’s own legal page calls itself MariaDB plc.[66](#e12fdb2a-fd36-4507-a618-a88580604d2d) I’ve named the owner exactly as the published agreement does.







### Who decides in each of these open source projects, and where is it written down?

Same rows, two new columns. The last column is the one document I’d open first if it were my project. The rows answer different kinds of decision: license changes at Drupal, committee membership at Backdrop, board elections at Joomla and TYPO3, and technical decisions at WordPress.

ProjectWho decides, and how they’re chosenWritten down atLabelBackdrop CMSA Project Management Committee; new members need a unanimous committee vote[67](#6fc9d985-0516-4d06-b600-c4d6a96f4bf1)backdropcms.org/about/leadershipverifiedDrupalThe project lead decides license changes; the Licensing Working Group can only recommend[68](#5ca86c1a-2a91-4874-a556-93b938a10036)Licensing Working Group charterverifiedGhostGhost lists its founders as CEO and CTO; no board page found[69](#6c604d2e-a00d-47d4-8a2f-4c83617b85c7)ghost.org/aboutverified; board unknownJoomlaA board of three department coordinators and four officers, elected through its official teams[70](#c701ab65-60c8-491a-8ce1-3f5aca2c03aa)[71](#431be99e-d495-4809-9818-ea2b93662653)volunteers.joomla.org; Open Source Matters election policyverifiedMariaDBThe Foundation’s board, which “does not make technical decisions”[72](#7b676251-f078-4537-be94-8781d5f41147)mariadb.org/aboutverifiedMySQLOracle, “the project lead for MySQL community edition”; its steering committee FAQ lists “Oracle (majority),” and there’s no foundation[73](#6273b12a-c5a3-4042-8237-abc997831f9d)MySQL Community Governance ModelverifiedNode.jsA Technical Steering Committee, “a subset of the collaborators”[74](#e5d81d9b-c3e4-4e80-a498-fccd765d5f66)GOVERNANCE.md on GitHubverifiedOpenJS FoundationA board with one director per Platinum member, plus seats elected by Gold and Silver members and by the Cross Project Council[75](#c09d5cf5-2692-4c2c-80d1-25f9699bfaf0)OpenJS 2026 board announcementverifiedPHPProposals called RFCs, passed by a two thirds vote[76](#e10d5634-9d00-47d4-8ded-7f0156f1d208)wiki.php.net/rfc/votingverifiedTYPO3About 1,100 members elect the board at a yearly general assembly[77](#e2cb5397-6ce4-4deb-83d1-aea67b0f4aab)typo3.org/project/associationverifiedW3C (CSS)A Board of Directors with “ultimate authority”; members elect part of it[78](#3b52d94f-35eb-47dc-aba7-611df7e6cd48)W3C Groups pageverifiedWHATWG (HTML)A Steering Group of browser engine makers, with “final say in all matters”[79](#f6bf90f8-ae67-4fb7-b792-5e3f6638037e)whatwg.org/sg-agreementverifiedWordPressA core leadership team “led by co-founder and lead developer”; lead developers hold “final authority on technical decisions”[80](#3ef77697-29b8-4a72-9d32-a88917172ac5)Core Handbook, “Project Organization”verifiedWho decides in each of the open source projects Merge Conflicts compares, and the document that says soThe WordPress row quotes WordPress’s own handbook, the same way the others quote theirs. Season 2 goes question by question; this table is only the map.

### Why these open source projects?

### The stack WordPress runs on

- **Projects:** PHP, MySQL and MariaDB.
- **Why they’re here:** WordPress’s requirements page asks for PHP 8.3 or greater, and for MariaDB 10.11 or MySQL 8.4 or greater, as reread on November 20, 2026.[81](#0ca71cb1-8811-4a15-9e6c-5555215099a7) Without them, your site doesn’t run.
- **What they add:** two ways to run a database project. MariaDB pairs a foundation with a company. MySQL is one company’s product.

### The standards WordPress renders

- **Projects:** CSS through W3C, and HTML through WHATWG.
- **Why they’re here:** every WordPress page is HTML and CSS. WordPress’s own coding standards say pages “should be verified against the W3C validator.”[82](#21bfb912-ab41-4d39-9eca-0a2ad4ba5ebf)
- **What they add:** standards bodies decide differently from software projects. One is a nonprofit with members. The other is a contract among four companies.

### The JavaScript side

- **Projects:** OpenJS and Node.js, as two rows.
- **Why they’re here:** the Block Editor Handbook calls Node.js “essential” for block development.[83](#a4fee8d7-72b4-4224-89c5-20e854c6e059)
- **What they add:** a foundation and a project it holds the name for. Keeping them apart shows which body decides what.

### Other content management systems

- **Projects:** Drupal, TYPO3, Joomla, Backdrop and Ghost.
- **Why they’re here:** they do the same job WordPress does. If you build sites, you may have met one of them in a client’s old stack.
- **What they add:** five different answers to “who’s in charge of a CMS?” Drupal and Backdrop also share a history, which the fork section covers.

### xz-utils: one maintainer holds every key

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2024-02-24 and 2024-03-09:** releases 5.6.0 and 5.6.1 shipped from a second maintainer account.[84](#05d4b45c-a8b7-40c5-95dc-77e6bb790785)
- **2024-03-29:** a downstream engineer posted “backdoor in upstream xz/liblzma” to the oss-security list.[85](#c765e06e-15d6-4667-9911-fe26117a6ace) The US Cybersecurity and Infrastructure Security Agency (CISA) told users to downgrade the same day.[86](#0d25ca9a-58d3-467d-a573-9b98da9eb33c)







[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2024-03-30:** the original maintainer wrote that the second account never had access to the project’s own site or git server. It could reach only the assets hosted on GitHub.[87](#42f8c812-31bf-4b08-b10a-84e4724baec2)







### ClassicPress: a small fork votes on its own future

[source-derived](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2022:** the directors resigned and named their successors, with $352 in the bank at the time.[88](#0c713963-12a6-40ca-8677-217134269d73)
- **December 2022:** core contributors polled on the next step. A director reported 20 votes to fork WordPress again and 18 to continue as is.[89](#27444615-3e3a-4a9b-ba03-8b5d0f3ff4f1)







### What happened after the RubyGems access change?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2025-10-17:** the Ruby core team took ownership of the repositories, with “no changes to licensing terms.”[90](#79ab9f24-e2c1-42d9-91fc-bcc708e03d12) Ruby Central would keep managing the projects, now jointly with the Ruby core team.
- **2026-03-31:** Ruby Central published an incident report by a member of its Open Source Committee. It said Ruby Central “lacked the structural ability to make this change directly.”[91](#e852657a-1fec-4076-9e82-f67f1c2b64b9)







### Forks already in the comparison set

You don’t need extra cases for forks. Four of them sit inside the main rows:

- **Databases:** MySQL to MariaDB.[92](#39dbb176-9b5c-4a06-913b-894c75d9d5ff)
- **JavaScript:** io.js and Node.js.[93](#4dc107f7-b380-4b6a-a5ea-c939db4e1a3f)[94](#360d5d62-fea5-47c7-91e0-b267a4acd44c)
- **Content management:** Mambo to Joomla,[95](#5b2c0511-a9f3-4860-a7a6-7c2ab948cc6a) and Drupal to Backdrop.[96](#c2b4e84c-ea27-4a95-a760-d877dc2e3556)

### How big is the record behind the comparison?

ItemCountDistinct incidents (WordPress history only)86Claims2,417 (2,406 public)Sources2,840The Merge Conflicts research record, as of October 30, 2026Every claim carries one of six evidence labels, which the methods page explains. Counts are floors, not totals. The incidents cover WordPress’s own history; the claims and sources cover every project. The methods page publishes these counts and dates them.[97](#8ba528f7-f155-4d6f-84fa-b753bd4bac92)

## 🧱 The open source stack: who approves a change at each layer

This table backs [the post on who decides the open source stack under WordPress](https://courtneyr.dev/2026/11/10/open-source-stack/), published November 10, 2026.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

LayerProjectWho approves a changeContributor agreementBrowserChromiumAn owner of each directory a change touchesNot checkedBrowserFirefoxThe module ownerNot checkedBrowserWebKitReviewers; reviewers also pick new reviewersNot checkedStandardsW3CWorking Groups; a Council hears formal objectionsNot checkedApplicationWordPressCore leadership team; lead developers on technical callsNot checkedLanguagePHPRFC voters, two thirds majorityNot checkedDatabaseMySQLOracle, as project lead; a steering committee reviews changes to the governance rules[98](#1d46ca40-7dd8-477d-b593-8720aa4735de)Not checkedDatabaseMariaDBNot named on the pages read; most developers work for MariaDB plc, and the board doesn’t decide technical questionsNot checkedWeb serverApache httpdA project committee; committers vote, and any binding veto stops a consensus changeASF individual agreement, for maintainers and large contributions[99](#38c53206-5722-490a-8366-671755e6febd)Web serverNGINXA technical committeeF5’s agreement, for every contributor[100](#2d49b12b-6195-4416-9217-6bf8e26dbe4f)Operating systemLinuxSubsystem maintainers, then the top maintainerNot checkedBuild toolsNode.jsOpenJS hosts it; members elect or appoint the boardNot checkedBuild toolsPHP\_CodeSnifferNot stated in its README; label: unknownNot checkedThe open source stack under a WordPress site, top to bottom, and who approves a change at each layer





Then pick one layer and read one page:

- **Linux:** [the kernel development process guide](https://docs.kernel.org/process/2.Process.html).
- **Apache or NGINX:** [Apache’s voting guidelines](https://httpd.apache.org/dev/guidelines.html) or [NGINX’s governance page](https://nginx.org/en/docs/governance.html).
- **MySQL or MariaDB:** [MySQL’s Community Governance Model](https://dev.mysql.com/community/governance-model/) or [the MariaDB Foundation’s about page](https://mariadb.org/about/).
- **PHP:** [the PHP RFC voting rules](https://wiki.php.net/rfc/voting).
- **WordPress:** [the Core Handbook’s Project Organization page](https://make.wordpress.org/core/handbook/about/organization/).
- **Your browser:** [Chromium’s code review guide](https://chromium.googlesource.com/chromium/src/+/HEAD/docs/code_reviews.md), [Mozilla’s module ownership policy](https://www.mozilla.org/en-US/about/governance/policies/module-ownership/) or [WebKit’s commit and review policy](https://webkit.org/commit-and-review-policy/).

## 💸 Sponsorship: what a payment returns

These tables and lists back [the post on what open source sponsorship buys](https://courtneyr.dev/2026/11/11/open-source-sponsorship/), published November 11, 2026.

### What open source sponsorship returns, project by project

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Here’s open source sponsorship as a table, sorted A to Z. WordPress is one row. Each row names what you pay for and what comes back.







OrganizationYou pay forWhat comes backDoes it include a say?Drupal AssociationRipple Makers membership, from free to $50 or more a monthRecognition, newsletters and webinars at paid levelsThe free level carries the voting rights[101](#76b7e9de-243f-40f7-b2a1-45e0873b0ca3)MariaDB FoundationSponsorship, EUR 5,000 to EUR 500,000 a yearAn observer at board meetings, or entries in the board selection poolNo guaranteed seat[102](#91e626c0-5fcc-44e6-b1f3-e7411b83d18f)OpenJS FoundationMembership at Platinum, Gold or SilverPlatinum members appoint directors; Gold and Silver members elect theirsYes, by class[103](#46a854e2-aa43-4dcf-a1cf-d07bb138fde9)PHP FoundationSponsorship at Silver, Gold or PlatinumAn Advisory Board seat, and up to three board seats at PlatinumAt Platinum only[104](#3c434ce4-4509-4294-8d57-b4cab4676cf1)TYPO3 AssociationMembership at five levels, EUR 10 to EUR 13,750 a year plus a one time feeOne vote at the General Assembly. Discounts of 10 to 45 percent from Bronze up. The word mark in paid ads at Gold and Platinum[105](#7a228e96-508e-43b7-80b5-a6c43c2b4efd)Yes, the same for every member[106](#8a6bcdf5-b74a-4de7-ad82-f08147b75390)W3CMember dues, set by size and revenueOne vote per Member, whatever the feeYes, the same for every Member[107](#b0392bbb-ca11-46bd-b074-fe4ba6c624f8)WordPressDonations, event sponsorship, hosted servicesA name on a list, event benefits, a thank youNone stated on the pages I readWhat a payment returns in seven open source organizations, A to Z, as each one’s own pages state it[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

I haven’t read sponsor pages for Backdrop, Ghost, Joomla, MySQL or the WHATWG yet. So they aren’t in the table. Unknown isn’t the same as absent.







### Sponsor tiers that come with a seat or a class vote

Some open source sponsorship comes with a formal say. Here are three examples.

- **PHP Foundation.** Its governance page sets a board of 5 to 10 people. It also grants up to three of those seats to qualified Platinum sponsors.[108](#daf0fbf5-a018-4946-ad25-d8fb6d90deab) Meanwhile, the home page lists four Platinum sponsors today.[109](#8679fcce-f81e-4b1a-ab3d-92e366cea493)
- **OpenJS Foundation.** Each Platinum member appoints a director. Gold and Silver members, in contrast, elect directors as a class.[110](#1dd315da-1e5b-463a-8b15-75d25ef59672)
- **MariaDB Foundation.** Platinum buys one entry in the board selection pool, and Diamond buys two. However, the sponsor page says sponsorship doesn’t guarantee control over technical decisions.[111](#d2af7578-d62c-425e-94fe-c5c7358585b3)

### Advisory access and observer seats

Other open source sponsorship buys a voice, not a vote.

- **PHP Foundation.** Sponsors at Silver and above sit on an Advisory Board. Its members “do not hold decision-making authority.”[112](#9fce4f68-8228-4319-bebc-f7fc07b0a470) Still, when the board declines a formal recommendation, it owes a written reason within 30 days.
- **MariaDB Foundation.** Gold sponsors get an observer at board meetings.[113](#39a820c2-9e11-4237-8304-0f905d658ee7)
- **W3C.** Each Member gets one vote, whatever fee it pays.[114](#03f53793-c00a-4ca0-95ed-e0673d34d699) In other words, a bigger invoice doesn’t buy a bigger vote.

### Sponsorship that returns benefits only

The third kind of open source sponsorship returns benefits only.

- **Drupal Association.** The free membership level carries the voting rights. Paid Ripple Makers levels, on the other hand, add recognition, newsletters and webinars.[115](#4ca26d9c-5dab-45bc-888a-3390ebe7129d)
- **TYPO3 Association.** Every member has one vote at the General Assembly, under Article 15.[116](#7693437d-73cc-4fc0-a5a0-dcbe12fd4bbc) Higher levels don’t add votes. They add discounts of 10 to 45 percent from Bronze up, on events, certifications and TYPO3 partnership.[117](#e3fdd434-3ea8-4528-8fbe-7686682c026f) Gold and Platinum also get the TYPO3 word mark in paid advertising. On October 29, 2026, members adopted rules for six Units.[118](#0f2cef73-e992-4497-a27e-9cbf292a11c5) A Unit Member votes in the Unit Council, and that role requires an active personal Association membership.[119](#c62f535c-504d-446a-8b5e-401b16b6e0db)
- **WordPress.** It has five channels and no vote. That row gets its own section below.

### Beyond money: users, paid contributors and leaders

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Paid contributors.** MariaDB’s governance repository lists ten Stewards and maintainers. Nine of them give MariaDB plc as an affiliation.[120](#de5fbc91-bad1-4281-ae84-bfbcfb65fae5) Meanwhile, the PHP Foundation says its contractors wrote about 42 percent of 2025 commits to PHP core.[121](#d7bee138-4a78-402e-9d52-1b9e95336954) A share of the work isn’t a share of the votes, though. Season 2 comes back to that.
- **WordPress leaders.** The Core Handbook says the project is “led by co-founder and lead developer Matt Mullenweg.”[122](#c64ce10e-5609-4c1e-8f00-327045f3022f) However, the same page gives five lead developers the final word on technical decisions.
- **Drupal’s Project Lead.** Its core governance page says the Project Lead, Dries Buytaert, sets direction and breaks ties. Meanwhile, core committers decide by consensus.[123](#d4c354e8-2c5f-46ee-805d-73010cfcc3ee)
- **MySQL.** Oracle nominates the first committers and project leads. It also keeps authority over licensing and trademarks.[124](#35e44a98-6294-478d-8ba1-583966edcaab)







### Donating to the WordPress Foundation

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **What you pay for:** education programs, trademark protection and free access to the software.[125](#16d15546-962a-4368-aab0-9760b5dfb1d4)
- **What comes back:** your name on the Donors page, if you pick an annual plan. Plans run from $10 to $5,000 or more a year.[126](#0d473b3d-10d1-47cf-af05-3feacc5e2768) The donate page mentions no seat and no vote.
- **Who decides the spend:** three directors. The Foundation’s 2024 tax return lists no members, so nobody outside the board elects them.[127](#53af2cf9-9719-4fba-8cc5-2864885df642)
- **How big it is:** $93,131 in revenue for 2025. Of that, $47,131 was general donations.[128](#54e8d5dd-af63-4fef-b86c-4f3c1f8015ba)
- **Where it went in 2024:** $100,000 of $121,957 in expenses went to the Internet Archive. That year, do\_action events got $1,066.[129](#2f0ccb85-2ee2-469a-ab50-be82955daf78)
- **The stated reason:** the Foundation’s post says it has long supported the Archive’s work to preserve the web. The board’s vote was unanimous.[130](#e702da73-0746-4bc6-b572-68ffb321bcf2)
- **What the donate page tells you:** it names education programs, the trademark and free access.[131](#b8779c20-a440-43e1-9735-03462453a6fd) However, it doesn’t mention the Internet Archive or gifts to other nonprofits.







### Sponsoring events: the Global Partner Program

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **What you pay for:** WordCamps and meetups. The 2026 tiers cost $180,000, $110,000 and $60,000.[132](#62e4602d-9543-4fd5-997f-4240eb3eacf1)
- **What comes back:** sponsor tables at local WordCamps, a landing page, event tickets and recognition posts. However, no tier lists a vote, a seat or a role in decisions.
- **Who holds the money:** WordPress Community Support PBC, the Foundation’s subsidiary. In 2025 it took in $3,794,359 in sponsorship, about 89 percent of its operating revenue.[133](#53d25bf2-27ae-4c7c-838c-4c7b4fac0a90)
- **Who approves a sponsor:** project leadership. A January 2025 Community Team post says sponsorships need its approval, and it names the project lead and Mary Hubbard as project leadership.[134](#7317a5f6-2bd9-4b23-8946-5c695cafaee1)







### Sponsoring infrastructure

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

WordPress.org’s sponsorships page lists one organization, Salesforce. It says Salesforce gives $8.8 million a year in kind, as premium access to the project’s Slack.[135](#cc57a1d9-80b3-4c2a-ae90-473d74060b65) However, the page doesn’t say what Salesforce gets back. (A thank you counts.)







### Open source funding proposals inside WordPress

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Contributors have proposed changes on the money side too.







- **2018.** A proposal described a public pledge list for companies that pay contributors.[136](#57f09fd5-0c6b-4415-87a7-01ca7a1422c9) A pledge list now runs on WordPress.org.[137](#917aacf1-a5e7-402f-9259-375faf3a39d7)
- **2024.** A proposal recommended sponsorships tied to one task, project or release.[138](#b3104043-c56c-4035-be69-feb60fa5316c)
- **2024.** WordPress Community Support reported $665,000 in 2023 global sponsorship and a loss of about $148,718.[139](#7dff0713-611e-48f0-bcfd-f487eb375f64)
- **2026.** A proposal asks for a $30,000 education sponsor fund with two published selection criteria. Every sponsor would get the same recognition.[140](#41463f07-c381-4b1d-9137-cab821a64e1d)

[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Neither the 2024 nor the 2026 proposal records a decision on its own page.







### Open Collective and the security fund

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The Foundation also runs a host page on Open Collective.[141](#fa176430-bc08-45ba-b229-cf88ff7bef0c) A 2019 Community Team post says moving do\_action charity hackathons there makes each event’s budget public.[142](#220edb0c-93ad-4742-9b9a-138d4ff052b3)







### What the hosting page says about itself

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Who’s listed:** Pressable, Bluehost and Hostinger, as read on November 10, 2026.[143](#d06b22f0-2e0b-480a-9185-6f50e43b07cd)
- **How hosts are chosen:** the page calls its own listing “completely arbitrary.” Still, it names factors, among them contributions to WordPress.org and current system software.
- **Where the money goes:** the page says some hosts donate part of your fee to support WordPress.org.
- **Who decides:** a Meta ticket once asked to remove or rework the page. It was closed, and the closing note put the listing at the project lead’s discretion.[144](#f9ddcb65-b0fe-4bec-ad26-f56399836a63)







[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The page doesn’t say who receives that donated money, or how much it is.







### What contributors proposed: a matrix, Project Bedrock and a rubric

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Contributors have drafted written criteria for this page since 2019.







- **2019, the Requirement Matrix.** A working draft says the criteria should filter hosts and “should not result in a rank.”[145](#2daa1b19-5625-4445-90be-c0cff1094726)
- **2020, a rubric.** A chat recap says the project lead was “+1.” Next, people who don’t work for hosts would evaluate hosts, then recheck yearly.[146](#4a7d061b-265e-46a8-85fd-ed7180633216)
- **By 2023, Project Bedrock.** Javier Casares proposes a directory that any host can join by meeting minimum requirements. A review team would check each entry.[147](#d7fd0cb0-e9e8-412e-a5c7-572733012e36)
- **2023, the Hosting Application Rubric.** It scores hosts from 0 to 10 on contributions, company criteria and values. Trademark adherence is one criterion.[148](#89f87523-ec67-402a-a4d6-c0bcfd215fea)
- **2024, a directory proposal.** Hosts would publish their own data for volunteers to review.[149](#8ef41fa7-093b-4546-a448-888ec4e901ac)

Disclosure: I drafted the 2023 rubric. A Make post credits me by name.[150](#1deb37b9-619d-4335-873a-3caf7c8ba9bb) I worked at GoDaddy then.

### What has been said about payment, 2005 to 2026

Here are the statements in date order. I’ve left out a 2016 comment and a 2014 interview that I couldn’t verify.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2005.** The page told visitors that some hosts would donate part of the fee back.[151](#a51dd6bb-2db2-4b93-beb6-3e3279f6fa59)
- **2021.** The project lead wrote, “No one can pay to be on the page, and there are no affiliate payments made for customers sent from that page.”[152](#554eb462-0e6a-4f07-9315-0c9fff1b7d39) The stated reason for one decider came with it. The page drives so much business that a larger group would raise the risk of bribery or conflict. In the same report, the Executive Director at the time said she knew of nobody who had paid.







[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **2025.** In a sworn declaration, the project lead said companies seek endorsement on WordPress.org for their hosting. When a deal succeeds, a partnership follows, and its terms stay confidential.[153](#c6faeddc-9651-4e21-8694-3bf15c3754f2) A sworn statement is an account, not a finding.
- **2026.** WP Engine’s complaint alleges that an internal document says money sent from the hosting page went directly to the project lead.[154](#6677bd8b-d834-453f-bd44-c097f75a1ca3) However, the company’s name and the amount are redacted. The defendants deny the complaint’s characterizations, and no court has ruled on this allegation.[155](#9559f003-6e22-48f6-859a-894671a728db)







### Who appears on which public list

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

You can check one thing yourself: which names repeat across public lists. This is a matching table, not a cause.







OrganizationHosting page[156](#86283cbe-ae2f-43cd-88f1-39e5771357ff)Foundation Donors page[157](#b13418d2-a275-4a4f-9b3f-c72f5667e122)2026 Global Partner[158](#961ede7c-8303-4a1f-b2c2-140c68bbaf6e)Named as compliant in the trademark policy, November 2024 to February 2025[159](#d8f1c132-dba9-4c67-8d9d-2d3aa6fe5071)AutomatticNot by that nameYesYesYesBluehostYesYesYesYesGoDaddyNoNoNoYesHostingerYesYesYesYesInMotion HostingNoYesNoNoPressableYesYesNot by that nameNoSix organizations and four public WordPress lists. The hosting page and Donors page were read on 2026-11-10; the other two columns come from pages read on 2026-10-26Two rows cut against a simple reading. First, GoDaddy was named as compliant and appears on none of the other three lists. Second, InMotion Hosting donates and isn’t a listed host. Also, the Donors page shows current annual plans and 97 anonymous donors. So it can’t tell you who gave in earlier years.

### Who holds what in WooCommerce

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Name:** Woo’s guidelines say “Automattic Inc. owns and oversees the Woo trademark.”[160](#c91c2c69-f105-4b6f-95da-95ee761fa11a)
- **Code:** WooCommerce is open source, and anyone can fork it. However, the same guidelines say open source licenses cover copyright only, not the marks.
- **Security reports:** they go to Automattic’s bug bounty program, according to the repository README.[161](#caa66783-abd5-4d39-b404-550304a70b33)
- **Who decides:** the README names no governance document.[162](#badd6663-7862-4d10-b5fc-b7f23aa2c6b9)







### Who holds what in WordPress

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Code:** contributors hold the copyright. The license file reads “Copyright 2011-2026 by the contributors.”[163](#bf3002e2-5291-4d35-a3d7-f3f008da2ea2)
- **Name:** the WordPress Foundation holds the marks. Automattic gave them to the Foundation in a 2010 agreement.[164](#6dc07cef-2a8c-49d9-9bae-5c68d855452c)
- **Commercial license:** that agreement licensed the marks back to Automattic for hosting on WordPress.com. The license is exclusive, perpetual and royalty free.
- **Fallback:** if a court ever voids that license, the agreement treats the donation as if it never happened.







### One offer, two sets of marks: what the court has ruled so far

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

On October 1, 2024, Automattic published a term sheet it had offered WP Engine that September.[165](#db5db1b9-3230-47de-b169-155c927d3580) It would license the WordPress and WooCommerce marks together, with Automattic as licensor. The price was 8 percent of revenue, paid as a royalty, as staff time on WordPress, or a mix.







Then WP Engine sued and called the demand extortion. Here’s where the rulings stand, in pairs.

OrderWent toward AutomatticWent toward WP EngineDkt. 169, September 12, 2025[166](#f4ca3943-5ca8-4cc1-afc3-1a8d0bb9550e)Attempted extortion claim dismissed: the statute gives no private right to sue. Computer fraud extortion claim dismissed, with leave to amendInterference and unfair competition claims surviveDkt. 410, September 24, 2026[167](#3e251bec-3f40-49e0-a0ad-ac21319018b0)Computer fraud extortion claim dismissed for goodAntitrust counts 11 to 14 survive. Trademark counterclaims dismissed as Automattic and its chief executive brought them in their own rightRulings on the license demand in WPEngine v. Automattic, each made at the pleading stageA pleading stage ruling tests whether a complaint states a claim. It isn’t a finding of fact. Also, the second order treats Automattic and its chief executive as neither owners nor registrants of the marks. Meanwhile, the Foundation’s and WooCommerce’s counterclaims continue. Trial is set for October 19, 2027.[168](#f6ad8e93-bdbe-4865-9e2c-4396cf6d0162)

## 🚪 First contributions: doors, waits, credit and cohorts

These tables and counts back [the post on where to make a first open source contribution](https://courtneyr.dev/2026/11/12/first-open-source-contribution/), published November 12, 2026.

### Which was my first open source contribution, 2009 or 2014?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

TimeWhoMessage18:36courtneydawnso that leaves Template Hierarchy which seems to be abandoned, Post Formats which needs someone who is good at them to go over it and make some tweaks for first draft, and Web Fonts18:38CourtneyI’m making progress on Post Formats now on my own sites, and will finish the area I started at NYC contributor day18:39CourtneyShould have more written this week on the tutorial18:39courtneydawngreat Courtney – tracy had thought youhad done as much as you felt comfortable18:39courtneydawnWe prefer you continuing on it 🙂 And tell us if you need any help!!18:39courtneydawnI will update the statusChat log from #wordpress-getinvolved, September 2, 2014. Times are UTC.





### A first contribution without code, project by project

Disclosure: I work at Pantheon, a WordPress and Drupal host.

These twelve rows come from [the post that explains which projects this series compares](https://courtneyr.dev/2026/11/09/open-source-projects-compared/). That post also lists the OpenJS Foundation. It sits outside these tables, because a first contribution goes to a project, and Node.js has its own row. Each project’s own pages name where a first open source contribution can start without code. Each also sets a gate before your work can count. Some gates in the third column apply only once you send code. Here they are, A to Z.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectFirst step without codeWhat you need, or sign if you send codeBackdrop CMSTest a pull request in its sandbox site[169](#116bb6cd-54ce-4dce-b36b-01a5614ea303)GitHub account; an issue for every pull request[170](#546d9b2d-f858-4744-9bb6-bbb2584ed6ee)DrupalTriage one issue report[171](#d9db1326-0db5-4815-aa1b-492cc7f412be)Drupal.org account; accept terms before Git access[172](#38844499-1274-4ead-a015-052c9d28884b)GhostAnswer questions on the forum[173](#e4809705-df8d-4b8f-941b-289d1a5437e9)License grant takes effect when you contribute code[174](#479ab619-0606-4ead-9769-de3639df15c9)JoomlaAsk the volunteer team to place you[175](#4a8a460d-baea-48ee-9c68-5dc45c627a7a)GitHub account to test patches; no agreement named[176](#9500c473-059c-452b-9625-9bee9f60702f)MariaDBTry a development release and report back[177](#9b31fc06-8f84-4fa9-b9d1-058b6fb19193)Its contributor agreement, or a BSD license[178](#cd79b0a7-bca4-48a2-a06c-1294d24ddf41)MySQLReport a bug[179](#e90e3a71-71cb-415f-a636-79b87bf50ad8)Oracle Contribution Agreement, signed before Oracle takes your code[180](#b9b6a8d1-1d95-4a2e-afc1-9f4bf9ee15be)Node.jsTriage issues or answer questions[181](#8485487b-5dc8-404d-9081-764158a05d06)A sign-off line on every commit[182](#39b738b2-d8bf-43d3-bb1f-400322098c62)PHPRun the test suite on a release candidate[183](#da802a29-0b08-4518-9952-0cb5a053cbe4)Nothing signed; a pull request certifies your rights[184](#5689a7c9-b90a-4835-a97f-b1e4d0e6c7be)TYPO3Help a team with its work[185](#e0345116-81e1-4967-abae-d42fd6eb0b14)A my.typo3.org account; no agreement named[186](#ed4bcb2b-6da2-49b1-b526-b96c96e95d22)W3CReview a draft and send comments[187](#49781d85-ef2e-4428-bfaf-a4e9a9944d29)Patent commitment for substantive changes from outsiders[188](#1f7eba82-d31a-4723-b0c0-65fb13cc12cd)WHATWGReview a standard and file an issue[189](#ddd2c83f-0f3c-4fc8-bc95-e7394ae64ad2)Participant agreement; some employers must sign[190](#d4353099-8548-411f-b595-7cac936c6c5e)WordPressPick a starter guide by skill[191](#12d2fc80-0c30-4c5b-a9ac-97ae0594fbc8)WordPress.org account; no separate agreement found[192](#28d88c47-f1fb-4775-9af0-233ff4153501)Where a first contribution starts in twelve open source projects, A to Z, as each project’s own pages state it





### What stands out in the first table

- **WordPress sorts by skill.** Its [Contribution Pathways index](https://make.wordpress.org/handbook/pathways/) groups starter guides by skill, and it first appeared in March 2026.[193](#eca07555-982c-4791-b0bc-c541357c6fde)
- **Five WordPress steps need only an account.** For example, you can answer a forum question, suggest a translation, submit photos, caption a video, or test a ticket in the browser.[194](#c04eba04-649e-4908-9d49-97cb01fd234a)
- **A first open source contribution can be tiny.** In WordPress, one translated string earns a badge.[195](#bdd8d9c1-9bbb-443c-956d-6e1abcdbe0fd)
- **Ghost and MySQL list narrow paths.** Besides donating, Ghost’s only path without Git is its forum. Meanwhile, MySQL’s documentation path isn’t open yet.
- **Several pages are old.** Drupal’s list of contribution areas, for instance, dates from February 2021.[196](#b5d2a1b7-b7d0-4a51-a291-70c8d7607dd9)
- **Some lists don’t say what’s open.** On November 11, 2026, Joomla showed 99 help wanted roles across 25 teams, with no posting dates.[197](#2ff22d47-0f55-4ffa-ba3f-d933fe48c4ce)

### What you sign, and who else has to

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Nothing found:** WordPress, PHP and Backdrop. WordPress’s licensing page says contributing licenses your work.[198](#096cfccc-d3fb-4e76-b0a7-b6004cb97179) However, no page I read says “no agreement” in those words, so this one is my reading.
- **One line per commit:** Node.js asks for a sign-off line and doesn’t require a legal name.[199](#13c5bdfc-339b-4041-a4f5-9f750ed81c07)
- **A choice of two:** MariaDB takes its own agreement or a BSD license.[200](#0a7c1e26-bfeb-4b7a-998c-ae90c1ee3013)
- **Signed agreement:** MySQL needs Oracle’s agreement signed before it merges your code.[201](#e992cc35-1173-4f77-b20e-ce7d81b16f1a)
- **Your employer’s signature:** WHATWG asks people who work in web technology to have their employer sign.[202](#50e3980e-702e-4c71-82b4-ad778d31ee39)
- **A patent promise:** W3C asks outsiders for a patent commitment on substantive changes.[203](#19aaff9f-e985-4c31-b58e-236fc26cc2fc) Typo fixes pass without one.
- **Unknown:** I found no current agreement page for Joomla or TYPO3. That’s unknown, which isn’t the same as none.







### How long a first contribution waits

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Only one project I read publishes both a target and its own numbers. MariaDB’s target is a first response within “7 calendar days.”[204](#5e57da91-6191-435c-99c1-6312e82e0ee0) Its statistics for January to June 2026 count 777 new pull requests: 246 answered and 174 not. The rest were drafts, or merged or closed by their authors.[205](#9f87c9ab-30ec-4a35-a9a0-566e51e47ea5) However, one caveat applies: the count covers every pull request, not only a newcomer’s.







WordPress publishes its waits too. For example, on November 11, 2026, its Core components page showed tickets with no replies: 115 in Editor, 91 in General and 50 in Taxonomy.[206](#a04be405-6fb8-4834-95f4-d115797df002) In April 2026, a project post gave the stated reason for new onboarding work: “Teams want help, but we’re losing people at the door.”[207](#3332e92e-1f65-4bcf-9754-e4353c390470) It also named scattered onboarding and unanswered Slack messages. (Every project has a door. Fewer have a doorbell.)

Meanwhile, the same project credited more than 800 contributors in WordPress 7.1. Over 170 of them were first timers.[208](#b1f9be9b-f376-4823-961f-bd7cf7d5e3c1)

One study helps here, at its own size. Researchers looked at 111,094 pull requests in ten projects. Newcomers who got a human reply within a day were more likely to open another pull request.[209](#0c341194-b562-4868-9362-aef49ef10d58) Still, that’s an association, and it’s about code. It doesn’t prove a fast reply keeps a translator.

Some projects write the wait into their rules instead. For example, Node.js lets a change land with two approvals after 48 hours, or one after seven days.[210](#2a698168-267b-40e8-888d-3c8a1d2b1402)

### Who says your open source contribution counts?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectWho credits the workRoute to a sayBackdrop CMSRelease posts thank contributors as a group[211](#bc851add-6fa2-4716-aec9-951c31f69090)Committee nomination, then a unanimous committee vote[212](#ffaee4f8-4c30-465b-9543-82864a71594c)DrupalA project maintainer grants issue credit[213](#fd36fff2-ffe9-4096-9f84-ec7d0a41b65b)Free membership votes in the yearly board election[214](#a4f09227-15ea-4c11-ad32-3e6a685b8061)GhostRelease notes name the author of each listed change[215](#3824925a-1ac3-484e-b7d2-ae8d1820f559)No contributor vote documented[216](#a9c69668-3489-4bb2-96b5-d7dc25985245)JoomlaRelease posts and volunteer portal profiles[217](#387c2479-5b36-44f3-840a-826fdb88dbc5)Membership in an official team, not a subteam, makes you a voter[218](#82b352b9-d188-4d7d-9587-20ba8f5466bf)MariaDBStatistics posts and a patch log[219](#06c662c8-9dea-4873-b1ea-1fe830644733)Nomination by maintainers and stewards[220](#a00bba74-9fd3-4ca9-8157-e83673e02477)MySQLRelease notes thank contributors by name[221](#93983b4d-2da8-41c5-95f5-67c42329f1e0); release posts give counts[222](#6327f8d5-9aba-4c94-81dd-ef321d9270c5)Nomination; Oracle names the first committers[223](#b8260ca1-9ceb-4359-9761-c8c093c24964)Node.jsCommit authorship and README role lists[224](#ff2c3cc3-a750-4375-96c1-a017db6f9e36)Collaborator nomination, with one week for objections[225](#b4eccfdb-873c-4f29-8503-eda5b69110cf)PHPA credits page names contributors by role[226](#ea23b828-8588-4a89-a662-b3298a11588b)A php.net account and code contributions earn a vote on proposals[227](#fc6c6bbb-ca79-423d-9fab-c83427ad1072)TYPO3A monthly post names contributors[228](#86cd762a-8c63-4710-ac37-7bb6da252b33)Membership: EUR 10 once, then EUR 10 a year[229](#cf3f888a-3ee4-4de1-a97f-c9559960b119); Units since October 2026[230](#b142519c-82d4-4d10-9ee5-55701b919c7b)W3CAcknowledgments sections; translators are named[231](#0e22ff67-0faa-425f-8e56-de707c603cd0)Members hold committee seats; Invited Experts join groups[232](#af6ab966-5e2c-436b-b312-7f9f6926ef56)WHATWGYou add your own name to the acknowledgments[233](#a8bea3f1-c739-415a-807d-ac993ab42b64)No vote; editors decide, four companies rule on appeal[234](#9bdc4f8e-0a5f-4187-9051-bca24c357e18)[235](#1be96dcc-1996-4139-a593-08fa7dbf6810)WordPressProps and profile badges[236](#b188f623-8a37-4ecd-b697-53d1dde96271)Teams elect reps; committers need the lead’s approval[237](#624d8cb6-fab7-4302-9db0-6f70f35ccb6a)[238](#dc94302d-f5c5-4496-bf79-83ee0d1b2e93)Who credits a contribution and what route leads to a say in twelve open source projects, A to Z, as each project’s own pages state it





### Where WordPress credit is automatic

Disclosure: Training badges are assigned by hand, and I held roles on that team.

- **By count:** one translated string or one published photo earns a badge.[239](#8b6e6544-067a-46b0-b59e-bdcd8d7429da) Similarly, 50 forum replies earn the support badge.[240](#87953462-ba63-4c62-9d17-227eb70ca866) The Support Team’s own handbook, last updated in July 2025, still lists 400 replies and awards by hand.[241](#6071236e-9b27-476e-ae76-77ae33574c17)
- **Hand assigned:** Docs, Training, Design, Accessibility, Test and Community badges come from a person.[242](#9e05e79e-3f4f-444c-ac7a-c787caa43606) A team rep can now grant them from the team’s own Make site, with no network admin needed.[243](#aa17f30b-0035-4c02-a022-ec1e4ac2ad58)
- **Through props:** Core’s handbook says design, writing, user testing and good bug reports deserve props. However, a maintainer has to add them.[244](#97be6f55-978a-49ec-bba6-8733302dcdbb)
- **Not gathered:** the same page says work done in Slack isn’t compiled automatically.
- **Yes, but:** for WordPress 7.1, the Test Team thanked 84 testers by username, and 50 of them had no Test Contributor badge yet.[245](#f6fd537f-8353-4eda-a164-6c390d29893a) The tracker behind that count already finds those testers by scanning Trac. Still, the badge waits for a request, and a Test Team Rep reviews requests weekly.[246](#b1994012-f218-46d5-a40d-5623331dde4c) The tracker also misses testing done on GitHub.

Check it yourself: open your WordPress.org profile and count the badges. Then ask which ones a person had to hand you.

### What could count without a person

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Some of that recognition already runs on software. The rest waits on a person, or on code nobody has shipped yet.







- **Built:** core props, translations, photos, patterns and forum replies award badges with no request.[247](#9b685663-8c0c-4388-a603-2b8b8fca24b2)
- **Found, not awarded:** the Test Team’s tracker finds new testers on Trac, but a rep still grants the badge.[248](#38bbfb7b-d8dc-472b-9c3c-5704482a3155)[249](#3d141654-f9d5-46ce-bade-f28fca86dc94)
- **Faster by hand:** after a recent Meta change, team reps grant badges themselves from their Make site’s Tools menu.[250](#99685b6a-deac-47ce-8b98-b0ec45b41d0f)
- **Proposed:** a Meta ticket from 2022 asks for the Performance badge to arrive with each GitHub contribution. It’s still open.[251](#49e68a0a-ef86-4cde-a11a-eb5c5680adfc)
- **Piloted:** a contributor dashboard tracks support, translation and event activity across teams. It doesn’t award badges.[252](#0558d1ef-1586-4953-86a3-6abf543e2df7)

### From a first contribution to a say

- **Membership:** Drupal Association membership is free on request and votes in the yearly board election.[253](#6e4c92db-e946-41c0-991c-0239e1714dac) Likewise, TYPO3 membership comes with one vote.[254](#25afa362-cd9d-46af-8d83-e31ff8fe48fb) In October 2026, its members also approved Units, contributor groups that will hold their own elections.[255](#3a73d077-967a-4e86-88d5-79471fda8b8b)
- **Team listing:** Joomla’s voters are the members of its official teams. Subteam members don’t vote. That meant 84 and 94 people in two 2026 elections.[256](#92624e4a-8380-4193-9e1a-d3454b8e1bd3)
- **Code:** PHP gives a vote on proposals to people with a php.net account and code contributions.[257](#9f99d38a-ba5f-48d1-bdd6-4f04e3834586)
- **Nomination:** WordPress teams elect their reps.[258](#f7d6a29c-7821-4672-b00e-fe7410f30149) Commit access, however, takes a public nomination and the project lead’s approval.[259](#20ab9e26-64ac-486c-8949-248ac7029456)
- **Organizations first:** at W3C, each member organization has one Advisory Committee representative. Individuals can join working groups as Invited Experts.[260](#6cd179a1-f87c-4711-861c-19b5ce2e3c5b)
- **Nothing documented:** Ghost and WHATWG describe no contributor vote.
- **Yes, but:** a vote isn’t turnout. For instance, Drupal’s ballots fell from 707 to 528 to 307 in three years.[261](#bef01d17-9d73-46df-9c55-e5c6bd2b74e5)

### Mentoring programs count heads, not who stays

Disclosure: I helped write the 2023 pilot proposal, and its closing post lists me as a facilitator.

A mentoring program is one answer to a first open source contribution that stalls. So what do the programs publish?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

CohortMenteesMentorsCompleted2023 pilot[262](#44af43b0-665a-4b43-bcd2-37006633db4d)1313112024, first quarter[263](#d61d529c-cd26-4a1a-9fb7-b0e2390d2e33)5228442024, fourth quarter[264](#2cae8260-89c5-497f-b657-2ebfbd126f93)Over 1002563WordPress Contributor Mentorship Program cohorts, as each recap post counts them





The proposal named two marks of success. First, at least 80% of the first cohort would graduate.[265](#af24a0a6-1a08-4a5c-868c-a58d04de797c) In addition, at least half would keep contributing three months later. The closing post reported the first: 11 of 13 completed.

The fourth quarter recap adds a limit of its own. More than 30 mentees had no assigned mentor.[266](#3394e8af-b3cb-412a-b557-576afbb7d031) It also planned another cohort alongside WordPress 6.8.

A post at the end of 2023 came close to the second mark. It said at least 7 of the 13 kept contributing.[267](#8cc5f1af-559a-41aa-b8f7-e9b874906cbe)

[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

I found no post that measures that at three months. It may sit in Slack or in a document I can’t see.







### What other projects publish

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Joomla:** its January 2026 sprint reported more than 150 people in 14 countries.[268](#4f6711b8-21ef-4b9a-a746-0d1cdae6a651)
- **TYPO3:** one documented cohort ran from September 2020 to February 2021, with six mentees and four mentors.[269](#a38a5d51-10c6-46b3-9652-3e20d757629c)
- **Node.js:** its mentorship repository has been archived since February 26, 2022.[270](#9f83f2b9-882a-4260-816a-a47dc674ddcb)
- **PHP:** its foundation started an onboarding group in August 2026. So far, its scope is new PHP users.[271](#207729de-ea78-49ce-a7ca-0462bd3f2c93)
- **One study:** of 367 Google Summer of Code students, about 15% were still committing a year later.[272](#010d89db-5302-48bd-a113-f811f81be524)







### Work that isn’t code: what the credit systems see

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The evidence is mixed, so here it is in pairs.







- **Drupal’s project lead** wrote in 2021 about what its credit data misses. The list included event organizers, speakers and translators.[273](#54f2577e-9ae4-4205-b124-abf97370d61b)
- **A 2021 study** compared All Contributors lists, which credit work beyond code, with GitHub’s own panel in 2,855 projects. The All Contributors list named more people in 29.5% of them. However, it named fewer people than GitHub’s event data in over 90%.[274](#602eb8ae-5e1b-4ca0-a926-5448429d64ff)
- **The PHP Foundation** says it hires only for the core language. As a result, documentation, websites and translations sit outside its hiring.[275](#d72965a9-5c3e-44e0-a9f5-32c27515ac8c)
- **Drupal’s written policy** credits triage, testing, design and mentoring. Even so, a maintainer still ticks each name.[276](#3565a70f-08f9-4837-8e09-84ac65da48ad)
- **WordPress** hands out some badges automatically for translation, photos and support.[277](#34afacee-b2a1-49d4-9cb0-b4a7f1fc70bb)

### Who measures work beyond core

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Several projects compared here count more than core code. Each counts a different slice.







- **Drupal** moved credit into a separate Contribution Records system in 2025. Its stated reason: many contributions need no code, so credit can’t rely on commits.[278](#aa940a14-c6da-43f5-8635-9b4e20c4ed68) Its credit page also gives an event’s organizer credits, from 220 for a DrupalCon to 25 for a meetup.[279](#18393187-55f5-4c34-8733-afcf62f8ff9e)
- **TYPO3’s** monthly numbers sit documentation and translation next to core patches. July 2026 listed 16 documentation improvers and 6,384 words translated on Crowdin.[280](#a2bfaac8-4c2b-4a0d-be4a-69c128a584dc)
- **PHP’s** credits page names documentation, quality assurance, websites, infrastructure and event maintainers.[281](#08d464a0-31a0-4405-8aad-6ae53946cb4f)
- **Joomla’s** developer site charts who tests fixes and who manages issues, plus documentation wiki activity.[282](#c1842548-994c-46db-834e-91b45f353703)

### Limits: what changed for a first contribution, 2024 to 2026

Disclosure: I was a Training faculty member. I worked with the Sustainability Team on a dashboards project, and a news report quotes me objecting to its closure. I also started and ran GoDaddy’s Five for the Future program until July 2026.

The tables above are a snapshot, and some doors moved. This list comes from a record built around big decisions. Because of that, it leans toward the role that made them.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **April 2024, Marketing.** A post by the Executive Director proposed a Media Corps to get dependable project news to users. It said the Marketing Team would be “temporarily archived.”[283](#fd73b8d9-9e3a-4b03-ae0e-faff393d26ba) Then, in May 2025, a post ended the Media Corps experiment.[284](#ff9eec82-b4a7-4a31-b15c-8a7cfdd4c7cf) The Marketing blog still reads inactive, though it still lists work that’s open to contributors.[285](#fc7a0c25-e1f7-4f49-b0ac-71f2b847c8d5)
- **Summer 2024, Training.** The team retired its Faculty Program to “free up people’s time to focus on higher-impact areas.” The same post said many faculty were no longer active, and some contributors could see the program as a barrier.[286](#10d73b1a-a818-45fe-8b6e-0aedae133f06)
- **January 2025, sponsored hours.** Automattic cited an “imbalance in how contributions to WordPress are distributed” and WP Engine’s lawsuits. It said it would cut its sponsored time to about 45 hours a week, matching other companies’ pledges.[287](#5102f4cf-35b2-4dd6-a528-00358a19f114) In May 2025, it announced a full return.[288](#3ae95ba3-5198-4b34-9142-94f4661533af)







### One closure, and its stated reason

[source-derived](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

**January 2025, Sustainability.** On January 8, 2025,[289](#e59d96e8-7dcd-4e83-9818-358e9f26a966) the project’s cofounder posted in the team’s Slack channel. The message cited “results of the team so far, and the ROI of time invested.”[290](#8f3939de-3c04-472c-b8e5-9fd0e10fa7ba) The same message said it was time to dissolve the team.[291](#00f63765-51b8-48ca-b5f6-43606a40732e) In June 2025, the cofounder added that it “was not a solo decision.”[292](#5185db95-5ad9-4582-b58c-a6e501412c80) Today’s team lists omit it, and its blog carries no closure notice.[293](#16286f4c-d75f-4589-8483-3623390c6522)







### What opened in 2026

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Doors opened too. In January 2026, the project’s goals named onboarding.[294](#5d9d59f1-ecf5-4138-8faf-3f00f0a879a7) By March 2026, the Pathways guides and a contributor dashboard pilot had arrived.[295](#e10c1b46-6e3a-4630-9a1e-1fcbd624cfde) A Good First Issues board followed in April.[296](#dfaa7abc-b0f3-4b39-bb12-3581826abf55)







## 🔑 What a license decides: licenses, names, domains and roles

These tables and rosters back [the post on what an open source license decides, and what it leaves out](https://courtneyr.dev/2026/11/13/open-governance-license/), published November 13, 2026.

### What an open source license decides

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectLicense, as its own file or page states itBackdropGPL version 2 or laterClassicPressGPL version 2 “or (at your option) any later version”DrupalGPL version 2 or laterGhostMITJoomlaGPL version 2 or laterMariaDBGPL version 2; libraries under the new BSD licenseMySQLGPL version 2 plus a commercial license, with an open source exception for client librariesNode.jsMITOpenJS Foundation projectsApache 2.0, Blue Oak 1.0.0, MIT, or BSD with 2 or 3 clauses; anything else needs Board permissionPHPBSD style with 3 clauses, “The PHP Group and Contributors”RubyGemsMIT, or RubyGems’ own conditionsTYPO3GPL version 2 or laterW3C (CSS)W3C Software and Document License, 2023 versionWHATWG (HTML)Creative Commons Attribution 4.0; code under BSD with 3 clausesWordPressGPL version 2 or any later version, “Copyright 2011-2026 by the contributors”xz-utils0BSD for the library and tools; GPL version 2 or later for some scripts; GNU Lesser General Public License 2.1 or later for one bundled partWhat each project’s license file says, fetched 2026-11-13. The World Wide Web Consortium (W3C) and the Web Hypertext Application Technology Working Group (WHATWG) form one standards unit with two rows.





### What the license leaves to open governance

Here are the six WordPress records.

1. 2014: a Training Team call on workshop slides
2. 2022: WebP images by default, reverted before Beta 1
3. 2024: an @WordPress post about the Bay Lights
4. 2024: WP Engine’s access to WordPress.org
5. 2025: a post that said it was deactivating five accounts
6. 2026: a committer told he holds no WordPress.org positions

### The name: the first job of project governance

A license lets anyone copy the code. But a trademark decides who can call that copy by the project’s name, or speak as the project. So the first open governance question is who holds the name. Each project’s answer comes from the series’ legal and intellectual property (IP) matrix.[297](#13381be6-bb0d-4956-9f6e-ec4fd599faf2)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Backdrop:** the Software Freedom Conservancy, which allows “based on” uses.
- **Drupal:** an individual, who grants licenses at “sole discretion.” Plain references get an automatic license.
- **Ghost:** the Ghost Foundation.
- **Joomla:** Open Source Matters.
- **MariaDB:** MariaDB plc owns it, while the MariaDB Foundation holds a license.
- **MySQL:** Oracle, which can revoke its logo license “in its sole discretion.”
- **OpenJS Foundation:** its policy keeps its marks out of product names.
- **TYPO3:** the TYPO3 Association, registered in 7 jurisdictions.
- **WordPress:** the WordPress Foundation. Automattic holds “the exclusive license” for commercial use.







[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **ClassicPress, PHP and xz-utils:** no mark holder found.







### Access: governance outside the license

The GPL lets anyone run WordPress on any server. However, it doesn’t promise anyone the project’s plugin directory, update service or forums. Those live on WordPress.org, and no license clause says who controls a domain. That’s open governance territory. Here’s who each project’s own site pages name, and in what role: domain owner, site operator, copyright holder or website access. Most of these pages say who runs the site, not who registered the domain.[298](#28b18364-4ab2-4b11-8cfd-ad2aedb70109)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **ClassicPress (site operator or copyright holder):** The ClassicPress Initiative, a US nonprofit.
- **Drupal (domain owner):** Dries Buytaert “owns and retains full rights to the domain names,” the Drupal Association’s copyright page says. The Association runs Drupal.org with his permission.
- **Ghost (site operator or copyright holder):** Ghost Foundation Ltd.
- **Joomla (site operator or copyright holder):** Open Source Matters, Inc.
- **MariaDB (site operator or copyright holder):** the MariaDB Foundation.
- **MySQL (site operator or copyright holder):** Oracle, whose terms of use cover mysql.com.
- **Node.js (site operator or copyright holder):** the OpenJS Foundation.
- **PHP (copyright notice):** The PHP Group holds the site’s copyright.
- **RubyGems (site operator or copyright holder):** Ruby Central, Inc.
- **TYPO3 (site operator or copyright holder):** the TYPO3 Association.







[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Backdrop and WHATWG:** no holder named on the pages I checked.







[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **xz-utils (website access, not ownership):** Lasse Collin, its maintainer. “Only I have had access to the main tukaani.org website,” he wrote.[299](#b2317901-4da6-4727-9c5b-b1f8e472206d)
- **WordPress (domain owner):** Matt Mullenweg. “I own the domain name www.WordPress.org individually,” he declared under oath.[300](#20eccccf-19b3-4562-8bd8-5d710b8fd150)







[![Open governance chart: who each project's own pages name for its trademark and its main site, by kind of holder.](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2-1-who-holds-the-keys-chart-v2.png) \[PNG, 205.25 KB\]](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2-1-who-holds-the-keys-chart-v2.png)Two key boards: who holds each project’s name, and who each project’s own site pages name. The stamp marks two holders whose line rests on their own statement. Diagram drawn with Claude at my direction.Text description and data for the key board chart### What this chart shows

- **What it shows:** Two key boards side by side. Each hook is a kind of holder, and each small key on its ring stands for one project. Dashed keys mean no holder was found or named on the pages checked. The “2 on account” stamp marks two holders whose line rests on their own statement, one of them sworn.
- **The name, 12 projects:** a foundation or nonprofit, 6 (Backdrop, Ghost, Joomla, OpenJS Foundation, TYPO3, WordPress). A company, 2 (MariaDB, MySQL). One person, 1 (Drupal). None found, 3 (ClassicPress, PHP, xz-utils).
- **Who the site’s own pages name, 14 projects:** the 13 projects in the domain footnote plus WordPress. A foundation or nonprofit as site operator or copyright holder, 7 (ClassicPress, Ghost, Joomla, MariaDB, Node.js, RubyGems, TYPO3). A company as site operator or copyright holder, 1 (MySQL). One person, 3: Drupal and WordPress by a domain statement (WordPress’s is sworn), and xz-utils by its maintainer’s access statement. A group with no legal entity, by a copyright notice, 1 (PHP). None named, 2 (Backdrop, WHATWG).

### Teams and roles: project governance for people

How each project adds people to trusted roles:[301](#d5d48259-2ae3-44b4-b9a6-593c91204dfb)

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Backdrop:** a unanimous vote of its Project Management Committee.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Drupal:** committers usually need “at least a year” of broad work on core issues.
- **MySQL:** Oracle nominates the first committers. Later, existing committers nominate and approve new ones.
- **Node.js:** a nomination passes when no one objects.
- **PHP:** voting rights (“vote karma”) with no written grant process.
- **W3C:** the W3C Team appoints chairs.
- **WHATWG:** the Steering Group appoints editors.
- **WordPress:** the committer page lists onboarding tasks, but no selection criteria and no removal procedure.







### Appeals: who can say no, and who reviews it

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **OpenJS Foundation:** people involved can appeal within 30 days, but only if the documented process wasn’t followed or the decision didn’t meet the policy. If the Code of Conduct team handled the report, different members of that team hear the appeal.[302](#5ece1fff-9a69-400e-87d2-ea5bec16a527)
- **TYPO3:** members can also call a vote by petition.[303](#91cd0419-762e-4811-9904-c2b0e35da35c)
- **WHATWG:** participants may appeal an Editor’s final response to the Steering Group. Removal, however, is “final and non-appealable.”[304](#fa883b47-e1ae-4974-aa4d-515a8e0f0b26)
- **WordPress:** the Code of Conduct lists four steps: Correction, Warning, Temporary Ban and Permanent Ban. It describes no appeal.[305](#dbfd5e09-254c-44cd-822c-ccedb4f2d0f1) At events, though, either party can appeal an incident decision within 7 days, to a community team rep or to the Executive Director the page names.[306](#86dd883a-2f2d-4417-b044-dedec7f2299d) Five named lead developers hold final technical authority.[307](#bcab8d58-8c35-4750-a8e8-a901e8b6465f)







## 🗳️ Decision making: votes, blocks and final says

These tables back [the post on how open source projects make decisions](https://courtneyr.dev/2026/11/16/open-source-decision-making/), published November 16, 2026.

> \[!note\] Disclosure I work at Pantheon, a WordPress and Drupal host. At GoDaddy, I started and ran its Five for the Future program until July 2026. Separately, I chose which groups GoDaddy funded: the PHP Foundation, OpenJS, W3C, PHP\_CodeSniffer and The WPOCC. Some appear in this table.

### Project decision rules: 16 rule sets from 15 projects and standards bodies (Drupal has two)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectDecision coveredWhat settles itWho settles itBackdrop CMSCommittee business, members and philosophyA committee voteA six member committee; an elected member breaks ties[308](#edd707c8-ebc8-4c5a-b968-aae25ba379a6)ClassicPressProject directionA final sayThree directors, who “make decisions as allowed”[309](#0e27b61c-b7e4-48d8-9e3e-f4c5cedbbc2e)Drupal AssociationAt-Large board seatsA vote, then board ratificationMembers elect At-Large seatsDrupal coreCode and core policyConsensusCommitters; the Project Lead breaks tiesGhostThe product roadmapA final sayThe staff core teamJoomla (Open Source Matters)Board elections and bylawsA voteMembers in three classes: officers and coordinators, team leaders, team membersMariaDB ServerCode and governance changesA council vote with a rationed vetoThe Maintainer Council; the Foundation CEO breaks tiesMySQLCode changes and strategyA final sayOracle as project lead; the core project lead “makes the final decision”Node.jsLanding a pull requestConsensusAny collaborator can block; the Technical Steering Committee overrides by voteOpenJS Cross Project CouncilCouncil businessLazy consensusTwo thirds of all voting members can overrule an objectionPHPLanguage changes by RFCA voteCode contributors with php.net accounts, plus chosen community representativesTYPO3 AssociationGeneral Assembly businessA voteMembers, one vote eachW3CSpecifications and Formal ObjectionsConsensus, then a councilAnyone may object; a council decidesWHATWGStandards changes and editorsImplementer support, then a final sayTwo browser makers must support a change; a steering group decidesWordPressCode, WordPress.org and communityA final say by named rolesA core leadership team; five lead developers on technical decisionsxz-utilsCode and releasesA final sayOne lead maintainer, with no governance fileWhat settles a disagreement, read 2026-11-13. MySQL and Backdrop rows came through a summarizing tool, so they’re source-derived.





### Open source voting: who counts, and what counts as a yes

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectWho votesWhat passesMinimum turnoutDrupal AssociationMembers, including a free membershipMost approvals wins the At-Large seat; the board ratifiesNone writtenJoomla (Open Source Matters)Members: officers, coordinators, team leaders and team membersA majority of votes cast; bylaw changes need two thirds of all membersA majority of members presentPHPCode contributors with php.net accounts, plus chosen community representativesYes at least twice No; abstentions don’t countNone writtenTYPO3 AssociationMembers, with three proxies at mostA simple majority; bylaw changes need two thirdsNone written; any properly called assembly decidesWordPressTeam reps are elected by poll, open about two weeksNo product or technical decision goes to a countNone writtenVote rules as written, read 2026-11-13. Of the four that hold broad votes (the Drupal Association, Joomla, PHP and TYPO3), only Joomla writes a minimum turnout.





For example, [PHP’s voting rules](https://wiki.php.net/rfc/voting) set a two thirds bar, and recent results show it working.[310](#d0449a8f-6ce8-4d7f-9e79-d3d14cb3583b)

- **PHP:** the Pipe Assignment Operator drew 14 yes, 12 no and 7 abstain in August 2026. It failed, because 14 isn’t twice 12.[311](#9443827c-4475-4255-a421-28b4f3ee24af) Somewhere, a math teacher smiles.
- **Joomla:** 63 of 84 eligible members voted for president in 2026.[312](#439b72e0-e3aa-49f6-bf4d-f2f1f0477bd4)
- **Drupal Association:** 307 of 1,274 eligible voters cast ballots in 2026, down from 528 of 1,459 in 2025.[313](#89d67e61-7578-4a3b-90d0-46e551845fc8)

### Who shows up to vote

[![Open source decision making turnout chart: Joomla 75 percent, Drupal Association 36 then 24, TYPO3 24 percent of eligible voters.](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.2-v04-who-shows-up-to-vote-v2.png) \[PNG, 186.39 KB\]](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.2-v04-who-shows-up-to-vote-v2.png)Turnout from each page’s own counts, so the table below names every vote. Chart drawn with Claude at my direction.[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

VoteEligibleVotedShareJoomla president, 2026846375%Drupal Association At-Large, 20251,45952836%Drupal Association At-Large, 20261,27430724%TYPO3 bylaws, online, October 20261,12127224%Turnout as a share of eligible voters. Counts are as published, except TYPO3’s electorate, which I computed. Electorates differ in kind.





TYPO3 note: 204 yes, 66 no, 2 blank; 849 eligible votes uncast.

### TYPO3: one term limit failed in April, another passed in October

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **What happened:** in April 2026, a member petition asked for a limit of two terms on the Board. It got 22 votes for and 44 against, so it failed.[314](#1b912df2-c76f-46e0-b661-28632bb753be) Then, in October, members voted online on a broader bylaw package. This time it passed 204 to 66, while 849 members didn’t vote.[315](#850b3af4-8735-496a-acdc-a9f2d3496ccc)
- **Stated reasons:** the petitioner wrote that the board “needs to be more diverse and also needs fresh faces.” However, the Board recommended rejection, citing “incomplete text, unresolved retroactivity” and more. Instead, it offered milder options, including “a cap of three instead of two consecutive terms.”[316](#189f5f04-a715-4e46-94eb-eb77e9bf6f0e) Later, its September protocol proposed nine year limits and gave no reason there.[317](#3515f5b4-0b3f-44d2-9f3c-d13e5b084c1b)
- **What decided it:** members, by vote, both times. The new bylaws let Board members be reelected twice, then require a break of at least a year.[318](#34fff9a2-0ab9-4106-ac28-932f1223a08b) In fact, that’s close to the Board’s April alternative.
- **What cuts the other way:** the October Assembly took note of the online result. The Association says a legal opinion made the online vote binding, but I found no link to the full opinion.[319](#c3873b89-d319-4277-a0d0-1d401a49fb9d)







[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Also, the 204 yes votes are 18 percent of 1,121 eligible members. So a rule can change with most members silent.







### Consensus: how open source projects decide when nobody counts

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Node.js:** a change needs two approvals, or one after seven days. One collaborator’s objection blocks it until consensus or a committee vote.[320](#cc887978-c9e7-413e-8273-566ac486cc60)
- **OpenJS Cross Project Council:** “silence indicates consent,” but objections must be resolved.[321](#39907b80-f564-4818-9aa7-161b4aea16ae)
- **W3C:** consensus means wide support with “no sustained objection from anybody in the set.”[322](#5f0e0777-63cf-486b-bb6c-900d69c9e318)
- **WHATWG:** a change needs support from “at least two implementers.” Since an edit on 2026-11-09, a positive standards position counts as support.[323](#e4c9bb59-8355-43ee-a02a-12660fa46d46)
- **Drupal core:** committers “use consensus decision-making,” and unresolved questions then go to the Project Lead.[324](#c0640469-42c3-4409-9f6e-41a5d7c34fdb)
- **WordPress:** release candidates need “a double signoff by two different committers,” and “Every decision needs to be clearly made in public.”[325](#f4e9abee-c775-4338-8d35-42c2789e0509)







### Who can block a change in open source decision making

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectWho can blockHow the block endsApache (reference)A binding no on a code change, which needs a technical justification: “A veto without a justification is invalid and has no weight”[326](#c367c345-cb42-4957-8f67-63c184f44fce)With a justification, it “cannot be overruled nor overridden by anyone” and stands until the voter withdraws itBackdrop CMSAny committee member, on decisions that need unanimityNo written way outDrupal coreNo individual veto is writtenThe Project Lead “may proactively make or override these decisions”MariaDB ServerEach council member, once every three yearsA two thirds vote overridesNode.jsAny collaborator, with a reasonConsensus, a committee vote, or dismissal after seven silent daysOpenJS Cross Project CouncilAny objectorTwo thirds of all voting membersPHPNo vetoA no from more than a third of yes and no votes defeats a proposalW3CNo single block; anyone may file a Formal ObjectionA council decidesWHATWGImplementers, by declining to implementThe steering group can overrule an editorWordPressNo written objection rightThe release lead makes “big final decisions on feature readiness”Who can block a change, and how a block ends, read 2026-11-13; the Apache row was reread 2026-11-20. Apache, though, is a reference row from outside the comparison set.





[Who decides the open source stack under WordPress](https://courtneyr.dev/2026/11/10/open-source-stack/) also walks through Apache’s veto. Meanwhile, W3C publishes how its objection councils end.[327](#4de4b830-838c-41ee-9d0f-0b43e6e452ab)

### How W3C objection councils end

- **Count:** the index lists ten completed formal cases from August 2023 to June 2026.
- **Outcomes:** five overruled the objection, one upheld it, three ended by a unanimous short circuit among council members, and one went to the CEO.
- **Newest:** a Digital Credentials council overruled its objection in June 2026.

### A final say: one person, one company or one small group

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Drupal core:** the Project Lead “acts as a tie-breaker when needed” and approves changes to governance. However, a footnote on the same page adds that the Project Lead “may proactively make or override these decisions.”[328](#922f705f-497d-472d-8c0b-b81574a4b2ea)
- **Ghost:** staff decide, while feature votes are “not a democratic system.” Ghost keeps its roadmap private, because sharing it “turned out to be more distracting than helpful.”[329](#ad36fa0a-a5af-4190-8bbe-9e51c77de2f6)
- **MySQL:** Oracle nominated the first committers and project leads, and “Oracle is the project lead.”[330](#c87fa287-d409-49b3-8e1b-5bdb4c8e20ee)
- **WHATWG:** a steering group of browser makers has “final say in all matters.”[331](#7eaa6fd2-9e9d-4d92-ac60-edb5b83f3bdc)
- **WordPress:** the Core Handbook says a core leadership team “governs all aspects of the project,” led by Matt Mullenweg. Five lead developers also “have final authority on technical decisions.” But the page sets no term, election or removal rule.[332](#1ea88217-ddd8-4d4b-ae83-b38b47f0eb07)
- **xz-utils:** one lead maintainer, but no governance file.[333](#cbd5c918-b90b-4e83-8497-5b96c8ff5814)







### Open source decision making inside teams

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Of 26 team sites I checked, three publish a clear way to settle a contested decision: Core, CLI and Openverse. Sustainability, though, covers only minor changes. The rest describe approvals, elections or venues instead, with no tiebreaker.[334](#1ad7e40a-b72d-44ea-b55f-30978a7a599c) Two offer appeals for single rulings: theme suspensions go to the executive director or project lead, and conduct cases to a community team rep.[335](#5f284a18-d6e1-4d3e-8f3e-14a4ecb7dc25)[336](#9f6f4096-fbee-408a-871c-03eeedb76bdd) No page I read sets an appeal, or any procedure, for a change made from above.







### Nine times a team’s decision didn’t stand

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

From 2018 to 2026, the project lead or the executive director set aside a team’s decision or process nine times. The count uses one definition: “a decision or process a team had adopted, set aside by the project lead or the executive director.” Recent cases are easier to find, so this isn’t a trend line. Seven came in 2024 or later. Six rest on public pages, while three rest on Slack messages, which need a WordPress.org account to read.[337](#7c8909f2-00fb-4e88-a657-d2180b711f36)







> \[!note\] Disclosure I’m a former Training Team rep and Faculty member. In 2024 I wrote Sustainability Team posts, and I objected to its closure. My work sits alongside the Accessibility Team.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

When and teamStated reasonWhat changedDec 2018, Core committers“I would not recreate the old deliberation process”[338](#bcdba816-0dfe-4527-b333-4e91b3b32c67)Project lead alone approves commit accessSep 2022, PerformanceThe default was “a lot for right now”[339](#7ba5d523-c165-40d9-b408-ca74f09ff464)WebP by default came out of 6.1Mar 2024, Marketing“not requests that I am able to fulfill”[340](#dc912075-e435-44dc-a92d-b030504fb7ea)Scope changed; then an archive plan in AprilJan 2025, Sustainability“a good time to officially dissolve the team entirely”[341](#4afddaa6-532a-413d-b28b-772286b5bc06)Team dissolved and delistedApr to May 2026, Core committers“have changed my mind and we’re doing this”[342](#85b3bfaa-1239-485f-b2ff-fb685a7da2b4)Akismet restored, although committers backed a revertApr 2026, Themes and Accessibility“Somehow the #accessibility team put this requirement in?”[343](#504c5d64-026b-4f48-aae6-17945e2a4200)Link underline rule droppedApr 2026, Meta“move quickly, embrace experimentation”[344](#36dd55a9-d703-4b02-bfe7-d87597d5c3f2)Janitors change WordPress.org without team approvalMay 2026, Core“a stable and reliable WordPress 7.0 release”[345](#ae5fe9ea-6ada-4c0c-bb9a-89e53b81eb0e)Real-time collaboration pulled from 7.0Aug 2026, Accessibility“The team has overstepped its authority, usefulness, and charter.”[346](#3a17378f-8e60-4333-9fbc-a6b9f361850c) A 2026-08-17 reply added “missing your own set goals and deadlines”[347](#29c01089-8219-4513-b57d-5dff21f05882)“Permanently delayed.” In October, the team made its accessibility-ready tag conditional; its post doesn’t mention Matt’s comment[348](#14f5fbb1-a0b1-4d41-b85f-8a51fc0be8e3)Team decisions changed from above, read 2026-11-14. Every row is verified except May 2026, which is source-derived.





[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Each was announced by post, ticket comment, handbook edit or Slack message. However, no page I read sets a procedure for these changes.







### Where other projects write the undo button

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Other projects, however, write down the lever above a team.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Project: who sits above the teamThe written leverPython: Steering CouncilRecall a delegate, which “will overrule any prior acceptance or rejection”[349](#7d070cd3-a577-4499-a1e9-8deefced8c1b); the proposal goes back to draftNode.js: Technical Steering Committee (TSC)“The only recourse” is to “revoke the entire charter”[350](#eb643b39-1994-47ef-a873-315f95fc3455)Apache (reference): BoardEnd a project committee “by resolution”[351](#b3d88489-262c-49ee-9e95-9d4e8ccb8ff7)Drupal: Review panel (conduct); Project Lead (core)Panel overrides on appeal[352](#f9de5ff2-7197-43e0-911c-88e001d97590); Lead may override core decisions[353](#32d8eab7-096e-450c-a423-45ceaf435ab4)W3C: A council per caseAffirm or overturn on appeal[354](#f1a0a683-102b-470f-aacf-cc9be2423f9f)WordPress: Project lead; executive directorFinal say written, but no override procedureWho can undo a team’s decision, read 2026-11-14.





### Ties and deadlocks in open source decision making

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **A named person or office:** Drupal’s Project Lead, and MySQL’s core project lead, who “makes the final decision.” Also, TYPO3’s chair on business items, with lots drawn in tied elections, and the W3C council chair.[355](#25439398-6590-4842-a732-248fab0cd43a)[356](#bfaddfb9-aea4-420a-b67b-bff1b53e62db)[357](#e017bb41-0b3f-4fb1-8ad2-68ed1125daed)[358](#f5b33bb0-75af-413d-a8ac-3d0419d84275)
- **Someone outside the deciding body:** MariaDB’s Foundation CEO, “who must not be a member of the Council.”[359](#e715a360-935d-4255-ad45-0dd684f86d82)
- **Another vote:** the Node.js committee votes, a tied PHP vote fails, and OpenJS overrules by two thirds.[360](#2c599216-8651-4114-a45c-0444badefa66)[361](#c2ae9cac-47f6-4b1c-9427-f64277753ce7)[362](#2475bffd-5ea4-413c-b77d-b04e00c91837)
- **Nothing written:** Ghost and xz-utils. In WordPress, meanwhile, Core Tech Lead cases “are usually escalated to project leadership,” a term the page doesn’t define.[363](#da3c8103-701c-4772-aded-3ed822640c6e)







[source-derived](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ClassicPress shows the last kind in action. A 2022 poll split 20 to 18, but no written rule said who would decide.[364](#923d078b-dee4-4d86-8890-730d5615ec97)[365](#7df8ed6b-5bd6-44ef-9702-1c2f6dfa9581)







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

On the other hand, PHP voters declined a Technical Committee 10 to 21 in 2023.[366](#39e5ba3a-beaf-45dc-bcb5-51f56c012787) So a project can choose to have no tie breaker.







### Who changes the project decision rules

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The voters:** PHP voters set their own rules by the same two thirds vote. TYPO3 and Joomla members also amend their bylaws by two thirds.[367](#7e364a2d-232a-4417-8de1-0b69681f41cd)[368](#ad009bbd-3d30-4d24-aa52-75c4ec659cb7)[369](#5846ccb5-0106-4dc5-a302-64f189355019)
- **A board or council:** the Drupal Association board, by two thirds of directors present, and MariaDB’s council, by two thirds.[370](#6b854d70-1bc1-4040-9a39-cbcaa25d5034)[371](#82917e41-4e7f-49f3-838d-e8874ea5f06f)
- **A second body:** Node.js changes its committee charter only with approval from the OpenJS council. W3C’s Advisory Board drafts process changes for a member review of at least 28 days.[372](#fa8f5136-d294-4af9-8cca-1a692cba527f)[373](#282c7bf5-a85a-4736-9e0e-76c6c70fd6e0)
- **No written path:** Backdrop’s leadership rules, ClassicPress, Ghost, xz-utils and WordPress, whose organization and release team pages state no amendment step.[374](#77870a6b-8c5f-4698-ab0f-56054b2b7434)[375](#538ac397-5fb1-420f-990d-08ecbf744bce)







### Records you can check: how open source projects decide in public

Check it yourself: for example, open any PHP RFC page. The vote table then lists each voter’s username next to yes, no or abstain. For example, End PEAR Endorsement passed 40 to 0.[376](#c58ece2b-2414-4eb2-8e29-f896210fd445)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Named votes:** PHP’s completed RFC votes list each voter’s username and choice.
- **Named approvals:** Node.js pull requests and their reviewer lines.[377](#0e21a2fc-95f2-475c-8b00-da7638a576ee)
- **Positions in public issues:** WHATWG steering group decisions.[378](#9a2629c7-e80a-4ac4-ba4e-63b848e76f48)
- **Names without positions:** W3C council reports name who took part but “must not attribute any position to any individual.”[379](#37c23a09-b4d9-4472-9911-a45b9afda196)
- **Counts without names:** TYPO3 protocols, Joomla’s motions registry and Drupal Association totals.
- **Who asked:** a 2026-11-13 Make WordPress Core post says a new theme became the flagship “at @matt’s request.”[380](#1db2f3ed-ada6-4158-a294-0b61c6201a24)







[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **A decision log:** the WordPress 7.1 release lead published one “to publicly document some of the various decisions.”[381](#145812e7-6c42-44d7-899a-f83f22d3b695) It’s one person’s account, not an official record.







## 🍴 Forks: what seven forks kept and rebuilt

This table and its lists back [the post on what an open source fork can keep](https://courtneyr.dev/2026/11/17/open-source-fork/), published November 17, 2026.

### Seven forks, one packing list

Here’s what each open source fork packed, at the split and by its first release. Read across a row for one fork, or down a column for one asset.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ForkSplitCode and history at the splitName and domain at the splitUpdates by first releaseWho could relicense laterBackdrop2013Kept, with historyNewPre-release code pointed at Drupal’s server; switched to updates.backdropcms.org on 2014-12-21, a month before 1.0, while the new server still reported “not implemented”[382](#ac9421fe-361b-4610-ad4a-470ca637ade6)No single holder; authors keep copyrightClassicPress2018Kept, with historyNewCommittee decided on 2018-09-07 that “WordPress endpoints will be used for plugin checks”; the minutes call an initial permission review “positive” and record no final result. Plugin and theme checks still go to api.wordpress.org (update.php, lines 381 and 657)[383](#d72acb1e-63a3-4d88-a553-b13e14656bc4)[384](#d1380b3a-081b-469f-8c19-26a0f823688e)No single holder; authors keep copyrightio.js2014Kept, with historyNewOwn downloads at 1.0 (2015)No single holder; MIT notices keptJoomla2005Code kept; public history starts at the split (2005-09-15)NewOwn downloads and project forge at 1.0 (2005)Miro, then the Mambo Foundation, for Mambo’s codeMariaDB2009Kept, with historyNewOwn releases from the first beta (2009)Oracle, for MySQL, as copyright owner and through its contributor agreementOpenTofu2023Kept, with historyNewOwn registry at 1.6.0 (2024); HashiCorp provider names keptHashiCorp, for Terraform, through contributor permissionValkey2024Kept, with historyNewOwn releases and images at 7.2.5 (2024)Redis Inc, for Redis; older code stays BSDWhat seven open source forks kept and rebuilt, at the split and by their first release. Seven forks, as of 2026-11-14. Sources in the footnotes.





### What every open source fork took: code and history

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Every fork started from the original’s code. Six of them carry the original’s history, so the authors’ names travel with the code. Only Joomla’s public repository starts at the split.







- **Backdrop:** more than 19,000 commits from before the fork, with Drupal history back to 2000.[385](#ca83e3e2-9caa-41f5-a86b-2c0b35f0956b)
- **ClassicPress:** WordPress history back to the repository’s start on 2003-04-01.[386](#c99cec76-8dae-4ca5-b0e8-caaf8fa56533)
- **io.js:** its 1.0.0 README said it “began as a GitHub fork of joyent/node.”[387](#665f223e-e091-4de5-8e30-39f93bd14cd6)
- **Joomla:** version 1.0 was Mambo 4.5.2.3, “given it a spring clean and named it Joomla! 1.0.”[388](#614b7869-77ac-4c0b-acde-e540ece56238) Its public repository starts at the split. The oldest commit, “Initial import into SCM,” is dated 2005-09-15.[389](#e148a80a-b953-492e-9918-c17c95280079)
- **MariaDB:** its first beta, on 2009-10-29, was “based on MySQL 5.1.38”.[390](#da81095c-bfe0-4389-a149-9f3b134bbf08)
- **OpenTofu:** its repository’s oldest commit is dated 2014-05-21. It holds 31,551 commits across all branches from before 2023-08-25.[391](#baacb678-7289-43d7-9edc-1163d2bbac8e)
- **Valkey:** its repository’s oldest commit is dated 2009-03-22. It holds 18,643 commits across all branches from before 2024-03-28.[392](#4fc8e636-9429-4179-98fc-4151ff0cb24e)

### What no fork took: the name, the mark and the domain

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Drupal:** its policy names a Drupal fork called “ImprovedDrupal” as a use that doesn’t qualify for its automatic license.[393](#1cbed506-cefc-4a9b-ab7a-4aa98c02829c)
- **MySQL:** Oracle’s guidelines bar its marks from the name of an open source distribution without permission.[394](#5ac80f89-4884-408a-9d8e-11e8fc67769b)
- **Redis:** its current policy lets a fork say it’s “based on a fork of Redis® Open Source version XX.”[395](#a8f1f7c5-bae6-4cad-aebb-86a0bcf1eb49) However, calling some products “Redis compatible” needs a commercial agreement, under conditions the policy lists.
- **WordPress:** the Foundation’s policy aims to stop anyone who would “unfairly profit from, trick or confuse people.”[396](#97bfb186-321a-47d0-805e-469597842d3b) It also asks people not to put WordPress in a domain name.







### Forks build their names early

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

So forks build their names early. MariaDB registered mariadb.org on 2009-03-04, about eight months before its first beta.[397](#d875ea22-84de-42b7-a879-f104d7beb131) Backdrop’s trademark claims first use on 2013-08-15, a month before the announcement.[398](#1ccab7b0-b740-454a-b703-590f1d765731) At first, the registration went to one founder. Software Freedom Conservancy holds it today, through an assignment signed in 2021.







A new name doesn’t guarantee a new kind of holder, though. A company owns the MariaDB mark, and the MariaDB Foundation uses its own name and listed marks under a license from that company.[399](#2c319909-55f1-4fe6-810b-26da1be11134)

### The update channel a fork can’t pack

Disclosure: I’m an active member of the Technical Steering Committee of the FAIR Package Manager, which also distributes packages.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Backdrop:** on the day of the announcement, its code still asked `updates.drupal.org`.[400](#cc6c36fe-2e6e-42bb-bc50-df44af9fd577) A commit on 2014-12-21 switched it to `updates.backdropcms.org`, a month before 1.0.[401](#47d9960a-46ea-4a6b-be3b-a53ed8c93e2a) That’s `git blame` at its purest: one line, two commits, about 15 months apart.
- **ClassicPress:** in 2018, its committee decided to use WordPress endpoints for plugin checks. The minutes call an initial permission review “positive” and record no final result.[402](#ff212e26-ac4e-49c2-b331-f4490ae38fba) Version 1.0 then sent update notices from its own servers, with downloads hosted on GitHub.[403](#f82b0d8d-43fb-4af2-88f1-174ae2f6aba5) Today its code still sends plugin and theme checks to `api.wordpress.org`.[404](#d048a7ca-982d-4814-abc7-92ab36ff53dd)
- **io.js:** it shipped the npm client and promised releases “compatible with the npm ecosystem.”[405](#550d1e5c-00ba-469b-a3c2-77e65abfa0a1)
- **OpenTofu:** it built `registry.opentofu.org` and kept short provider names like `hashicorp/aws`.[406](#e3795e09-6759-4f03-af67-6eb92313d762) Its FAQ also says plainly: “OpenTofu will not have its own providers.” Its stated reason: “Terraform providers have not altered their licenses, and the potential for such a change is virtually zero.”[407](#23a05360-8d0d-4cf7-8fab-e4542f297891)
- **RubyGems:** former maintainers launched gem.coop, a gem server and mirror. But the rubygems.org registry stayed with Ruby Central.[408](#e4d12647-35f5-478f-9f21-5b29d3160415)







### Who can change the license after the fork

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **MySQL:** Oracle’s rule reads “Without a submitted and approved OCA, Oracle cannot integrate your contribution”.[409](#4805ac61-bf5e-41c3-acf6-e8fa69b7643d) (OCA is the Oracle Contributor Agreement.) Earlier, its 2010 version gave Oracle joint ownership of each contribution.[410](#e3505e68-e58b-4da7-b687-d04fa3dafd7b)
- **Terraform:** HashiCorp’s agreement takes a broad license, and contributors keep ownership: “You reserve all right, title, and interest in and to Your Contributions”.[411](#b4b46b02-2b8b-4c6b-ae8d-6d5fcd8c7bb7) In 2023, HashiCorp moved future product releases to the Business Source License. However, APIs, SDKs and most libraries stayed on the Mozilla license.[412](#c237b8da-97b0-40b7-ae9c-f6c7d3e711bc)
- **Redis:** Redis Inc moved Redis 7.4 to two source available licenses in 2024.[413](#444b1609-da5a-400f-b823-1bee9d78d645) Later, in May 2025, it added the AGPLv3, starting with Redis 8.[414](#20727b60-18ba-4622-8293-54dc04e6a4a0) Its contributions file says code from before 7.4 stays available under the BSD license.[415](#5ec6d780-6ed2-4d00-82c5-8fc814704ba6)
- **Backdrop:** an early README says the code is “Copyright 2001 – 2013 by the original authors”.[416](#b9beb5da-7987-49d4-9e9c-0e30ac064032)
- **ClassicPress:** GPL version 2 or later, with the WordPress contributors’ notice kept.[417](#a7e887ac-de9f-4f32-9747-b363d84cc37f)
- **WordPress:** `license.txt` reads “Copyright 2011-2026 by the contributors”.[418](#40caa158-aad8-42f5-9ef1-1a30853b2039)







## 🪑 Board seats: what payment can reach

This chart, table and set of rosters back [the post on how many open source board seats sponsorship can buy](https://courtneyr.dev/2026/11/18/open-source-board-seats/), published November 18, 2026.

### Board seats by organization, A to Z

[![Open source board seats tied to payment: PHP 6 of 10, OpenJS 4 of 8, MariaDB unknown, six others 0.](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.4-v01-what-money-can-reach.png) \[PNG, 255.08 KB\]](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.4-v01-what-money-can-reach.png)Seats tied to payment as a share of each listed board, from each organization’s own pages. The table below names every source. Chart drawn with Claude at my direction.Text description and data for the board seats chart#### What this chart shows

- **What it shows:** One bar per organization on one axis, from 0 to 100 percent of the board as its own page lists it. A solid bar is seats tied to payment today. A dashed bar is seats whose link to payment is unknown or missing from the page’s labels. A diamond marks the most seats a paying tier can fill by written rule, and an arrow means no ceiling.
- **Seats tied to payment:** PHP Foundation, 6 of 10, and the rules allow 7. OpenJS Foundation, 4 of 8, or 5 counting the Chair’s 2025 Silver seat, with one director per Platinum member and no ceiling. MariaDB Foundation lists 5 of 9 as company representatives, and whether payment placed them is unknown.
- **No seats tied to payment:** Drupal Association 0 of 11, Joomla 0 of 7, MySQL 0 of 7, TYPO3 Association 0 of 6, W3C 0 of 11 by tier, and WordPress Foundation 0 of 3 as of the 2024 tax year.

OrganizationWhat money buysMost seats a paying tier can fill, by written ruleSeats tied to payment todayDrupal AssociationA logo00 of 11 directors listed, plus one adviser; the page predates the 2026 electionJoomla (Open Source Matters)A logo00 of 7MariaDB FoundationPool entries0 reserved; how an entry becomes a seat is unknown5 of 9 listed as company representatives; whether payment placed them is unknownMySQL (Oracle)Nothing for sale; ownership holds the seats00 of 7 listedOpenJS FoundationSeats by ruleNo ceiling: one director per Platinum member4 of 8 by the page’s labels; 5 counting the Chair’s 2025 Silver seatPHP FoundationSeats by rule7 of 106 of 10TYPO3 AssociationOne vote per member00 of 6W3COne vote per member0 by tier0 by tier; 7 of 11 elected by dues paying Members, one vote eachWordPress FoundationA logo0 of 30 of 3, as of the 2024 tax yearOpen source board seats that payment can reach at nine organizations, A to Z. A seat counts as tied to payment only when a paying tier selects, elects or nominates it. The denominator is each listed board. Pages read 2026-11-15; sources in the footnotes.[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

At GoDaddy, I started and ran its Five for the Future program until July 2026. Separately, I chose which groups GoDaddy funded: the PHP Foundation, OpenJS, W3C, PHP\_CodeSniffer and The WPOCC. Today, GoDaddy.com is listed as a Gold sponsor of the PHP Foundation. GoDaddy is also a Silver member of OpenJS.[419](#c5a4184f-ff25-4065-967d-70497d147ee8)[420](#e2431720-f3c7-474a-9e87-edc3204fbe93)







### PHP Foundation: up to 7 of 10 seats

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** First, the [PHP Foundation governance page](https://thephp.foundation/governance/) sets a board of 5 to 10 people. Platinum sponsors then get up to 3 seats, “automatically granted to qualified Platinum sponsors.”[421](#65f4bd49-9e06-4fb7-8601-9b01c6ea71d3) Other sponsors get the remaining seats, “not to exceed 4.” Meanwhile, community representatives get at least 3.







[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The count.** Today, the board page lists 10 directors.[422](#d806ebfb-a53f-45a4-a6a1-9852a37632cc) According to the Foundation’s own posts, Automattic and JetBrains hold the 2 Platinum seats.[423](#7802d0fa-48ac-4745-aa70-b329a6afc75e)[424](#8269f762-e97f-4798-a452-8fbb7c796ced) Four more directors work at companies on the Silver sponsor list.[425](#b13cba9f-bd18-416c-92c1-ae1cd2aeb243) So 6 of the 10 open source board seats tie to payment today. The rule, however, allows 7.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **What holds the rest.** Strategic matters need a “2/3 majority of total board.” In addition, every director is “Nominated by an existing Board member” and voted in each year.[426](#fc658edb-c473-4450-a3d7-e8b82c301e37) On a board of 10, two thirds means 7 votes. So the 4 community directors, voting together, could block. Swap one community seat for a sponsor seat, though, and they couldn’t. Board size has its own exit, too. After 4 failed votes at least 4 weeks apart, a simple majority can decide it.[427](#f891f8c3-a5b2-498b-98cf-4528c5b60b89)
- **The promise.** “Sponsorship does not imply governance rights.” That sentence, however, sits in the Code of Conduct.[428](#4d0ba7c7-c9e1-4c80-ab70-e49411922c03) The governance page, which reserves the seats, doesn’t repeat it.







### OpenJS: one director per Platinum member, no ceiling

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** Each Platinum member appoints its own director. It can also remove that director “at any time, and for any reason, or for no reason.”[429](#7345dc1f-6a2b-4bfc-9096-a26306f61fb5) Gold and Silver members, by contrast, elect directors by formula. Still, no clause caps the Platinum count.







[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The count.** The governance page lists 8 seats.[430](#108a4c00-566e-47e8-b358-4d48686bf3a4) Member tiers fill four: Platinum, Gold and Silver directors, plus an End User director those tiers elect together.[431](#a32fec04-140d-494c-88a7-20597e0f11c0) Three more are Cross Project Council (CPC) seats. The page gives the Chair, from GitHub, no class. However, the 2025 board post called the same person a Silver director.[432](#b592d1c6-14ed-4804-8026-75d43582840b) So member tiers fill 4 of 8 seats by the page’s labels, or 5 counting that seat.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **What holds the rest.** First, CPC seats can’t exceed 80 percent of the Platinum, Gold and Silver director seats. Second, CPC participation “shall not be limited to Members.” Finally, a two thirds vote guards listed matters, including removing the Platinum appointment right.[433](#871f73a6-8d4d-4e98-87d6-95b4510029a4) If all 8 directors vote, that means 6 votes, so the 3 CPC seats could block it together.
- **The promise.** The Join page says neutrality “ensures that no one company controls an important open source technology.”[434](#8d8fcd06-300b-4b93-9840-0109e5989fdc) However, that line sits beside the prices, not in the bylaws.







### MariaDB: pool entries the bylaws don’t mention

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** The sponsor page sells governance access by tier. For example, Gold at EUR 50,000 buys “Representation as an observer at meetings of the MariaDB Foundation Board.” Platinum at EUR 100,000 buys “One entry into the selection pool.” Diamond at EUR 500,000 then buys two entries.[435](#307c91e0-37b2-4823-a285-b3f9681ae8b5) The bylaws, however, never mention a selection pool. Instead, directors elect directors.[436](#8c7351bf-6fdd-4ca6-9f74-2fe924893920)
- **The count.** Next, the About page lists 9 directors. It files 5 under “Directors representing organisational board members”: Amazon Web Services, DBS, MariaDB, Nextcloud and Virtuozzo.[437](#40c689f4-8620-4201-a7f7-a9808c66a9e5) So company labels cover 5 of these 9 open source board seats. Still, the pages don’t say whether payment placed any of them.
- **What holds the rest.** No single election may raise one sponsor’s share of directors above 25 percent. Also, “An Observer may not vote in any meeting of the Board.”[438](#62c768b1-5514-4aad-bd24-2345d6a868ca) But no clause caps sponsors as a group.
- **The promise.** Finally, the sponsor page says sponsorship “does not guarantee the acceptance of code, control over technical decisions or preferential treatment.”[439](#409d1d7a-e5a0-4434-962a-78309c296856) That covers code and technical processes, though, not seats.







[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Meanwhile, how a pool entry becomes a seat isn’t written anywhere I found. Of course, unknown isn’t the same as absent.







### One vote at every price: W3C and TYPO3

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** First, W3C’s bylaws give each Member in good standing one vote. Good standing, in turn, requires paid dues.[440](#0b42a2c7-8394-457d-a87e-7e23ae5da59d) Members then elect 7 Consortium Directors.
- **The count.** In the US, dues run from USD 2,250 to USD 77,000 a year, set by a member’s size and type.[441](#4958de00-4a32-4f0e-95d1-cd5cb6567797) Meanwhile, the board page lists 11 directors, and 7 are Member elected.[442](#64d4bcef-36c9-4f22-8b99-637ed2b65c4f) So no seat goes to a tier.
- **What holds the rest.** The page lists 3 directors chosen by Partner Members. It also marks one director as Board elected, then says there are none right now.[443](#5cf0d990-978a-482f-a0ff-1ab4db140d90) (One page, two answers.)
- **The promise.** The Process Document says “no Member receives preferential treatment within W3C.”[444](#2ec5fa89-d48e-4cb5-a612-cefffeb27255) Still, it covers Members, not sponsors, and the seat rules live in the bylaws.







[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

In other words, W3C’s top fee is about 34 times its lowest, for the same single vote.







### TYPO3: one vote, and no seat on the board

TYPO3, likewise, runs the same model with a different menu.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** The membership page puts it plainly: “While all members have one vote each, higher membership tiers offer additional benefits.”[445](#5f9391cc-9c94-49b1-a892-3ba9da41aebf) Members also elect the board.
- **The count.** As a result, no board seat is reserved for any tier. The board page lists 6 members.
- **What holds the rest.** Platinum costs EUR 1,000 once plus EUR 13,750 a year. In return, it buys a “Personal Association Board member contact,” which is access, not a seat.[446](#920b4a2d-066d-4164-8ab0-39aef47c2ebd)
- **The promise.** Here, the one vote rule is the promise. It sits in the statutes, beside the board rules, and on the membership page too.







### A logo, not a board seat: Drupal and Joomla

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** First, the Drupal Association’s bylaws mention no sponsor, fee or donation in any seat clause.[447](#1f2fa1f3-e38c-4d71-9a6c-68c5a7394791) Certified Partner fees, meanwhile, run from $1,500 to $25,000 a year, set by company size. Partner tiers then rank by contribution credits.[448](#1070444d-ff69-4d05-8935-2bd521e6520b)
- **The count.** The board page lists 11 directors plus an Immediate Past Chair in an advisory role.[449](#5e115607-949e-4cdc-a94a-14b13a226672) Members elect At Large seats, which the board ratifies. In addition, only Dries Buytaert is eligible for the Founding Director seat.[450](#a1ed5084-0262-4012-80e4-73d6c2259976) The page also predates the 2026 election, whose winner joins on November 1.[451](#35058906-69bb-4426-bb5a-c5e378077576)
- **What holds the rest.** A free membership tier exists “to guarantee voting rights for those who choose not to make a financial donation.”[452](#6dc6af16-9af5-4cd2-8795-a5d47be389d9)
- **The promise.** No line says money doesn’t buy a seat. Still, the free tier comes closest.







There’s one advisory body worth knowing, though. The 2024 Starshot Advisory Council had 12 members, and 3 were Certified Partner representatives. Its job, in its own words, was to “provide strategic input and feedback.”[453](#2193bb18-4dc8-4141-9606-734e100d71bb) The announcement doesn’t say payment earned those places.

I work at Pantheon, a WordPress and Drupal host. Pantheon is a platinum Drupal Certified Partner, and a Pantheon employee sat on the 2024 Starshot Advisory Council.[454](#917cc820-3c54-4228-b5f1-4552255874a5)[455](#9e3f9860-9beb-477e-88a5-e02ee9bab5e0)

### Joomla: no board seat, just advertising

Joomla’s sponsor page, by contrast, is the bluntest of the nine. It says “sponsorship is a form of advertising, not a charitable contribution.”[456](#910a2113-c174-4367-9d67-3d88d7d3813b)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** Bylaw membership comes from team roles, not payment. Also, each member gets one vote.[457](#c10d5d4d-2de9-41c0-969a-b4f09a9e8376)
- **The count.** The board has 7 seats: 4 officers and 3 department coordinators.[458](#a571ddc4-6a48-42b2-84e3-cd6200fa9a5e) So none of them is a sponsor seat.
- **What holds the rest.** Team leaders and members elect the department coordinators who sit on the board.
- **The promise.** No line limits what sponsors get. Instead, the advertising line comes nearest. It describes sponsorship, but it doesn’t limit it.







### Where does WordPress sit?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **The rule.** The WordPress Foundation’s 2024 tax return reports 3 voting directors, all 3 independent. Those are the numbers at the end of 2024. It also reports no members, and no one outside the board elects directors.[459](#434b42be-e3d9-40d3-8816-9b1eac4b63cd) Donors, meanwhile, get a listing. The 2026 Global Partner tiers cost $60,000 to $180,000. For that, they list visibility and “A dedicated Slack channel” with the Community Support team. The two upper tiers add event tickets.[460](#9cb15390-19cd-4491-8e1f-001167f66600) However, no tier lists a seat, a vote or an advisory role.
- **The count.** So payment fills 0 of the 3 Foundation seats.
- **What holds the rest.** The board elects itself. The same return says directors must disclose possible conflicts every year. Yet it also says there’s no written conflict of interest policy.[461](#a2701b51-3ade-499d-9bbc-cafd1fbe7010)
- **The promise.** Five for the Future invites companies to “Take your seat at the table.”[462](#04db167b-760b-4b31-90be-12933be77848) Still, it names no body, seat or vote.







### MySQL: ownership holds the seats instead

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

MySQL sells no open source board seats, because Oracle owns the project. For a start, the governance model says Oracle nominates the first committee “for a term of 2 years.” Its FAQ then describes 5 to 7 people “that represent Oracle (majority).” After two years, “elections will be held for non-Oracle seats.”[463](#34179e50-277f-4c15-b34a-d363d64d5692)







Today, the committee page lists six members. Four come from AWS, Booking.com, Google and JP Morgan Chase, and two from MySQL Engineering. In addition, an Oracle vice president chairs it.[464](#06851a8a-94c3-4083-a283-59d103d0d788)

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

So, counting the Chair and the two MySQL Engineering members, 3 of 7 tie to Oracle. That’s not the majority the FAQ describes. The page also doesn’t say whether the Chair votes. Yet neither page explains the gap.







### Do “no governance” promises sit beside the seat rules?

Only one of the nine, TYPO3, keeps both in one document. Here’s where each statement lives, so you can check it yourself.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **PHP Foundation:** in the Code of Conduct, while the seats live on the governance page.[465](#10d64f0d-e87f-4c96-bcc4-198b5345e356)[466](#961f9fb1-4c28-4ef6-89ac-25640c6823ed)
- **OpenJS:** a neutrality line on the Join page, while the seats live in the bylaws.[467](#cfac9a6e-0fe2-4023-819a-ba2d17a75e73)[468](#4b249e84-81b4-479c-9975-41faebd9a53f)
- **MariaDB:** on the sponsor page, beside the pool entries, though it covers code, not seats.[469](#e34189c3-b25b-449b-9263-335413def3a6)
- **W3C:** in the Process Document, while board seats live in the bylaws.[470](#3d26ec28-0538-4cc1-b2e0-a94e6544a91c)[471](#5bd52312-cb8a-4a52-991a-db40703fab9b)
- **TYPO3:** a one vote rule in the statutes, beside the board rules, and on the membership page.[472](#14b2abb9-193f-4387-9054-50cb506d242c)
- **Drupal:** a voting guarantee, also on the membership page.[473](#ab3a839b-9cd0-43ee-886a-6ff438048e37)
- **Joomla:** an advertising line on the sponsor page. It describes sponsorship and limits nothing.[474](#dd08da72-f440-43f3-8b49-ee4103b951df)
- **MySQL and WordPress:** no statement found, so far.







## 👥 Leadership: team reps by employer, and caps on one employer

These tables back [the post on who holds open source leadership when companies pay for the code](https://courtneyr.dev/2026/11/19/open-source-leadership/), published November 19, 2026.

### WordPress team reps by employer, 2018 to 2026

[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

My own seats are in this count. In 2022, I was a Training Team rep, and GoDaddy sponsored my hours.[475](#944c23d2-4e25-492a-90cc-6ad8ce4a55f1) I work at Pantheon now. Pantheon employees have held rep seats on two teams, Photos and Hosting.







[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

YearRep seatsAutomatticOther employerSelf, no employer namedUnknownTeams with repsTeams with an Automattic rep2018286 (21%)19031142019213 (14%)15031232020398 (21%)27041362021346 (18%)24311352022437 (16%)332114520233810 (26%)25211482024478 (17%)38101562025537 (13%)43211652026476 (13%)3443205WordPress team rep seats by employer, 2018 to 2026. A seat is one person on one team in one year, so a handover adds a seat. Seat counts are floors, and shares can move either way. As of 2026-11-15, with 2026 still running.





Notes on the table:

- A seat is one person on one team in one year, so a handover adds a seat. This rewards turnover.
- Automattic led every year but 2019, when it held 3 seats, no other employer held more than 3 and 3 seats had no employer on file.
- 2025: 46 seats went to someone other than Automattic: 43 to other employers (none over 3, so at least 15 employers), 2 self sponsored, 1 unknown.

Here’s what the table shows, in four lines.

- **Most seats:** In my count, Automattic held the most placed rep seats, or tied for the most, every year from 2018 to 2026. In 2018 and 2026, unplaced seats could at most produce a tie. In 2019, they could flip the lead.
- **Its share:** That came to 3 to 10 seats a year, or 13 to 26 percent.
- **Runners up:** No other employer held more than 3 seats in a year.
- **Every team:** Automattic never held a rep seat on every team. Its high was 8 of 14 teams, in 2023.

[analysis](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

“Other employer” isn’t one company, either. In 2025, for example, 43 seats went to at least 15 different employers, and none held more than 3. So the spread of open source leadership in WordPress is wide, with one tall column in the middle of it.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The Team Reps page calls the rep role “a leadership role that is mostly administrative in nature; it is not a Lead role.” It adds that the role “doesn’t impart unilateral decision-making authority for the WordPress project.”[476](#ae8b6ff3-e46f-4d10-b818-595f1401a05d)







### How the count works

The record behind each seat comes from public sources, in this order. Because a seat is one person on one team in one year, a handover can add a person without adding a chair at the table. The [Merge Conflicts methods page](https://courtneyr.dev/merge-conflicts-methods/) explains the labels.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Rep posts:** each team’s public announcements on the Make WordPress blogs name its reps.
- **Pledge profiles:** archived WordPress.org profiles show who sponsored each rep’s hours that year.







[source-derived](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Outside records:** term research and public LinkedIn histories fill gaps. People write their own LinkedIn pages, so those rows carry a lower label.
- **Public chat:** searches of public Making WordPress Slack channels found one more employer.







[account](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **My own seats:** my 2015 seat counts as self employed, from my own account.







Two things stay out on purpose. First, the table counts seats and never names reps. Second, no direct message or private channel went into any count.

### Before 2018, the record thins

From 2012 to 2017, the record holds 35 rep seats, and 8 still have no employer on file. Automattic held 2 of 13 in 2012. In 2013, DreamHost led with 2 of 10. With numbers that small, though, a single seat moves a share by 8 points or more. From 2014 to 2017, for instance, the record holds just 5, 1, 2 and 4 seats a year. So the table starts in 2018, when the rep posts get regular.

### What the record shows beside it

An aim is a claim about intent, so it stays my account. Here’s the public record beside it, element by element.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Who joined:** Automattic’s pledge page listed 36 profiles in December 2019. By July 2022, it listed 112.[477](#e3a1115e-7886-454c-9859-7f1b4a4555e5)
- **Where reps sat:** In 2019, Automattic held rep seats on 3 of 12 teams. In 2020, it held them on 6 of 13.







### What the project said about team reps in public

The project and Automattic both wrote about sponsored work and reps in public. Here’s what they said, in order.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **When coordination went public:** A March 2021 post gave its purpose first: helping coordinate sponsored work. It then opened a Slack channel “for contributors who are sponsored for 32 hours or more.”[478](#bcec39a9-2dad-4bac-a96a-98b163dd0e96)
- **What the project asked for:** That November, a Marketing Team post relayed the executive director’s wish.[479](#4775ddab-381c-4624-9824-0f00aa452dc0) She wanted “two to three Team Reps in each Contributor Team,” with “a mix of company sponsored and self sponsored folks.”[480](#c5f516cf-cb1c-4739-878c-59d76426dd09)
- **When it changed:** Automattic’s January 2025 post gave its reasons first. It cited “an imbalance in how contributions to WordPress are distributed” and the cost of WP Engine’s lawsuits. Then it cut its pledge to “about 45 hours a week.”[481](#4cc76c8d-a4da-4fdd-b0e4-cbff959c609f) In May 2025, it announced a return.[482](#2163ea72-12ed-4c18-bda6-0114eab3ba8c)
- **How it was framed:** The January post had a heading, “A Level Playing Field.” Under it, Automattic said it would match pledges “made by WP Engine and other players.”[483](#110bd9bf-d2f1-41e4-8da7-37bf5b165994)
- **What the pledge page showed:** Automattic listed 103 profiles in November 2024 and 86 in February 2025.[484](#3ab0cde3-08fe-405d-931b-667323ddf274)







### Which projects cap one employer’s share of open source leadership?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

ProjectLeadership bodyWritten limit on one employerReason given beside the ruleDrupalCore committers and initiative leadsNone foundNone foundJoomlaDepartment coordinatorsNone found in the bylaws[485](#4c0fa1dd-df26-4606-8c8b-2dbb51ced9cd)None foundMariaDBStewards and maintainersNone for maintainers. Bylaws stop an election from pushing any sponsor above 25 percent of directors (board only)[486](#f92f8765-42b1-4cce-9434-c12715cb0069)The process applies to every maintainer “regardless of employer or affiliation”MySQLCommitters, leads and steering committeeOracle nominates the first members; the FAQ says Oracle holds the majority, but the listed roster doesn’t show one[487](#ad0f39e1-47ec-491f-b6b0-0dbc7e337dd9)[488](#c1de979c-0143-4b97-afed-747fc58f07f4)None statedNode.jsTechnical Steering CommitteeNo more than one fourth of voting membersTo ensure “adequate representation” of diverse interestsOpenJSCross Project CouncilNo more than one fourth of voting membersNone beside the rulePHPRFC voters and release managersNone foundNone foundTYPO3Team leadsNone found for teams. One person per company on the board (Art. 16).[489](#29ea0918-be8d-4239-b2f4-29a90703699c) Members voted in October 2026 on rules that regroup teams into Units[490](#4ba0cf49-f073-47db-a82c-ca04bc279ab9)None foundW3CElected TAG and Advisory Board seats; group chairsOne elected seat per primary affiliation; a chair can be replaced if a new employer would be “over-represented”“to ensure that the diversity of W3C Members is represented”WordPressTeam repsNone; each team runs its own yearly electionNone foundWritten limits on one employer in ten projects’ leadership bodies, as of 2026-11-15. Sources in the footnotes.





So three bodies write a limit: Node.js, OpenJS and W3C.[491](#026dd52c-61e7-427e-8558-fa2c46b1c713)[492](#33bb3c5a-ab39-44c3-bd37-195831f1dddc)[493](#9b2d78c7-b6b0-4a91-9ca3-c30023b839a2) In each case, a change of job can trigger it. The [Node.js TSC charter](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md), for example, says the overflow “must be immediately remedied.”[494](#02c83e90-5355-4a73-a644-4651a592e148) OpenJS uses almost the same words for its council.[495](#af38ab8b-1ba9-4ce9-902c-424cc865bff6)

### What happens when a leader changes jobs

A cap matters most on the day someone switches employers. So each charter says what happens next.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Node.js:** The overflow is fixed “by the removal of voting member status” from members tied to the over-represented company.[496](#20c4eb76-c8fc-40b5-8acc-180466546fe1)
- **OpenJS:** The council fixes it “by the resignation or removal of one or more voting CPC members.”[497](#9711752a-70a5-484e-a755-276a23baa8e9)
- **W3C:** On the TAG, the organization “must have returned to having at most one seat” by the next regular election.[498](#039b6319-c241-4ad7-93d1-4099226a4f54)







### Share of the work against share of the votes

A cap counts leaders. However, the work and the votes can split in other ways too.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **PHP:** The Foundation says it “authored roughly 42% of all commits to PHP’s core” in 2025.[499](#e739b41c-94a6-4379-913e-9b67759caf3c) It also warns that “a 1-line commit and a 100-line commit are counted equally.”
- **MariaDB:** Its list of stewards and maintainers names 10 people. Nine list MariaDB plc as an affiliation.[500](#4b045aad-6194-4b22-8fce-85214cb8d48e)







- **PHP’s votes:** The 2026 license vote was 51 yes, 0 no and 2 abstain.[501](#1ae4f727-80fb-49aa-a019-01b0ab070951)

## 🧾 Finances: budget votes, filings and who can open the books

This table and the chart back [the post on whether publishing open source finances gives members a say](https://courtneyr.dev/2026/11/20/open-source-finances/), published November 20, 2026.

### Four shapes of published finances

What’s public comes in four shapes, from the most detail to the least.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Every transaction:** The PHP Foundation says all its incoming and outgoing transactions are public through Open Collective. It also posts a yearly report.[502](#2a2982e9-05ab-48d3-89f3-bfbe7b4429b8)
- **Audits and a budget:** TYPO3 links its 2025 financial statements, its auditor’s report and its 2026 budget from one General Assembly page.[503](#08a648b8-c57e-4f87-9c34-cb2a7261cb63) Its auditor, BDO, describes the work as a “limited statutory examination.”[504](#71495fd9-5421-4db6-90d7-47b421252da4) The Drupal Association lists statements for each year from 2011 to 2025.[505](#b048d498-a179-4a7d-be40-d3a710a86adc) On November 15, the links for 2011, 2012 and 2014 didn’t open.
- **Tax returns:** W3C posts its Forms 990 for 2022 to 2024.[506](#13e734ea-fd61-447f-a66b-fc3f4be5c0a3) The WordPress Foundation’s 2024 return is on ProPublica, and its site posts yearly summary pages.[507](#ec810898-5a09-4061-bb4e-9aa9dfbf0cee)[508](#c26372cf-e3a2-4838-8020-02987422e6b2) The OpenJS Foundation’s 2024 return is on ProPublica, too.[509](#f481075f-3e05-4f75-bf0c-8bb45e61f4a8)
- **Short statements:** Joomla’s Open Source Matters posts a profit and loss for its year ending June 2025. The document doesn’t say whether it was audited.[510](#22fa0eaa-58d5-4c88-9974-4315e4262da8) Meanwhile, the MariaDB Foundation’s board puts its budget estimate in public minutes.[511](#dbca8bcd-9f75-4d0c-b03c-0b2c42285356)







### Who gets a budget vote?

OrganizationWho approves the annual budgetOutside vote on itOutside say over directorsDrupal AssociationThe board, on a Finance Committee draft[512](#93a31227-81f1-487a-8d4e-adc36c762b76)None; the bylaws say it “has no members”Individual members elect At-Large seats, which the board ratifiesJoomla (Open Source Matters)The board, under its 2015 Financial Policy[513](#b750577d-c961-4ecf-8da3-53495e4692de)None foundVolunteer members elect the directors and officers[514](#b23d2da2-b697-4cc3-91a2-5f178b3da572)MariaDB FoundationThe board: “Budget approved as presented”[515](#9b7dce96-69b7-439e-8331-2d34c4c2d64d)None; the directors are the only members[516](#62d42800-4bcd-4fc0-b415-0692c9ea2f85)NoneOpenJS FoundationThe board; a council approves a budget “to be presented to the board”[517](#186b93d5-973f-41b8-a044-d1e65ba6b02f)None; the council approves funds the board delegatesPaying tiers appoint or elect directors; the council designates more[518](#1e99007e-a284-431f-9640-ae6bfc12d9ed)PHP FoundationThe board[519](#9d3525ba-f941-4c20-894d-0ab58f8102d0)None; an Advisory Board recommendsPlatinum sponsors get “Up to 3 seats”TYPO3 AssociationThe board, after a member survey[520](#735170d6-ccbd-434f-b6ea-59b77816dd0e)None; the General Assembly takes note, and members vote on community ideasMembers elect the boardW3C Inc.No budget rule found; the board by inference[521](#971e08c9-12f9-484f-a8da-543ab095c6fa)None foundConsortium Members elect 7 directors; Partner Members elect up to 4WordPress FoundationUnknown; no bylaws foundNone; its return reports no members[522](#a099732a-8fb2-4255-9f5f-8ec8aeaa9224)None; its return answers “No”Who approves the annual budget at eight open source foundations and associations, A to Z. “Outside” means anyone who isn’t a director. Documents read 2026-11-15; sources in the footnotes.### TYPO3: a poll with “no official character”

TYPO3’s [Voting Procedure](https://docs.typo3.org/m/typo3/guide-policy/main/en-us/Association/VotingProcedure.html) states the poll’s purpose first. It calls the poll “a tool of the Board, to ask the members for their preferences regarding the next budget.”[523](#d6085f40-f380-400c-bc91-bc20d591db62)

Then it sets the limits. “The Budget Polling is not an official election,” it says, and the vote “has no official character.”[524](#5e643974-4997-4093-8d6d-0808e19cd51b)

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The statutes match. In my translation of the binding German text, the board prepares and adopts the budget after a member survey. The General Assembly, by contrast, takes note of it.[525](#f1f3fae5-8b68-491a-89c0-712668244e31) Note that the English translation online is older than the German text adopted on October 29, 2026, so I cite the German.







In practice, the 2026 General Assembly shows the gap. Altogether, 112 members took part, representing 123 votes with delegations, out of 1,134 members. The budget item recorded no vote at all.[526](#35d57256-8a3b-48e5-950b-a39d3f4ba2b8)

Still, TYPO3 members hold real power over the people who spend. They elect the board, and they accept the annual accounts.[527](#9a3c642d-9cc4-4b94-9548-466b1847b9db) At the 2026 Assembly, they also voted to discharge the board, a formal approval of its past year. The tally was 56 for, 5 against, 11 abstaining and 51 not cast.[528](#0809c8fb-23a6-4b6a-ba77-5451de7f47ac)

The same protocol records four more votes:[529](#3ccaf43a-7429-469b-b5a6-6143ba61efbf)

- **Discharge of the treasurer:** 72 for, 3 against, 10 abstaining, 38 not cast.
- **BDO confirmed as auditor:** 69 for, 0 against, 17 abstaining, 37 not cast.
- **Petition 5, “Regular Publication of Board Reports and Records”:** 60 for, 2 against, 7 abstaining, 54 not cast.
- **Petition 7, “Making Official Records Published, Findable, and Permanently Available”:** 62 for, 2 against, 9 abstaining, 50 not cast.

It records no vote on the 2025 accounts or on the 2026 budget of EUR 1,000,000.

Community Ideas votes bind, too, on both tracks. For community ideas, “The community votes,” and “the top two community ideas will be funded.” For team ideas, Association members vote on the applications. The third 2026 round had €40,000, split evenly between the two tracks, and the Business Control Committee (BCC) reviews the applications.[530](#f2f2db79-d5a4-4c4b-b6fa-851d96bc0c5c)

### Can you see open source finances without a vote on them?

[![Open source finances, 8 foundations: all publish, 6 let outsiders pick directors, 3 open records to members, no budget votes.](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.6-v01-who-can-act.png) \[PNG, 201.73 KB\]](https://courtneyr.dev/wp-content/uploads/2026/11/oss-2.6-v01-who-can-act.png)Four checks for eight foundations and associations, from their own documents, read November 15, 2026. The image counts “no” and “none found” as one state and needs a rebuild; the data below uses three states. Chart drawn with Claude at my direction.Text description and data for the four checks chart### What this chart shows

- **What it shows:** A grid with eight organizations in rows, A to Z, and four checks in columns. A filled box with “YES” means a written rule or a posted record says yes. A dashed box with “NO” means no, or none found in the documents read. Each column ends with a total out of 8. The lists below split those boxes into three states: yes, no and not determined.
- **Finances public, 8 of 8:** Drupal Association, Joomla’s Open Source Matters, MariaDB Foundation, OpenJS Foundation, PHP Foundation, TYPO3 Association, W3C and the WordPress Foundation.
- **Who picks directors (the image’s “Outsiders pick directors”):** members elect, one vote each, at the TYPO3 Association, W3C, Joomla’s Open Source Matters and the Drupal Association, whose At-Large seats the board ratifies. Paying sponsors hold or choose seats at the OpenJS Foundation and the PHP Foundation, which has automatic Platinum seats. Neither applies at the MariaDB Foundation or the WordPress Foundation.
- **Members may see records by law:** yes at W3C, through Delaware law, and at Joomla’s Open Source Matters, through New York law. Yes at the OpenJS Foundation by my reading of Delaware’s Section 220, which is analysis. No at the MariaDB Foundation, whose directors are its only members, and at the WordPress Foundation, which reports no members. Not determined at the TYPO3 Association, because I didn’t read Swiss law. Also not determined at the Drupal Association and PHP Foundation, because the documents read don’t name the governing law for member rights.
- **Outsiders vote on the annual budget:** no document found gives outsiders this vote. TYPO3’s statutes have members approve the annual accounts, and TYPO3 runs a binding Community Ideas vote. Neither is a vote on the annual budget.

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

The WordPress Foundation’s minutes record money decisions, too. In October 2024, its board carried a motion “to approve a $100,000 donation to the Internet Archive.” The agenda request gives the reason “as they are currently in need.”[531](#f544d995-d8a7-4e22-b3f4-0b1e694702d7) Money coming in gets vetted as well. A 2025 community post says “all sponsorships need to be approved by” two people “from project leadership.”[532](#c995cb60-ed7d-4170-9d44-6dd7c25a9c4d)







Even so, Drupal shows the two can sit side by side. Its “individual members” elect At-Large board seats. In 2026, 307 of 1,274 eligible voters cast ballots.[533](#aac78572-6eb7-4806-8ba5-3d9cc20d5357) Disclosure and a vote sit together there.

### Whose published finances are you reading?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **A fiscal host:** A fiscal host holds and pays out money for a project. The PHP Foundation’s host is Open Source Collective, and its public ledger sits on the Open Collective platform.[534](#37311abe-4ce0-4539-b023-7c660c0ce4c2) PHP has two collectives there, one of them in euros.[535](#1c659c09-fe5b-4d8d-9675-5fd2db44e0df)
- **The foundation itself:** W3C, the Drupal Association and the MariaDB Foundation each report as one organization.[536](#36af7a2a-dc77-4f4f-9c7d-1f5a4fa8da1c)[537](#573a1b57-d06b-482b-82a4-e62fb4fa0015)[538](#61abdd19-324e-4c0f-99b0-a1f94379303f)
- **A parent with a subsidiary:** The WordPress Foundation owns all of WordPress Community Support, PBC (WPCS), a taxable company that runs the WordCamp money.[539](#ee0270f3-7332-46e8-a627-b0ec1c59482d) In 2025, WPCS reported $4,241,714 of operating revenue. The Foundation itself took in $93,131.[540](#d6fe0a2e-9285-4b80-a213-1fb03617a383) TYPO3 also owns 100% of a company, TYPO3 GmbH.[541](#0ea7b470-2a95-44e7-baac-47638583f225)
- **A small volunteer nonprofit:** Open Source Matters reported $15,567 of total income for the year ending June 2025. Interest added $2,468.[542](#227e0d09-3aed-4f0e-b185-e7fb4aafc719)







Cash isn’t the whole budget either. For example, WPCS booked $2,629,992 of donated salary services in 2025, on both sides of its ledger. The page doesn’t name the donor.[543](#6970fbde-8615-478e-9228-cf7779342a73) Also, the Foundation’s return reports zero employees, while it reports sharing paid employees with WPCS.[544](#e68c62bb-8f9e-403e-9e6c-a32162575116)

### Who can open the books?

[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

- **Directors only:** The Drupal Association opens its books “to inspection by the Directors.”[545](#acb05165-20c5-4e8c-b490-1d2a13856dee) At MariaDB, the directors are the members, so the right is theirs.[546](#40f769f7-e98b-49ab-88f3-4096a25f23c7)
- **Members, by Delaware statute:** W3C’s bylaws send member access to Delaware’s Section 220.[547](#136bf5b0-fa89-44e3-8191-9ea818062662) That section covers “a member of a nonstock corporation.”[548](#8d3e4cee-4c8c-49cf-90c7-e7bf87aa397d) OpenJS is a Delaware “non-stock, not for profit membership corporation,” and its members are the paying companies. So Section 220 reaches them too. Its directors also hold an “absolute right” to inspect.[549](#5904b500-acc7-47cd-9157-34b132586565)
- **Members, by New York statute:** Open Source Matters is “a New York Not-For-Profit Corporation.”[550](#753ca67f-e540-4f2c-80cb-a5820b7edf0d) There, a member of six months may inspect minutes and the member list on five days’ written demand. They may also request the yearly balance sheet and profit and loss.[551](#88a8cf3a-feb0-48ab-8d6e-6524a24498a1)
- **No members to ask:** The WordPress Foundation’s return reports no members at all.[552](#c8920162-ef91-4db5-acff-b91892f6b330)







[unknown](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

TYPO3 sits under Swiss law. I didn’t read the Swiss statute, so its members’ inspection rights are unknown, not absent.







[verified](https://courtneyr.dev/merge-conflicts-methods/#h-which-six-evidence-labels-do-the-merge-conflicts-methods-use)

Meanwhile, the PHP Foundation’s ledger shows each expense’s amount and title to anyone.[553](#4df29331-f9b3-4250-9641-fa65c0af0e7b) The papers behind them don’t. Open Collective says “attachments, payment details, addresses, and comments are private.”[554](#d4644264-2725-43c4-afcd-f544016857c5)







## 🏷️ How to read the labels

Many rows and lists on this page carry an evidence label, and [the Merge Conflicts methods page](https://courtneyr.dev/merge-conflicts-methods/) explains each one.

Every claim about a project’s open source governance procedures carries one of six labels, in the research’s own words.[555](#87fed7d4-5edb-481c-a5bb-d3d839400cde) **Verified**: read in a primary document or record, cited with its passage. **Source-derived**: stated by a reliable secondary source, not yet checked against a primary record. **Account**: a named participant’s attributed account, never a finding, including mine. **Analysis**: the researcher’s reading of cited facts. **Hypothesis**: a claim to test. **Unknown**: searched for and not established, which isn’t the same as absent.

Corrections work in the open here, as they do on the posts. Reply from your own site or in a post’s public discussion thread. Prefer a quiet note? The contact form works too. When a correction changes a claim, the methods page logs what changed and when, and the corrected claim stays visible. This page then gets a new revision date.