Skip to content

What does an open source license decide, and what doesn’t it?

An open source license decides what you can do with the code. Open governance decides the rest: the name, access, roles and appeals. Compare 15 projects, WordPress among them, and take four questions to ask before you join.

Courtney
Nov 13, 202618 min read

hen you install a plugin from WordPress.org, its open source license covers the code, but open governance decides who runs the site you got it from. The test I used is simple: when the top says no, is there a written next step? My take is that appeals test open governance, because they matter most when something goes wrong. Inside the project, only a written appeal promises that someone else reviews that no.

Disclosure first: I work at Pantheon, a WP Engine competitor. I used to work at GoDaddy, and I have ties to several people in this story. The full list comes before the evidence.

Key takeaways

  • The big picture: A license grants rights over code to everyone. It grants no vote and no say over servers or accounts.
  • By the numbers: In Drupal and WordPress, one person is named as owner of the main domain.12
  • Why it matters: All four checks or reversals I found after WordPress cut access or accounts came from a lawsuit, a later post or the same person, not from a written appeal.
  • Yes, but: WordPress’s event rules do allow an appeal, by email within 7 days.3
/* Zine treatment for the Yoast AI summary (2026-11-06). Uses theme tokens so dark mode follows. Move to courtneyr-child once approved. */ .wp-block-yoast-seo-ai-summarize{position:relative;background:var(--cr-surface-elevated);color:var(--cr-ink);border:var(--cr-border-thick);box-shadow:var(--cr-shadow-hard);padding:2.1rem 1.5rem 1rem;margin:2.75rem 0 2.25rem;counter-reset:cr-takeaway} .wp-block-yoast-seo-ai-summarize>h2{position:absolute;top:-.95rem;left:1rem;margin:0;padding:.25rem .95rem;background:var(--cr-tape);color:var(--cr-tape-ink);font-family:var(--cr-font-accent);font-size:var(--cr-text-sm);font-weight:700;letter-spacing:.12em;text-transform:uppercase;line-height:1.3;transform:rotate(var(--cr-rotate-1));box-shadow:1px 1px 0 var(--cr-border-strong)} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list{list-style:none;padding:0;margin:0} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li{counter-increment:cr-takeaway;position:relative;margin:0;padding:.75rem 0 .75rem 2.6rem;border-top:1px dashed var(--cr-paper-rule);font-size:1rem;line-height:1.5} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child{border-top:0;padding-top:.2rem} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li::before{content:counter(cr-takeaway,decimal-leading-zero)!important;display:block!important;position:absolute!important;left:0!important;top:.95rem!important;transform:none!important;font-family:var(--cr-font-mono);font-size:var(--cr-text-xs);font-weight:700;letter-spacing:.05em;color:var(--cr-ink-muted);background:none!important;width:auto!important;height:auto!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child::before{top:.4rem!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list strong{font-family:var(--cr-font-accent);font-weight:700;box-shadow:var(--cr-shadow-marker);-webkit-box-decoration-break:clone;box-decoration-break:clone;padding:0 .1em}

🪑 Where I sat, and what I bring

I’ve volunteered in the WordPress project since 2009, and I still contribute; GoDaddy later sponsored some of that work. Much of it was on the Training Team, which made WordPress teaching materials. I’m a former faculty member and rep there, and I’m not active on the team now.

In 2024, I asked a question from the stage at WordCamp US, a WordPress conference, which my post on unwritten governance procedures covers. My words from that day appear in court exhibits in the lawsuit WP Engine brought against Automattic, the company behind WordPress.com, which is led by Matt Mullenweg, WordPress’s project lead.456

In late 2024, before Joost de Valk’s December post and Karim Marucchi’s December post, both about WordPress leadership, I suggested Joost reconnect with Karim. Later, they talked, though I can’t say my suggestion was the reason. That December, I also helped unify the anonymous contributors’ letter that The Repository, a WordPress news outlet, published.7 I also invited several people who later led within FAIR. I wasn’t named in “Joost/Karim Fork,” the January 2025 post that named five accounts for deactivation, which surprised me.8 Looking back, I knew the process was muddy, but I didn’t expect it to turn personal and public at once. That’s my account, not a finding.

🧭 My standing ties, before any record

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

Separately, I chose which groups GoDaddy funded:

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

I’m also an active member of the Technical Steering Committee for FAIR, the FAIR Package Manager, which distributes WordPress plugins and themes. It’s a Linux Foundation project; the Linux Foundation is a nonprofit that hosts open source projects.

Pantheon is also a platinum Drupal Certified Partner.9 And Sé Reed leads The WPOCC; she’s a friend.

🧷 Three more ties to these records

Three more ties touch the records below. In January 2024, wp-content.co reported that I offered to help Matt Mullenweg.10 The Repository reported my 2026 LinkedIn question about a process.11 And I commented on a May 2025 WordPress.org post about blocked members, pointing to existing enforcement guidelines.12 I read each project’s own pages and records on November 13, 2026, for the projects my post on how I chose them explains. I didn’t interview anyone. (Every table sits on the Merge Conflicts data page.)

⚖️ What an open source license decides

A license is a grant. It hands the same permissions to anyone who gets the code, and nobody fills out an application. The Free Software Definition names four freedoms, to use, study, change and share.13 (My post on the four freedoms covers them in full.) Copyleft licenses, like the GNU General Public License (GPL), require shared changes to keep the same license. Permissive licenses, like MIT, don’t. WordPress uses GPL version 2 or any later version. Ghost and Node.js use MIT.14 (Ghost is a publishing platform, and Node.js runs JavaScript outside the browser.)

So notice what no license file I read mentions: a vote, an account or an appeal. That’s governance, and none of these open source licenses touches it. A 2011 report on governance in open source drew the line plainly, “while licenses apply to the source code, governance applies to the project or platform.”15

The name is separate, though. A trademark decides who can call a copy by the project’s name. WordPress’s marks sit with the WordPress Foundation, and Automattic holds “the exclusive license” for commercial use.16

🔑 The domain: governance outside the license

What surprised me most was that no license clause says who controls a project’s domain. Yet for open governance, the domain matters, because it’s where WordPress keeps its plugin directory and its update service. Of the 14 projects whose site pages I read, 8 name an organization as the site’s operator or copyright holder.17 Those pages say who runs the site, not who registered the domain. The 14 are the 13 projects in the first footnote plus WordPress. Two sources I read speak directly to who owns the domain, and both name one person:

  • Drupal. Dries Buytaert “owns and retains full rights to the domain names,” the Drupal Association’s copyright page says. The Association has his permission to use them.18
  • WordPress. Matt Mullenweg declared under oath, “I own the domain name www.WordPress.org individually.”19

A third case, though, is about access, not ownership. Lasse Collin, maintainer of xz-utils, an open source tool, wrote, “Only I have had access to the main tukaani.org website.”20

The chart below counts what each project’s own pages name. Drupal and WordPress sit under one person because of a domain statement, and xz-utils sits there because of an access statement.

[PNG, 205.25 KB]Two panels: who holds each project’s name, and who its site pages name. A stamp marks Mullenweg and Collin, whose entries rest on their own statements. Diagram drawn with Claude at my direction.

🚫 2024: access to WordPress.org, then the court

In 2024, access became the lever. “WP Engine needs a trademark license, they don’t have one,” Matt Mullenweg wrote on 2024-09-25.21 The post also cited “pending their legal claims and litigation against WordPress.org,” and it said, “WP Engine no longer has free access to WordPress.org’s resources.”22 The GPL let WP Engine run WordPress the whole time. I found no written governance step open to WP Engine for that kind of block, so the only outside check came from a lawsuit.

  • 2024-12-10. The court granted WP Engine a preliminary injunction, finding it likely to succeed on intentional interference. It didn’t reach extortion (Dkt. 64).23 (A preliminary injunction is a court order that holds things in place until trial. Intentional interference means knowingly disrupting someone’s contracts, and “Dkt.” is the court’s docket number.)
  • 2025-09-12. A ruling at the pleading stage dismissed attempted extortion without leave to amend. It dismissed the antitrust counts with leave to refile (Dkt. 169).24 (A pleading stage ruling tests whether a complaint states a claim; it isn’t a finding of fact. Antitrust claims allege unfair use of market power, and “leave to amend” means a side may try again.)
  • 2026-09-24. The court then let the refiled antitrust counts proceed. It dismissed the computer extortion claim without leave to amend. It also dismissed the trademark counterclaims Automattic and Mullenweg brought in their own right. Most other counterclaims proceed (Dkt. 410).25 (Counterclaims are claims a defendant files back.)

⚖️ Where the court case stands

Still, both pleading rulings went Automattic’s way on extortion claims. A scheduling order sets a jury trial for 2027-10-19.26

👥 Accounts and roles: project governance for people

Accounts and titles are governance too, even in an open project, and two WordPress records show how they ended.

In January 2025, Matt Mullenweg’s post “Joost/Karim Fork” named five accounts he was deactivating: Joost de Valk, Karim Marucchi, Sé Reed, Heather Burns and Morten Rand-Hendriksen. Its stated reason was “To make this easy and hopefully give this project the push it needs to get off the ground.”27 How many deactivations took effect is unknown, since TechCrunch reported de Valk’s account still active, and The Repository said only Reed’s and Burns’ were deactivated at first.28 De Valk and Marucchi wrote, “We did not talk about a fork.” Burns wrote, “I am not planning a fork of WordPress.”29

🎫 A ticket comment that ended a contributor’s titles

In October 2026, a ticket comment ended a contributor’s titles. Andrea Fercia, a core committer, one of the people who can merge code into WordPress, had opened Trac ticket 50486 on admin notice accessibility. (Trac is WordPress’s public bug tracker.)

On 2026-10-14 at 00:21 GMT, Matt Mullenweg wrote, “Please revert all of this. @afercia you no longer hold any WordPress.org positions or titles or authority, and are invited to contribute your talents to another project.”30 Before the revert, at least two committers had reported false counts, such as “(2 notices)” on a Dashboard showing none.31 Later that day, committer Joe Dolson committed the revert, which undid the change. The commit called the merged change “premature,” citing “significant numbers of unusual notice cases.”32 For the roles, though, the ticket gives no reason.

Neither record shows a written governance step open to the people named. Whether one would have changed either outcome, the record can’t say.

🧾 Where open governance writes down an appeal

Some projects write the next step down. At the OpenJS Foundation, home of Node.js, people involved can appeal within 30 days, but only if the documented process wasn’t followed or the decision didn’t meet the policy.33 If the Code of Conduct team handled the report, different members of that team hear the appeal.34 So that’s a partial answer to whether the same people hear it.

WordPress writes some steps down, too. Its Code of Conduct lists four steps, Correction, Warning, Temporary Ban and Permanent Ban, and describes no appeal.35 At events, though, either party can appeal an incident decision by email within 7 days, to a community team rep, one of the team’s elected leads, or to the Executive Director the page names.36 Community leaders enforce the code, and its list of them includes project leads. Yet it names no one who enforces it on a project lead, which leaves the top of its governance open.37 Drupal shares the one-owner domain finding, so I gave its governance the same check, using its open pages. Its Community Working Group page says the group can “enforce binding arbitration” and describes no appeal, though it links a separate conflict resolution policy I didn’t read.38

[PNG, 2.95 MB]Chapter 5 of the pantry story, a fictional food pantry that runs through this series. The pantry and its people are fictional. Illustration made with ChatGPT at my direction from the series cast.

🗒️ The 2025 review and project governance

The 2025 record pointed at that gap itself. A 2025-05-01 review prioritized blocks made “without communication or notification,” named no one and described no formal appeal.39 By 2025-05-21, a later post said most blocked members were back, and it proposed “clear and consistent paths for appeal.”40

⚖️ The best case against written appeals

The best case against my claim is that WordPress walked back parts of several of these calls without any appeal. In 2026, the same day as the ticket comment, Matt wrote, “Please whoever turned off @afercia’s account undo that. That wasn’t what I asked for and isn’t needed.”41 On 2025-04-22, he wrote on WordPress.org, “we’re dropping all the human blocks.”42 In April 2026, he wrote in #core-committers, a Slack channel for core committers, “I really wish we had followed [de Valk’s] lead when he tried to help us. I didn’t do enough to support him.”43

Appeals also cost time, and some projects choose finality on purpose. WHATWG, which writes the HTML standard, says that when it removes a participant, “the Steering Group’s determination in each instance is final and non-appealable.”44 OpenJS limits its appeals to 30 days and to process failures.45 On that view, a quick fix from the top beats a slow review.

But those fixes came from the same person or a later post, not from a written governance step open to anyone else. WHATWG’s no appeal rule at least has a written author, its Steering Group, not one person. A written appeal isn’t proof that it works. Still, nobody walks through a door that was never built.

🔍 What I still can’t answer about open governance

What I still can’t answer is how often any of these appeals changes an outcome. My research didn’t measure outcomes, so this post can’t either. If your project publishes how many appeals it has heard and how they ended, send me the page. I’ll add it.

❓ Questions to ask about any project’s open governance

None of these answers lives in a license. They’re governance questions, so ask them in the open before you join, and again before you lead.

  1. Who holds the trademark, and on what terms can you use the name?
  2. Who holds the domain, the update server and the package registry?
  3. Who can vote on a release, a budget or a leader, and who can lead a team?
  4. Who can suspend an account or remove a package, and who reviews that call?

When the answer is a page, read it. When it’s a person, write that down too.

🙋 Frequently asked questions

🏷️ Can I mention Drupal by name without asking?

For plain references, yes. Drupal’s trademark policy grants them an automatic license, and its holder grants other licenses at “sole discretion.”46

🎫 How old was the ticket behind the 2026 revert?

Andrea Fercia opened Trac ticket 50486, “Improve the admin notices accessibility,” on 2020-06-27.47

🐘 Who holds copyright on the PHP website?

The PHP Group, according to php.net.48 In your project, who reviews a no from the top, and where is that written?

Footnotes (48)
  1. Each project’s own pages, read 2026-11-13: ClassicPress privacy policy, https://www.classicpress.net/privacy-policy/; Drupal.org Terms of Service, https://drupal.org/terms; Ghost terms of service, https://forum.ghost.org/t/terms-of-service/4; Joomla privacy policy, https://www.joomla.org/privacy-policy.html; MariaDB Foundation privacy policy, https://mariadb.org/privacy-policy/; MySQL legal policies, https://www.mysql.com/about/legal/; nodejs.org README, https://github.com/nodejs/nodejs.org; PHP copyright, https://php.net/copyright; RubyGems.org policies, https://rubygems.org/policies; TYPO3 Association legal notice, https://typo3.community/legal-notice; Drupal Association copyright page, “Domain ownership,” modified 2017-10-13, https://www.drupal.org/association/copyright; Lasse Collin, “XZ Utils backdoor,” updated 2025-01-17, https://tukaani.org/xz-backdoor/; Backdrop about page, https://backdropcms.org/about; WHATWG FAQ, https://www.whatwg.org/faq. Accessed 2026-11-13. ↩︎
  2. Matthew Charles Mullenweg. Declaration, paragraph 2. WPEngine, Inc. v. Automattic Inc., No. 3:24-cv-06917-AMO (later captioned 4:24-cv-06917-AMO), Dkt. 39. Filed 2024-10-30. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.39.0_1.pdf [PDF]. Accessed 2026-11-13. ↩︎
  3. WordPress Community Team. “Incident report response procedure.” Make WordPress Community Handbook. https://make.wordpress.org/community/handbook/community-deputy/the-community-supporter-program/when-things-happen/incident-report-response-procedure/. Accessed 2026-11-13. ↩︎
  4. United States District Court, Northern District of California. “WPEngine, Inc. v. Automattic Inc., No. 4:24-cv-06917-AMO.” Exhibits at Dkt. 18-28, 107-4, 18-5 and 69-16. CourtListener RECAP. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.18.28.pdf [PDF]; https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.107.4.pdf [PDF]; https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.18.5.pdf [PDF]; https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.69.16.pdf [PDF]. Accessed 2026-11-13. ↩︎
  5. Dom Nicastro. “Automattic Confirms Mullenweg Is Back as CEO, 2 Days After It Had an Interim CEO.” CMSWire. 2026-09-12. https://www.cmswire.com/digital-experience/automattic-confirms-mullenweg-is-back-as-ceo/. Also TechCrunch. “Automattic’s board forces CEO Matt Mullenweg into leave of absence.” 2026-09-09. https://techcrunch.com/2026/09/09/automattics-board-forces-ceo-matt-mullenweg-into-leave-of-absence/. Accessed 2026-11-13. ↩︎
  6. Make WordPress Core. “WordPress Core Team,” Core Handbook. make.wordpress.org. Updated 2026-09-07. https://make.wordpress.org/core/handbook/about/organization/. Accessed 2026-11-10. ↩︎
  7. The Repository. “Dear WordPress community: We stand with you.” December 2024, as summarized by Post Status. https://poststatus.com/business-roundup-week-ending-december-20/. Accessed 2026-11-13. ↩︎
  8. Matt Mullenweg. “Joost/Karim Fork.” WordPress.org News. 2025-01-11. https://wordpress.org/news/2025/01/jkpress/. Accessed 2026-11-13. ↩︎
  9. Drupal Association. “Drupal Certified Partners.” Drupal.org. https://new.drupal.org/drupal-services. Accessed 2026-11-20. ↩︎
  10. wp-content.co. “Bay Lights” report, section on Matt Mullenweg. https://wp-content.co/bay-lights/. Accessed 2026-11-20. ↩︎
  11. The Repository (Rae Morey). “Matt Mullenweg Orders Accessibility Revert, Tells Core Committer to ‘Contribute Your Talents to Another Project’.” 2026-10-15. Sponsored by Pressable, owned by Automattic. https://www.therepository.email/matt-mullenweg-orders-accessibility-revert-tells-core-committer-to-contribute-your-talents-to-another-project. Accessed 2026-11-13. ↩︎
  12. Mary Hubbard. “Restoring Trust while Preserving Safety.” Make WordPress Project. 2025-05-21. https://make.wordpress.org/project/2025/05/21/restoring-trust-while-preserving-safety/. Accessed 2026-11-13. ↩︎
  13. Free Software Foundation. “What is Free Software?” GNU Project. Updated 2026-06-09. https://www.gnu.org/philosophy/free-sw.html. Accessed 2026-11-13. ↩︎
  14. Each project’s own license file or page, fetched 2026-11-13. WordPress: “license.txt.” wordpress-develop on GitHub. https://github.com/WordPress/wordpress-develop/blob/trunk/src/license.txt [TXT]. Ghost: “LICENSE.” GitHub. https://github.com/TryGhost/Ghost/blob/main/LICENSE. Node.js: “LICENSE.” GitHub. https://github.com/nodejs/node/blob/main/LICENSE. Accessed 2026-11-13; the Ghost and Node.js files rechecked 2026-11-20. ↩︎
  15. VisionMobile (Liz Laffan). “A new way of measuring Openness, from Android to WebKit: The Open Governance Index.” SlashData. 2011-07-29. https://www.slashdata.co/post/report-a-new-way-of-measuring-openness-from-android-to-webkit-the-open-governance-index-updated. Accessed 2026-11-13. ↩︎
  16. Drupal, WordPress Foundation and OpenJS Foundation. Trademark policies. Drupal trademark policy, sections I.A and II, https://www.drupal.org/about/trademark; WordPress Foundation trademark policy, https://wordpressfoundation.org/trademark-policy/; OpenJS Foundation trademark policy (2021-01-12), https://trademark-policy.openjsf.org/. Accessed 2026-11-13. ↩︎
  17. Each project’s own pages, read 2026-11-13: ClassicPress privacy policy, https://www.classicpress.net/privacy-policy/; Drupal.org Terms of Service, https://drupal.org/terms; Ghost terms of service, https://forum.ghost.org/t/terms-of-service/4; Joomla privacy policy, https://www.joomla.org/privacy-policy.html; MariaDB Foundation privacy policy, https://mariadb.org/privacy-policy/; MySQL legal policies, https://www.mysql.com/about/legal/; nodejs.org README, https://github.com/nodejs/nodejs.org; PHP copyright, https://php.net/copyright; RubyGems.org policies, https://rubygems.org/policies; TYPO3 Association legal notice, https://typo3.community/legal-notice; Drupal Association copyright page, “Domain ownership,” modified 2017-10-13, https://www.drupal.org/association/copyright; Lasse Collin, “XZ Utils backdoor,” updated 2025-01-17, https://tukaani.org/xz-backdoor/; Backdrop about page, https://backdropcms.org/about; WHATWG FAQ, https://www.whatwg.org/faq. Accessed 2026-11-13. ↩︎
  18. Each project’s own pages, read 2026-11-13: ClassicPress privacy policy, https://www.classicpress.net/privacy-policy/; Drupal.org Terms of Service, https://drupal.org/terms; Ghost terms of service, https://forum.ghost.org/t/terms-of-service/4; Joomla privacy policy, https://www.joomla.org/privacy-policy.html; MariaDB Foundation privacy policy, https://mariadb.org/privacy-policy/; MySQL legal policies, https://www.mysql.com/about/legal/; nodejs.org README, https://github.com/nodejs/nodejs.org; PHP copyright, https://php.net/copyright; RubyGems.org policies, https://rubygems.org/policies; TYPO3 Association legal notice, https://typo3.community/legal-notice; Drupal Association copyright page, “Domain ownership,” modified 2017-10-13, https://www.drupal.org/association/copyright; Lasse Collin, “XZ Utils backdoor,” updated 2025-01-17, https://tukaani.org/xz-backdoor/; Backdrop about page, https://backdropcms.org/about; WHATWG FAQ, https://www.whatwg.org/faq. Accessed 2026-11-13. ↩︎
  19. Matthew Charles Mullenweg. Declaration, paragraph 2. WPEngine, Inc. v. Automattic Inc., No. 3:24-cv-06917-AMO (later captioned 4:24-cv-06917-AMO), Dkt. 39. Filed 2024-10-30. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.39.0_1.pdf [PDF]. Accessed 2026-11-13. ↩︎
  20. Each project’s own pages, read 2026-11-13: ClassicPress privacy policy, https://www.classicpress.net/privacy-policy/; Drupal.org Terms of Service, https://drupal.org/terms; Ghost terms of service, https://forum.ghost.org/t/terms-of-service/4; Joomla privacy policy, https://www.joomla.org/privacy-policy.html; MariaDB Foundation privacy policy, https://mariadb.org/privacy-policy/; MySQL legal policies, https://www.mysql.com/about/legal/; nodejs.org README, https://github.com/nodejs/nodejs.org; PHP copyright, https://php.net/copyright; RubyGems.org policies, https://rubygems.org/policies; TYPO3 Association legal notice, https://typo3.community/legal-notice; Drupal Association copyright page, “Domain ownership,” modified 2017-10-13, https://www.drupal.org/association/copyright; Lasse Collin, “XZ Utils backdoor,” updated 2025-01-17, https://tukaani.org/xz-backdoor/; Backdrop about page, https://backdropcms.org/about; WHATWG FAQ, https://www.whatwg.org/faq. Accessed 2026-11-13. ↩︎
  21. Matt Mullenweg. “WP Engine is banned from WordPress.org.” WordPress.org News. 2024-09-25. https://wordpress.org/news/2024/09/wp-engine-banned/. Accessed 2026-11-13. ↩︎
  22. Matt Mullenweg. “WP Engine is banned from WordPress.org.” WordPress.org News. 2024-09-25. https://wordpress.org/news/2024/09/wp-engine-banned/. Accessed 2026-11-13. ↩︎
  23. United States District Court, Northern District of California. Orders in WPEngine, Inc. v. Automattic Inc., No. 4:24-cv-06917-AMO: Dkt. 64, 2024-12-10, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]; Dkt. 169, 2025-09-12, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.169.0.pdf [PDF]; Dkt. 410, 2026-09-24, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.410.0.pdf [PDF]. Accessed 2026-11-13. ↩︎
  24. United States District Court, Northern District of California. Orders in WPEngine, Inc. v. Automattic Inc., No. 4:24-cv-06917-AMO: Dkt. 64, 2024-12-10, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]; Dkt. 169, 2025-09-12, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.169.0.pdf [PDF]; Dkt. 410, 2026-09-24, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.410.0.pdf [PDF]. Accessed 2026-11-13. ↩︎
  25. United States District Court, Northern District of California. Orders in WPEngine, Inc. v. Automattic Inc., No. 4:24-cv-06917-AMO: Dkt. 64, 2024-12-10, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]; Dkt. 169, 2025-09-12, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.169.0.pdf [PDF]; Dkt. 410, 2026-09-24, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.410.0.pdf [PDF]. Accessed 2026-11-13. ↩︎
  26. United States District Court, Northern District of California. WPEngine, Inc. v. Automattic Inc., No. 4:24-cv-06917-AMO. Scheduling order, Dkt. 373, 2026-09-11, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.373.0.pdf [PDF]; unopposed administrative motion for clarification of that order, Dkt. 461, 2026-11-10, https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.461.0.pdf [PDF]. Accessed 2026-11-13. ↩︎
  27. Matt Mullenweg. “Joost/Karim Fork.” WordPress.org News. 2025-01-11. https://wordpress.org/news/2025/01/jkpress/. Accessed 2026-11-13. ↩︎
  28. TechCrunch. “Matt Mullenweg to deactivate WordPress contributor accounts over alleged fork plans.” 2025-01-11. https://techcrunch.com/2025/01/11/matt-mullenweg-deactivates-wordpress-accounts-of-contributors-planning-a-fork. The Repository (Rae Morey). “Fork or Fiction? WordPress Co-Founder Bans Governance Advocates in Latest Dispute.” 2025-01-13, update note dated “15 January 2024” [sic]. https://www.therepository.email/fork-or-fiction-wordpress-co-founder-bans-governance-advocates-in-latest-dispute. Note re-read 2026-11-13. Accessed 2026-11-13. ↩︎
  29. Joost de Valk and Karim Marucchi, 2025-01-11; Heather Burns, 2025-01-12. De Valk on Bluesky: https://bsky.app/profile/joost.blog/post/3lfirmrdbjc2c. Marucchi on X: https://x.com/karimmarucchi/status/1878212008287334409. Burns on her blog: https://heatherburns.tech/2025/01/12/another-day-of-stochastic-harassment-for-old-times-sake/. Accessed 2026-11-13. ↩︎
  30. WordPress Trac. “#50486 (Improve the admin notices accessibility).” core.trac.wordpress.org. Comments 82, 84, 94, 97 and 100; changeset 64347, 2026-10-14. https://core.trac.wordpress.org/ticket/50486. Accessed 2026-11-13. ↩︎
  31. WordPress Trac. “#50486 (Improve the admin notices accessibility).” core.trac.wordpress.org. Comments 82, 84, 94, 97 and 100; changeset 64347, 2026-10-14. https://core.trac.wordpress.org/ticket/50486. Accessed 2026-11-13. ↩︎
  32. WordPress Trac. “#50486 (Improve the admin notices accessibility).” core.trac.wordpress.org. Comments 82, 84, 94, 97 and 100; changeset 64347, 2026-10-14. https://core.trac.wordpress.org/ticket/50486. Accessed 2026-11-13. ↩︎
  33. OpenJS Foundation Cross Project Council. “COC_POLICY.md.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_POLICY.md. Accessed 2026-11-13. ↩︎
  34. OpenJS Foundation Cross Project Council. “COC_POLICY.md.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_POLICY.md. Accessed 2026-11-13. ↩︎
  35. WordPress Community. “Community Code of Conduct.” Make WordPress Handbook. Modified 2024-11-19. https://make.wordpress.org/handbook/community-code-of-conduct/. Accessed 2026-11-13. ↩︎
  36. WordPress Community Team. “Incident report response procedure.” Make WordPress Community Handbook. https://make.wordpress.org/community/handbook/community-deputy/the-community-supporter-program/when-things-happen/incident-report-response-procedure/. Accessed 2026-11-13. ↩︎
  37. WordPress Community. “Community Code of Conduct.” Make WordPress Handbook. Modified 2024-11-19. https://make.wordpress.org/handbook/community-code-of-conduct/. Accessed 2026-11-13. ↩︎
  38. Drupal Community Working Group. “Community Working Group.” Drupal.org. https://www.drupal.org/community/cwg. Accessed 2026-11-20. ↩︎
  39. Destiny Kanno. “Review of Blocked Community Members.” Make WordPress Project. 2025-05-01. https://make.wordpress.org/project/2025/05/01/review-of-blocked-community-members/. Accessed 2026-11-13. ↩︎
  40. Mary Hubbard. “Restoring Trust while Preserving Safety.” Make WordPress Project. 2025-05-21. https://make.wordpress.org/project/2025/05/21/restoring-trust-while-preserving-safety/. Accessed 2026-11-13. ↩︎
  41. WordPress Trac. “#50486 (Improve the admin notices accessibility).” core.trac.wordpress.org. Comments 82, 84, 94, 97 and 100; changeset 64347, 2026-10-14. https://core.trac.wordpress.org/ticket/50486. Accessed 2026-11-13. ↩︎
  42. Matt Mullenweg. “WordPress Jubilee.” WordPress.org News. 2025-04-22. https://wordpress.org/news/2025/04/jubilee/. Accessed 2026-11-20. ↩︎
  43. Matt Mullenweg. Message in #core-committers, Making WordPress Slack. 2026-04-14. https://wordpress.slack.com/archives/C18723MQ8/p1776174633204259. Visible to members of Making WordPress Slack. Accessed 2026-11-13. ↩︎
  44. WHATWG. “Workstream Policy,” Removal and Relationships with other groups. whatwg.org. No date shown. https://whatwg.org/workstream-policy. Accessed 2026-11-20. ↩︎
  45. OpenJS Foundation Cross Project Council. “COC_POLICY.md.” GitHub. https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_POLICY.md. Accessed 2026-11-13. ↩︎
  46. Drupal, WordPress Foundation and OpenJS Foundation. Trademark policies. Drupal trademark policy, sections I.A and II, https://www.drupal.org/about/trademark; WordPress Foundation trademark policy, https://wordpressfoundation.org/trademark-policy/; OpenJS Foundation trademark policy (2021-01-12), https://trademark-policy.openjsf.org/. Accessed 2026-11-13. ↩︎
  47. WordPress Trac. “#50486 (Improve the admin notices accessibility).” core.trac.wordpress.org. Comments 82, 84, 94, 97 and 100; changeset 64347, 2026-10-14. https://core.trac.wordpress.org/ticket/50486. Accessed 2026-11-13. ↩︎
  48. Each project’s own pages, read 2026-11-13: ClassicPress privacy policy, https://www.classicpress.net/privacy-policy/; Drupal.org Terms of Service, https://drupal.org/terms; Ghost terms of service, https://forum.ghost.org/t/terms-of-service/4; Joomla privacy policy, https://www.joomla.org/privacy-policy.html; MariaDB Foundation privacy policy, https://mariadb.org/privacy-policy/; MySQL legal policies, https://www.mysql.com/about/legal/; nodejs.org README, https://github.com/nodejs/nodejs.org; PHP copyright, https://php.net/copyright; RubyGems.org policies, https://rubygems.org/policies; TYPO3 Association legal notice, https://typo3.community/legal-notice; Drupal Association copyright page, “Domain ownership,” modified 2017-10-13, https://www.drupal.org/association/copyright; Lasse Collin, “XZ Utils backdoor,” updated 2025-01-17, https://tukaani.org/xz-backdoor/; Backdrop about page, https://backdropcms.org/about; WHATWG FAQ, https://www.whatwg.org/faq. Accessed 2026-11-13. ↩︎

Did you enjoy this article?

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

Across the AtmosphereDiscussions