How do open source projects make decisions: votes, consensus, or a final say?
Open source decision making ends a fight by a vote, by consensus or by a final say. I read 16 rule sets, WordPress among them, to ask whom your hours answer to.
hen you argue in a pull request, a proposed code change, open source decision making ends the fight by a vote, by consensus or by a final say. Some projects mix two. Drupal, an open source content management system like WordPress, settles its core code by consensus. In addition, members of its nonprofit elect board seats in its board elections.12
🔗 My ties, before any verdict
I work at Pantheon, a WordPress and Drupal host that competes with WP Engine, another WordPress host. My employer also competes with WordPress VIP, the enterprise service from Automattic, the company behind WordPress.com. At GoDaddy, I started and ran its Five for the Future program, which pledges staff time to WordPress, until July 2026.
Separately, I chose which groups GoDaddy funded:
- The PHP Foundation, which pays developers to work on the PHP language.
- OpenJS, the foundation behind Node.js and other JavaScript projects.
- W3C, the World Wide Web Consortium, a web standards body.
- PHP_CodeSniffer, a tool that checks code style.
- The WPOCC, a WordPress community collective where I’m a co-founding board member.
I’m also an active member of the Technical Steering Committee for FAIR, the FAIR Package Manager, which distributes WordPress plugins and themes. It’s a Linux Foundation project; the Linux Foundation is a nonprofit that hosts open source projects. Pantheon is also a platinum Drupal Certified Partner, and this post judges Drupal’s rules.3
Key takeaways
- The big picture: Of the 16 rule sets I read, some settle fights by vote, some by consensus and some by one role’s final say.
- By the numbers: I documented nine cases from 2018 to 2026 when WordPress’s top leaders set aside a team’s decision. I found no page that sets a procedure for that.4
- Why it matters: In open source decision making, the rule that ends a disagreement decides whom your volunteer hours answer to.
- Yes, but: A final say can follow the room. Python’s founder or a delegate agreed with the community in 99 percent of proposals where it had a view.5
🪑 Where I sat: a working group with no one named to decide
In February 2015, WordPress announced a working group on the new user experience, or NUX.6 I had just joined WordPress’s Training Team. First, NUX volunteers each claimed links from the dashboard’s Welcome Panel to study. I took “Set your timezone and date format.” My report noted that these settings sit near “Week Starts On.” The recap said grouping in that value “might be helpful as well.”78 On a related ticket in Trac, WordPress’s bug tracker, I wrote one line as courane01 (then @courtneyengle). “Hoping this is bumped up again.”9 Bold strategy.
The announcement promised that recommendations “will receive direct feedback from core team members.”10 Then Drew Jaynes, who led the chats, turned to the WordPress 4.2 release. Then, in May, I asked, “What’s the latest with NUX?” Ryan Boren answered that NUX was “waiting for @drew to recover from 4.2.”11
No closing post followed. Since then, I’ve found no record of the recommendations reaching anyone who could decide them. Eleven years later, Week Starts On still sits in General Settings.12 At least one of us stayed on task.
🔎 How I read 16 projects’ decision rules
So on November 13 and 14, 2026, I read the written rules for decision making in 15 open source projects and standards bodies. Drupal has two rule sets (code and nonprofit), so that’s 16. They’re chosen like the rest of my Merge Conflicts series. Every table lives on the Merge Conflicts data page. Also, I read each project’s own pages and didn’t interview anyone.
Three more ties bear on the WordPress teams below. I’m a former Training Team faculty member and rep. In 2024 I wrote Sustainability Team posts, and I objected to that team’s closure. My work sits alongside the Accessibility Team. (The full list is in the box at the end.)
Here’s my take. Before you give a project your hours, find out whom they answer to, and whether anyone has to answer back. NUX promised feedback from core team members. Nothing written said which one, or by when. The 4.2 crunch may have stalled it anyway. By contrast, a named decider would at least have owed an answer.
🗳️ Votes: how open source projects decide what counts as a yes
A vote is the plainest rule a project can write down. It needs three numbers. Who votes? What bar passes? How many must take part? Four in my set put decisions to a wide membership vote, meaning everyone in a defined electorate rather than a small council: Joomla and TYPO3 (two more open source content management systems), the Drupal Association and PHP. Only Joomla writes a minimum turnout.13141516 Joomla’s 84 voters are its members, team leaders, coordinators and officers.17
PHP, the language WordPress runs on, changes through written proposals called RFCs. People with php.net accounts and some chosen community representatives vote on them. PHP’s voting rules need yes votes to reach twice the no votes, so a tie fails. They set no minimum turnout.18 In August 2026, the Pipe Assignment Operator drew 14 yes and 12 no, so it failed.19 Somewhere, a math teacher smiles.
📉 How turnout shapes a vote
So turnout matters in every vote, and it varies a lot.
| Vote | Eligible | Voted | Share |
|---|---|---|---|
| Joomla president, 202620 | 84 | 63 | 75% |
| Drupal Association At-Large, 202521 | 1,459 | 528 | 36% |
| Drupal Association At-Large, 202622 | 1,274 | 307 | 24% |
| TYPO3 bylaws, online, October 202623 | 1,121 | 272 | 24% |
Drupal Association At-Large seats are the ones its members elect.24
TYPO3 shows the trade a vote makes. Most recently, in October 2026, its members passed new bylaws online, 204 to 66 with 2 blank. Another 849 eligible votes went uncast.25 So a clear, public result came from 18 percent of the electorate.
🤝 Consensus, and who can block a change
Consensus is the quietest method, because nobody counts. The group seeks agreement, and anyone can object. The Apache Software Foundation, a nonprofit that hosts many open source projects, calls its quiet version lazy consensus, “silence gives assent.”26
So the real question is who can block. For example, at Node.js, the JavaScript runtime, one collaborator’s objection holds a change. It holds until the group reaches consensus or its Technical Steering Committee votes.27 At Apache, a binding no, a no vote from someone whose vote counts, needs a technical reason on code. “A veto without a justification is invalid and has no weight.” With one, nobody can override it. It stands until the voter withdraws it.28 At MariaDB Server, the database forked from MySQL, each member of its Maintainer Council gets one veto every three years, and a two thirds vote can override it. When that council ties, the MariaDB Foundation’s CEO, who “must not be a member of the Council,” casts the deciding vote.29 At WHATWG, the HTML standards group, “The addition must have the support of at least two implementers,” meaning browser makers.30
🗓️ Consensus on a WordPress ticket
WordPress shows consensus on the ticket I touched. In 2014, Mark Jaquith proposed hiding the Week Starts On setting. The ticket was punted, or moved to a later release. “Still looking for a consensus on the best way forward here.” In 2015, two committed code changes, called changesets, hid the setting in some cases. Then the contributor rmccue wrote “Recommend revert,” because “it doesn’t seem like there was agreement here.” The revert landed, and the ticket closed as wontfix.31
Nobody voted, and every step of that open source decision making is public. Still, consensus can’t show who chose silence, or why.
🎯 A final say, written into a role
Then there are projects that write the final say into a role. Usually, that rule is easy to find in a handbook. However, it tells you who decides, not how often they overrule anyone.
Drupal’s Project Lead “may proactively make or override these decisions” on core code.32 At MySQL, the database Oracle owns, “Oracle is the project lead.” That’s the far end of a final say.33 And WordPress’s Core Handbook says a core leadership team, led by Matt Mullenweg, “governs all aspects of the project.” The page sets no term limit, and it names no way to elect or remove the leadership team.34
What surprised me most was a handbook page for Meta Janitors. In April 2026, Matt Mullenweg started the group, whose contributor table lists 12 handles. Its goal is to “move quickly, embrace experimentation, and rebuild WordPress.org into a world-class community hub.” The only approval it names is “me (Matt).”35 The page is public, but it doesn’t say how members are chosen.
⏱️ When a WordPress team’s decision didn’t stand
WordPress leaves many decisions to its teams.36 If a change touches only your team and the team agrees, the page for team representatives says “go for it.” For changes to WordPress.org, the project’s home site, the executive director (now Mary Hubbard) or Matt “will make the final decision.”37
🔽 Nine cases from the top down
So I looked from the top down, where leaders overrule a team. I counted each time the project lead or executive director set aside a decision or process a team had adopted. I found nine from 2018 to 2026.38
- 2018, Core committers (people who can commit code to core). The project lead alone approves commit access.39
- 2022, Performance. WebP, a compressed image format, came out of WordPress 6.1 as a default. Matt said the change was “a lot for right now.”40
- 2024, Marketing. The team’s scope changed, then an archive plan followed.41
- 2025, Sustainability. The team was dissolved.42
- 2026, Core committers. The Akismet spam filter plugin came back, though committers backed a revert.43
- 2026, Themes. A link underline rule from the Accessibility Team was dropped.44
- 2026, Meta (the team that runs WordPress.org’s sites). Meta Janitors change WordPress.org without team approval.45
- 2026, Core. Matt pulled real time collaboration from WordPress 7.0, citing race conditions, server load and bugs found in fuzz testing.46
- 2026, Accessibility. A theme review plan was “permanently delayed.”47
🗂️ Where these project decision rules came from
Each came with a stated reason, and the data page quotes them. Still, three rest on Slack messages that need a WordPress.org account to read. Recent cases are easier to find, so this isn’t a trend line. I didn’t count overrides by Drupal’s Project Lead or anyone else, so it isn’t a comparison either. In the last case, Matt wrote that the team had “overstepped its authority, usefulness, and charter.” Later, he said it kept “missing your own set goals and deadlines.”48 In October, the team made its accessibility-ready tag, a label for themes that pass an accessibility review, conditional. Its post doesn’t mention Matt’s comment.49
🧩 Project decision rules that write an undo button
In WordPress, I found no page that sets an appeal for a change made from above. Drupal writes its Project Lead’s override power down, and its governance page names no appeal of the Lead’s decisions either.50 Other projects write that lever down. Python’s Steering Council can recall a PEP delegate. A PEP is a Python Enhancement Proposal, and the delegate is the person named to decide one. That recall “will overrule any prior acceptance or rejection.”51 WordPress writes down the org chart, but the undo button has no manual. (My post on appeals in open governance asks who reviews the top role.)
What I still can’t answer is how often anyone pulls these levers. W3C is one exception. (Its index lists ten finished formal objection cases from August 2023 to June 2026, and five overruled the objection.)52 If you know where another project keeps that count, send me the source.
⚖️ The best case for a final say in open source decision making
The best case for a final say comes from Python. Its founder held the final say until July 2018.53 A study of about 1.5 million Python emails looked at how he decided. The founder or a delegate agreed with the community in 99 percent of cases where it had reached a view.54 A second study, of 208 Apache Incubator projects, found that a project’s written rules didn’t track where it spent its effort.55 So rules on paper may not show how decision making in an open source project really runs. Defenders add that a final say is fast.
Still, that 99 percent covers only proposals where a community view existed, about 60 percent of them.56 For the rest, then, the founder’s call was the answer. And Python wrote a new rule. Under PEP 13, its governance document, core team members elect a steering council after each feature release. They can remove it “via a vote of no confidence.”57 In one model, the Apache study also found better odds of graduating for projects that absorbed their voting rules.58 A lead who follows the room is a gift. Even so, a written way to answer back gives the room a lever if the lead stops listening.
🙋 Frequently asked questions
Two, or one after seven days, unless a collaborator objects.59
PHP’s voters, through the same RFC process, which needs a two thirds vote.6061
First, its Advisory Board drafts process changes. Then they go to a member review of at least 28 days.62
Every relationship I disclose here
- Pantheon: my employer, a WordPress and Drupal host that competes with WP Engine and WordPress VIP, and a platinum Drupal Certified Partner.
- GoDaddy: my employer until July 2026. I started and ran its Five for the Future program, which pledges staff time to WordPress.
- GoDaddy funding: separately, I chose which groups GoDaddy funded: the PHP Foundation, OpenJS, W3C, PHP_CodeSniffer and The WPOCC.
- FAIR Package Manager: an active member of its Technical Steering Committee.
- The WPOCC: a co-founding board member.
- Training Team: former faculty member and rep. NUX also overlapped my first months on the team.
- Sustainability Team: 2024 posts, and I objected to its closure.
- Accessibility Team: my work sits alongside it.
- My own words: a 2015 flow report comment, a 2015 Trac comment and a 2015 chat question, all quoted in this post.
On your own open source project, what decision making rule ended the last disagreement? Could a newcomer find it written down?
Footnotes (62)
- Drupal. “Drupal core governance.” Drupal governance pages. https://project.pages.drupalcode.org/governance/core/drupal-core/. Accessed 2026-11-13. ↩︎
- Drupal Association. “The Drupal Association Announces 2026 Board Election Winner.” drupal.org. 2026-08-31. https://www.drupal.org/association/blog/the-drupal-association-announces-2026-board-election-winner. And “The Drupal Association Announces 2025 Board Election Winner and Additional Board Members.” 2025-07-29. https://www.drupal.org/association/blog/the-drupal-association-announces-2025-board-election-winner-and-additional-board-members. Accessed 2026-11-13. ↩︎
- Drupal Association. “Drupal Certified Partners.” Drupal.org. https://new.drupal.org/drupal-services. Accessed 2026-11-15. ↩︎
- Courtney Robertson. “Team decisions changed from above, 2018 to 2026” and “Project decision rules, side by side.” Merge Conflicts data page, courtneyr.dev. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
- Pankajeshwara Nand Sharma, Bastin Tony Roy Savarimuthu and Nigel Stanger. “Influence of Roles in Decision-Making during OSS Development: A Study of Python.” EASE 2021. https://arxiv.org/abs/2106.02209. The 99 percent covers proposals where a community view was established, about 60 percent of them. The paper’s own counts differ in places (248 or 245 proposals; 415 of 466 proposals decided by the founder alongside a 73 percent share). Accessed 2026-11-13. ↩︎
- Drew Jaynes. “4.2 Community Initiative: NUX Working Group.” Make WordPress Core. 2015-02-05. https://make.wordpress.org/core/2015/02/05/4-2-community-initiative-nux-working-group/. Accessed 2026-11-13. ↩︎
- Tracy Levesque. “4.2 Nux Group Recap / Call to Action, March 3, 2015.” Make WordPress Test. 2015-03-08, with my comment of 2015-03-09. https://make.wordpress.org/test/2015/03/08/4-2-nux-group-recap-call-to-action-march-3-2015/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- Tracy Levesque. “4.2 Nux Group Recap, March 17, 2015.” Make WordPress Test. 2015-03-17. https://make.wordpress.org/test/2015/03/17/4-2-nux-group-recap-march-17-2015/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- WordPress Trac. “#28344: Remove ‘Week Starts On’ setting UI.” core.trac.wordpress.org. 2014-05-24 to 2015-11-18, with changesets 35336, 35337 and 35685; my comment of 2015-02-24, as courane01. https://core.trac.wordpress.org/ticket/28344. Accessed 2026-11-13. ↩︎
- Drew Jaynes. “4.2 Community Initiative: NUX Working Group.” Make WordPress Core. 2015-02-05. https://make.wordpress.org/core/2015/02/05/4-2-community-initiative-nux-working-group/. Accessed 2026-11-13. ↩︎
- Making WordPress Slack. #core-test (named #core-flow in 2015), public channel. Messages of 2015-03-31, 2015-05-05 and 2015-06-11, including my question of 2015-05-05. https://wordpress.slack.com/ (sign-in required). Accessed 2026-11-13. ↩︎
- WordPress. “options-general.php.” wordpress-develop on GitHub, trunk. https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-admin/options-general.php. Accessed 2026-11-13. ↩︎
- Open Source Matters. “2026 OSM President Election Results.” Joomla Community, Leadership blog. 2026. https://community.joomla.org/blogs/leadership/osm-president-election-results-2026.html. And “Amended and Restated By-laws of Open Source Matters, Inc.” 2021-12-13. https://www.opensourcematters.org/images/documents/20211213-OSM-Bylaws.pdf [PDF]. The results page labels 63 of 84 as 69.05 percent, which is 58 of 84 (the winner’s votes); 63 of 84 is 75 percent. Accessed 2026-11-13. ↩︎
- Drupal Association. “Second Restated Bylaws” (updated 2017-12-12). drupal.org. https://drupal.org/files/board-bylaws.pdf [PDF]. Accessed 2026-11-13. ↩︎
- PHP. “Voting on PHP features.” wiki.php.net, modified 2025-02-10. https://wiki.php.net/rfc/voting. And “feature-proposals.rst.” php/policies on GitHub. https://github.com/php/policies/blob/main/feature-proposals.rst. Accessed 2026-11-13. ↩︎
- TYPO3 Association. “Statuten der TYPO3 Association” (German original, valid since October 2026), Art. 15, 19 and 43. docs.typo3.org. https://docs.typo3.org/m/typo3/guide-policy/main/en-us/Association/BylawsAndProceedingsGermanOriginal.html. Translations are mine. Accessed 2026-11-13. ↩︎
- Open Source Matters. “2026 OSM President Election Results.” Joomla Community, Leadership blog. 2026. https://community.joomla.org/blogs/leadership/osm-president-election-results-2026.html. And “Amended and Restated By-laws of Open Source Matters, Inc.” 2021-12-13. https://www.opensourcematters.org/images/documents/20211213-OSM-Bylaws.pdf [PDF]. The results page labels 63 of 84 as 69.05 percent, which is 58 of 84 (the winner’s votes); 63 of 84 is 75 percent. Accessed 2026-11-13. ↩︎
- PHP. “Voting on PHP features.” wiki.php.net, modified 2025-02-10. https://wiki.php.net/rfc/voting. And “feature-proposals.rst.” php/policies on GitHub. https://github.com/php/policies/blob/main/feature-proposals.rst. Accessed 2026-11-13. ↩︎
- Caleb White. “PHP RFC: Pipe Assignment Operator.” wiki.php.net. Declined, poll closed August 2026. https://wiki.php.net/rfc/pipe_assignment_operator. Accessed 2026-11-13. ↩︎
- Open Source Matters. “2026 OSM President Election Results.” Joomla Community, Leadership blog. 2026. https://community.joomla.org/blogs/leadership/osm-president-election-results-2026.html. And “Amended and Restated By-laws of Open Source Matters, Inc.” 2021-12-13. https://www.opensourcematters.org/images/documents/20211213-OSM-Bylaws.pdf [PDF]. The results page labels 63 of 84 as 69.05 percent, which is 58 of 84 (the winner’s votes); 63 of 84 is 75 percent. Accessed 2026-11-13. ↩︎
- Drupal Association. “The Drupal Association Announces 2026 Board Election Winner.” drupal.org. 2026-08-31. https://www.drupal.org/association/blog/the-drupal-association-announces-2026-board-election-winner. And “The Drupal Association Announces 2025 Board Election Winner and Additional Board Members.” 2025-07-29. https://www.drupal.org/association/blog/the-drupal-association-announces-2025-board-election-winner-and-additional-board-members. Accessed 2026-11-13. ↩︎
- Drupal Association. “The Drupal Association Announces 2026 Board Election Winner.” drupal.org. 2026-08-31. https://www.drupal.org/association/blog/the-drupal-association-announces-2026-board-election-winner. And “The Drupal Association Announces 2025 Board Election Winner and Additional Board Members.” 2025-07-29. https://www.drupal.org/association/blog/the-drupal-association-announces-2025-board-election-winner-and-additional-board-members. Accessed 2026-11-13. ↩︎
- Mathias Bolt Lesniak. “TYPO3 Association members approve new governance structure.” TYPO3 News. 2026-10-29. https://news.typo3.com/article/typo3-association-members-approve-new-governance-structure. And “EGA 2026 Protocol.” typo3.org. https://typo3.org/fileadmin/Association/General_Assembly/2026_extraordinary/EGA_2026_Protocol_signed.pdf [PDF]. Accessed 2026-11-13. ↩︎
- Drupal Association. “The Drupal Association Announces 2026 Board Election Winner.” drupal.org. 2026-08-31. https://www.drupal.org/association/blog/the-drupal-association-announces-2026-board-election-winner. And “The Drupal Association Announces 2025 Board Election Winner and Additional Board Members.” 2025-07-29. https://www.drupal.org/association/blog/the-drupal-association-announces-2025-board-election-winner-and-additional-board-members. Accessed 2026-11-13. ↩︎
- Mathias Bolt Lesniak. “TYPO3 Association members approve new governance structure.” TYPO3 News. 2026-10-29. https://news.typo3.com/article/typo3-association-members-approve-new-governance-structure. And “EGA 2026 Protocol.” typo3.org. https://typo3.org/fileadmin/Association/General_Assembly/2026_extraordinary/EGA_2026_Protocol_signed.pdf [PDF]. Accessed 2026-11-13. ↩︎
- The Apache Software Foundation. “Voting.” apache.org. https://www.apache.org/foundation/voting.html. Accessed 2026-11-13 and 2026-11-20. ↩︎
- Node.js. “GOVERNANCE.md” (last changed 2026-09-12) and “Collaborator Guide.” nodejs/node on GitHub. https://github.com/nodejs/node/blob/main/GOVERNANCE.md; https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md. And “TSC Charter.” https://github.com/nodejs/TSC/blob/main/TSC-Charter.md. Accessed 2026-11-13. ↩︎
- The Apache Software Foundation. “Voting.” apache.org. https://www.apache.org/foundation/voting.html. Accessed 2026-11-13 and 2026-11-20. ↩︎
- MariaDB. “governance.md,” sections 3.2 and 3.3. MariaDB/governance on GitHub. 2026-08-01. https://github.com/MariaDB/governance/blob/main/governance.md. Accessed 2026-11-13. ↩︎
- WHATWG. “Working Mode.” whatwg.org. https://whatwg.org/working-mode. Accessed 2026-11-13 and 2026-11-20. ↩︎
- WordPress Trac. “#28344: Remove ‘Week Starts On’ setting UI.” core.trac.wordpress.org. 2014-05-24 to 2015-11-18, with changesets 35336, 35337 and 35685; my comment of 2015-02-24, as courane01. https://core.trac.wordpress.org/ticket/28344. Accessed 2026-11-13. ↩︎
- Drupal. “Drupal core governance.” Drupal governance pages. https://project.pages.drupalcode.org/governance/core/drupal-core/. Accessed 2026-11-13. ↩︎
- Oracle. “MySQL Community Governance Model,” sections 3.2, 3.3 and 10. dev.mysql.com. https://dev.mysql.com/community/governance-model/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- WordPress. “Project Organization” (updated 2026-09-07). Core Handbook. https://make.wordpress.org/core/handbook/about/organization/. Accessed 2026-11-13. ↩︎
- WordPress. “Meta Janitors.” Make WordPress Meta handbook. Updated 2026-04-23. https://make.wordpress.org/meta/handbook/about/projects/meta-janitors/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- WordPress. “Team Reps.” Make WordPress Updates. Updated 2026-09-28. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- WordPress. “Team Reps.” Make WordPress Updates. Updated 2026-09-28. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Courtney Robertson. “Team decisions changed from above, 2018 to 2026” and “Project decision rules, side by side.” Merge Conflicts data page, courtneyr.dev. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
- Matt Mullenweg. Message in #core-committers, Making WordPress Slack. 2018-12-15. https://wordpress.slack.com/ (sign-in required). Accessed 2026-10-28. ↩︎
- Matt Mullenweg. “WebP in Core for 6.1.” Make WordPress Core. 2022-09-11. https://make.wordpress.org/core/2022/09/11/webp-in-core-for-6-1/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Josepha Haden Chomphosy. “Making a WordPress Media Corps.” Make WordPress Marketing. 2024-03-20. https://make.wordpress.org/marketing/2024/03/20/making-a-wordpress-media-corps/. And “WordPress Media Corps Next Steps.” 2024-04-29. https://make.wordpress.org/marketing/2024/04/29/wordpress-media-corps-next-steps/. Accessed 2026-11-14. ↩︎
- Matt Mullenweg. Message in #sustainability, Making WordPress Slack. 2025-01-08. https://wordpress.slack.com/ (sign-in required). Accessed 2026-10-26. ↩︎
- WordPress Trac. “#65012.” core.trac.wordpress.org. Comments 38, 48 and 54, April to May 2026. https://core.trac.wordpress.org/ticket/65012. Accessed 2026-11-14. ↩︎
- Matt Mullenweg. Messages in #core-committers and #themes, Making WordPress Slack. 2026-04-13. https://wordpress.slack.com/ (sign-in required). Accessed 2026-10-28. ↩︎
- WordPress. “Meta Janitors.” Make WordPress Meta handbook. Updated 2026-04-23. https://make.wordpress.org/meta/handbook/about/projects/meta-janitors/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- annezazu. “Real-time collaboration will not ship in WordPress 7.0.” Make WordPress Core. 2026-05-08. https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Matt Mullenweg. Comments of 2026-08-01 and a reply of 2026-08-17 on Joe Dolson, “Accessibility-ready Theme Reviews: Extending the Deadline.” Make WordPress Accessibility. 2026-07-23. https://make.wordpress.org/accessibility/2026/07/23/accessibility-ready-theme-reviews-extending-the-deadline/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Matt Mullenweg. Comments of 2026-08-01 and a reply of 2026-08-17 on Joe Dolson, “Accessibility-ready Theme Reviews: Extending the Deadline.” Make WordPress Accessibility. 2026-07-23. https://make.wordpress.org/accessibility/2026/07/23/accessibility-ready-theme-reviews-extending-the-deadline/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Joe Dolson. “Accessibility-ready directory changes coming!” Make WordPress Accessibility. 2026-10-05. https://make.wordpress.org/accessibility/2026/10/05/accessibility-ready-directory-changes-coming/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Drupal. “Drupal core governance.” Drupal governance pages. https://project.pages.drupalcode.org/governance/core/drupal-core/. Accessed 2026-11-13. ↩︎
- Python. “PEP 1: PEP Purpose and Guidelines.” peps.python.org. https://peps.python.org/pep-0001/. Accessed 2026-11-14. ↩︎
- W3C. “W3C Council” index and the Digital Credentials council report (2026-06-19). w3.org. https://www.w3.org/about/council/; https://www.w3.org/2026/06/council-digital-credentials-report.html. Accessed 2026-11-13. ↩︎
- Python. “PEP 13: Python Language Governance.” peps.python.org. https://peps.python.org/pep-0013/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- Pankajeshwara Nand Sharma, Bastin Tony Roy Savarimuthu and Nigel Stanger. “Influence of Roles in Decision-Making during OSS Development: A Study of Python.” EASE 2021. https://arxiv.org/abs/2106.02209. The 99 percent covers proposals where a community view was established, about 60 percent of them. The paper’s own counts differ in places (248 or 245 proposals; 415 of 466 proposals decided by the founder alongside a 73 percent share). Accessed 2026-11-13. ↩︎
- Mahasweta Chakraborti, Curtis Atkisson, Stefan Stanciulescu, Vladimir Filkov and Seth Frey. “Do We Run How We Say We Run? Formalization and Practice of Governance in OSS Communities.” ACM, 2024. https://doi.org/10.1145/3613904.3641980; https://arxiv.org/abs/2309.14245. The authors call the graduation link correlational. Accessed 2026-11-13. ↩︎
- Pankajeshwara Nand Sharma, Bastin Tony Roy Savarimuthu and Nigel Stanger. “Influence of Roles in Decision-Making during OSS Development: A Study of Python.” EASE 2021. https://arxiv.org/abs/2106.02209. The 99 percent covers proposals where a community view was established, about 60 percent of them. The paper’s own counts differ in places (248 or 245 proposals; 415 of 466 proposals decided by the founder alongside a 73 percent share). Accessed 2026-11-13. ↩︎
- Python. “PEP 13: Python Language Governance.” peps.python.org. https://peps.python.org/pep-0013/. Accessed 2026-11-13 and 2026-11-20. ↩︎
- Mahasweta Chakraborti, Curtis Atkisson, Stefan Stanciulescu, Vladimir Filkov and Seth Frey. “Do We Run How We Say We Run? Formalization and Practice of Governance in OSS Communities.” ACM, 2024. https://doi.org/10.1145/3613904.3641980; https://arxiv.org/abs/2309.14245. The authors call the graduation link correlational. Accessed 2026-11-13. ↩︎
- Node.js. “GOVERNANCE.md” (last changed 2026-09-12) and “Collaborator Guide.” nodejs/node on GitHub. https://github.com/nodejs/node/blob/main/GOVERNANCE.md; https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md. And “TSC Charter.” https://github.com/nodejs/TSC/blob/main/TSC-Charter.md. Accessed 2026-11-13. ↩︎
- PHP. “php/policies” README (policies “adopted through its RFC process”). GitHub. https://github.com/php/policies. Accessed 2026-11-20. ↩︎
- PHP. “Voting on PHP features.” wiki.php.net, modified 2025-02-10. https://wiki.php.net/rfc/voting. And “feature-proposals.rst.” php/policies on GitHub. https://github.com/php/policies/blob/main/feature-proposals.rst. Accessed 2026-11-13. ↩︎
- W3C. “W3C Process Document” (18 August 2025), section 10, “Process Evolution.” w3.org. https://www.w3.org/policies/process/. Accessed 2026-11-13. ↩︎
Did you enjoy this article?
Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.