What can an open source fork keep, and what stays behind?
Every WordPress site asks a server for updates. Seven forks show that an open source fork keeps the code, not the name, and who runs its updates shows how far it left.
very WordPress site asks a server whether its plugins have updates. Who runs that server shows how far an open source fork really left. None of the seven forks I compared left with the original’s name. All of them kept the code.1
Before any verdict, my ties. 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.
Key takeaways
- The big picture: All seven open source forks kept the code, and each started under a new name.2
- Why it matters: Whoever runs a fork’s update server decides what its sites hear. ClassicPress still sends plugin and theme checks to WordPress.org.3
- By the numbers: Of the three forks whose channels I trace here, only ClassicPress still asks the original’s server. OpenTofu runs its own registry, and Backdrop moved before its 1.0 release.456
- Yes, but: Borrowing a channel spares a small fork real work, and it’s no secret when a fork does it.
🔌 Why I asked who runs a fork’s updates
The seven forks are Joomla, a 2005 fork of the Mambo content management system; MariaDB, a 2009 fork of the MySQL database; Backdrop, a 2013 fork of Drupal 7; io.js, a 2014 fork of Node.js; ClassicPress, a 2018 fork of WordPress; OpenTofu, a 2023 fork of the infrastructure tool Terraform; and Valkey, a 2024 fork of the Redis database.78910111213 On November 14, 2026, I read each fork’s posts and code, and those of the open source projects they left, plus court orders. I didn’t interview anyone. (The full packing list lives on the Merge Conflicts data page. The post on how I chose the projects explains the wider set.)
When I compared them, the difference I kept coming back to was the update channel. That’s the server your site asks for updates, the place downloads come from and the registry that lists packages.
A few of my ties sit right on this topic. WP Engine, Pantheon’s competitor, owns the Advanced Custom Fields (ACF) plugin, which comes up below. FAIR’s reason to exist sits close to this post’s question. The Linux Foundation also hosts OpenTofu and Valkey, whose records I cite.1415 (The full list, including my Training Team history, is in the box at the end.)
Here’s my take. Before you rely on a fork, ask who runs its updates.
🍴 What a fork keeps: the code, and a right
An open source fork is a copy of a project’s code that becomes its own project. It then makes its own decisions under its own name. The license makes that legal. The Free Software Definition calls it freedom 3: “The freedom to distribute copies of your modified versions to others.”16 So a fork starts with the code in hand. Everything else is a packing problem. (My post on what a license decides covers how little else it reaches.)
By my count, six of the seven forks carried their open source history too. Only Joomla’s public repository starts at the split, in September 2005.171819 Backdrop brought more than 19,000 commits, the saved changes in a project’s history, from before the split.20 ClassicPress carries WordPress history back to 2003.21 And io.js “began as a GitHub fork of joyent/node.”22
Here’s the catch, though. A fork is a right, not a remedy. It lets you leave a decision behind, but it doesn’t explain that decision or reverse it. And code you keep isn’t code you maintain.
🏷️ What no fork took: the name and the domain
Not one fork in this set left with its open source original’s name. The trademark policies I read explain why. Drupal’s policy names a fork called “ImprovedDrupal” as a use its automatic license doesn’t cover.23 Oracle’s guidelines bar the MySQL marks from an open source distribution’s name without permission.24 The WordPress Foundation’s policy aims to stop anyone who would “unfairly profit from, trick or confuse people.”25
MariaDB and Backdrop both built their names early. MariaDB registered mariadb.org about eight months before its first beta.26 Backdrop’s trademark claims first use a month before its announcement. Today it sits with Software Freedom Conservancy, a nonprofit that holds assets for open source projects. An assignment signed in 2021 moved it there.27
Still, a new name doesn’t guarantee a new kind of owner. A company owns the MariaDB mark, and the MariaDB Foundation uses its own name under a license from that company.28 The name is the one thing a fork can’t take, and the first thing it has to invent.
📡 The update channel shows how far a fork left
Whoever runs the update server decides what your site hears, including which version of a plugin arrives. So the channel is the clearest test of how far a fork really left.
In the record I read, Backdrop shows a full move. On the day of its announcement, its pre-release code still asked updates.drupal.org.29 On 2014-12-21, a month before 1.0, one changed line pointed it at updates.backdropcms.org. The commit treats that new server as “not implemented” until it answers.30
OpenTofu kept a foot in the old house, though not on its server. Providers are plugins that let Terraform and OpenTofu manage a service, such as Amazon Web Services. OpenTofu built its own registry but kept provider names like hashicorp/aws.31 Its FAQ says plainly, “OpenTofu will not have its own providers,” because “Terraform providers have not altered their licenses.”32
Would forks rebuild so much if update servers were shared infrastructure that no single project ran? Seven cases can’t answer that. It’s the question closest to FAIR’s work, which is why that disclosure sits above.
🔍 ClassicPress still asks WordPress.org
What surprised me most was ClassicPress. Scott Bowler’s 2018 founding post called it “a maintained fork of WordPress 4.9.8 without Gutenberg,” the block editor.33 In September 2018, its committee decided that “WordPress endpoints will be used for plugin checks.” (An endpoint is the web address code calls.) The minutes add that a check of whether that was allowed was under way, with an “initial review” that “seems positive.”34 Version 1.0 then sent core update notices from ClassicPress’s own servers.35
Plugins and themes never moved. You can open ClassicPress’s update code on GitHub and search for api.wordpress.org. In the version I read, it sits on lines 381 and 657.36 So a site on this fork still learns about plugin updates from the original project’s directory.
What I still can’t answer is why, or how that review ended. The minutes don’t record a full reason or a final result.37 I also can’t tell, from seven forks, which signs predict that a fork outlasts its first year. If you have a source on either, please send it.
🔀 When the directory’s owner forks a plugin
One 2024 record shows what running the channel can do. On 2024-10-12, a WordPress.org news post by Matt Mullenweg said the WordPress security team was “invoking point 18 of the plugin directory guidelines.” It forked ACF as Secure Custom Fields.38 Guideline 18 lets the directory change plugin code “without developer consent, in the interest of public safety.”39 The post said the fork removed commercial upsells and fixed a security problem.
Site owners carried the result. ACF sites still updating from WordPress.org received the fork through the existing listing when they updated.4041 On 2024-12-10, a court’s preliminary injunction, an order that holds until trial, required the ACF listing restored “as it existed as of September 20, 2024.”42 The orders I read don’t decide whether the security claim was right. As of October 2026, trial was set for 2027-10-19.43
So a fork reached a plugin’s users through the directory they updated from, because the fork’s maker ran it. ClassicPress sites ask that same directory about plugins, so a swap like this could reach them too.44
©️ Who can relicense after the split
A fork of an open source project can keep a license, but changing it for future releases takes owning the copyright, or permission from those who do. Oracle’s contributor agreement, the contract contributors signed to submit code, once gave it joint ownership of each MySQL contribution.45 HashiCorp’s agreement takes a broad license while contributors keep ownership. In 2023, HashiCorp moved Terraform’s future releases off the Mozilla Public License, an open source license.4647 OpenTofu forked from the open source code that came before.48
WordPress’s license.txt reads “Copyright 2011-2026 by the contributors.”49 With copyright spread across contributors, I see no single holder who could relicense WordPress alone.
⚖️ The best case for borrowing from the original
The best case for borrowing comes from the forks that do it, and it’s a fair one for small open source projects. Someone has to run and pay for every update server and registry. ClassicPress planned plugin checks against WordPress endpoints before its 1.0 release.50 OpenTofu runs its own registry but kept HashiCorp’s provider names on purpose.51 Borrowing meant neither had to build everything on day one, and the code was theirs either way. And borrowing is public: anyone can read the address in the code.
The counterweight is in this record too. Backdrop moved before its first release, and io.js went home when the Node.js and io.js committees merged in 2015.52 Secure Custom Fields shows what the directory’s owner can deliver to sites that never chose a fork.53 Borrowing a channel is a reasonable start. It isn’t independence.
🙋 Frequently asked questions
Yes, a fork can rejoin the open source project it left. Node.js 4.0.0 shipped in September 2015, “now combined in a single codebase” with io.js.54 The OpenJS Foundation took ownership of the Node.js trademarks in February 2022.55
Sometimes. Redis’s trademark policy lets a fork say its software “includes code that is based on a fork of Redis® Open Source version XX.”56
Yes. Its first beta, on 2009-10-29, was “based on MySQL 5.1.38.”57
Every relationship I disclose here
- Pantheon: my employer, a WordPress and Drupal host that competes with WP Engine and WordPress VIP.
- 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. FAIR is a Linux Foundation project, as are OpenTofu and Valkey.
- The WPOCC: a co-founding board member.
- Training Team: former faculty member and rep.
If your main platform made a call you couldn’t accept tomorrow, which server would your sites still be asking for updates?
Footnotes (57)
- Courtney Robertson. “Seven forks, one packing list.” Merge Conflicts data page, courtneyr.dev. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
- Courtney Robertson. “Seven forks, one packing list.” Merge Conflicts data page, courtneyr.dev. https://courtneyr.dev/merge-conflicts-data/. Accessed 2026-11-20. ↩︎
- ClassicPress. “update.php,” commit b577653e. GitHub. https://github.com/ClassicPress/ClassicPress/blob/b577653eb1cf13f3bf80d4cf8e493be1b1fc5202/src/wp-includes/update.php. Accessed 2026-11-14. ↩︎
- ClassicPress. “update.php,” commit b577653e. GitHub. https://github.com/ClassicPress/ClassicPress/blob/b577653eb1cf13f3bf80d4cf8e493be1b1fc5202/src/wp-includes/update.php. Accessed 2026-11-14. ↩︎
- OpenTofu. “Provider Requirements.” OpenTofu documentation. https://opentofu.org/docs/language/providers/requirements/. Accessed 2026-11-14. ↩︎
- Backdrop CMS. “Issue #386: Report the update server as ‘not implemented’ until it starts reporting HTTP 200,” commit 7f7ab99b, 2014-12-21. GitHub. https://github.com/backdrop/backdrop/commit/7f7ab99ba. Accessed 2026-11-14. ↩︎
- The Mambo Development Team. “Letter to the community.” 2005-08-17. Copy hosted by signatory Emir Sakic. https://www.sakic.net/news/mambo-open-source-development-team-letter-to-the-community/. Accessed 2026-11-14. ↩︎
- Michael “Monty” Widenius. “Press release concerning Oracle/Sun.” Monty says. 2009-10-19. https://monty-says.blogspot.com/2009/10/press-release-concerning-oraclesun.html. Accessed 2026-11-14. ↩︎
- Jen Lampton. “Introducing Backdrop CMS, a Drupal fork.” jenlampton.com. 2013-09-16. https://jenlampton.com/blog/introducing-backdrop-cms-drupal-fork. Accessed 2026-11-14. ↩︎
- io.js. “README.md” at v1.0.0. GitHub. 2015-01-14. https://raw.githubusercontent.com/nodejs/node/v1.0.0/README.md. Accessed 2026-11-14. ↩︎
- Scott Bowler. “ClassicPress: a fork of WordPress without Gutenberg.” ClassicPress. 2018-08-20. https://www.classicpress.net/classicpress-a-fork-of-wordpress-without-gutenberg/. Accessed 2026-11-14. ↩︎
- OpenTofu. “The OpenTofu Manifesto.” opentofu.org. https://opentofu.org/manifesto/. Accessed 2026-11-14. ↩︎
- Linux Foundation. “Linux Foundation Launches Open Source Valkey Community.” 2024-03-28. https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community. Accessed 2026-11-14. ↩︎
- OpenTofu. “FAQ.” opentofu.org. https://opentofu.org/faq/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Linux Foundation. “Linux Foundation Launches Open Source Valkey Community.” 2024-03-28. https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community. Accessed 2026-11-14. ↩︎
- Free Software Foundation. “What is Free Software?” GNU Operating System. https://www.gnu.org/philosophy/free-sw.html. Accessed 2026-11-13. ↩︎
- valkey-io/valkey on GitHub. Oldest commit ed9b544e, “first commit,” by antirez, 2009-03-22; 18,643 commits across all branches before 2024-03-28. https://github.com/valkey-io/valkey/commit/ed9b544e10b84cd43348ddfab7068b610a5df1f7. Checked by cloning, 2026-11-20. ↩︎
- opentofu/opentofu on GitHub. Oldest commit 649cf336, “Initial commit,” by Mitchell Hashimoto, 2014-05-21; 31,551 commits across all branches before 2023-08-25. https://github.com/opentofu/opentofu/commit/649cf336e86da10910f6e50ea3cfaad507a2e336. Checked by cloning, 2026-11-20. ↩︎
- joomla/joomla-cms on GitHub. Oldest commit 5169e6a0, “Initial import into SCM,” by Mitch Pirtle, 2005-09-15. https://github.com/joomla/joomla-cms/commit/5169e6a03c4013c911293fef82413817fec04635. Checked by cloning, 2026-11-20. ↩︎
- Backdrop CMS. “backdrop/backdrop” 1.x history: 19,285 commits dated before 2013-09-15 00:00 UTC (
git rev-list --count --before). GitHub. https://github.com/backdrop/backdrop. Accessed 2026-11-14. ↩︎ - ClassicPress. “New repository initialized by cvs2svn,” commit 51902156, the repository start, 2003-04-01. GitHub. https://github.com/ClassicPress/ClassicPress/commit/51902156. Accessed 2026-11-14. ↩︎
- io.js. “README.md” at v1.0.0. GitHub. 2015-01-14. https://raw.githubusercontent.com/nodejs/node/v1.0.0/README.md. Accessed 2026-11-14. ↩︎
- Dries Buytaert. “Drupal trademark and logo policy.” Drupal.org. https://www.drupal.org/about/trademark. Accessed 2026-11-14. ↩︎
- Oracle. “Oracle Trademarks.” oracle.com. https://www.oracle.com/legal/trademarks/. Accessed 2026-10-26. ↩︎
- WordPress Foundation. “Trademark Policy.” wordpressfoundation.org. https://wordpressfoundation.org/trademark-policy/. Accessed 2026-11-14. ↩︎
- Public Interest Registry. RDAP record for mariadb.org. https://rdap.publicinterestregistry.org/rdap/domain/mariadb.org. Accessed 2026-11-14. ↩︎
- United States Patent and Trademark Office. “BACKDROP CMS,” Registration 4776517, status and assignment records. TSDR. https://tsdr.uspto.gov/#caseNumber=4776517&caseType=US_REGISTRATION_NO&searchType=statusSearch. Accessed 2026-11-14. ↩︎
- MariaDB Foundation. “MariaDB Trademark.” mariadb.org. https://mariadb.org/about/trademark/. Accessed 2026-11-14. ↩︎
- Backdrop CMS. “update.module” at commit ddbffceb, 2013-09-16. GitHub. https://github.com/backdrop/backdrop/blob/ddbffcebcffa532991bbb9733872b95df3527dca/core/modules/update/update.module. Accessed 2026-11-14. ↩︎
- Backdrop CMS. “Issue #386: Report the update server as ‘not implemented’ until it starts reporting HTTP 200,” commit 7f7ab99b, 2014-12-21. GitHub. https://github.com/backdrop/backdrop/commit/7f7ab99ba. Accessed 2026-11-14. ↩︎
- OpenTofu. “Provider Requirements.” OpenTofu documentation. https://opentofu.org/docs/language/providers/requirements/. Accessed 2026-11-14. ↩︎
- OpenTofu. “FAQ.” opentofu.org. https://opentofu.org/faq/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Scott Bowler. “ClassicPress: a fork of WordPress without Gutenberg.” ClassicPress. 2018-08-20. https://www.classicpress.net/classicpress-a-fork-of-wordpress-without-gutenberg/. Accessed 2026-11-14. ↩︎
- ClassicPress. “Committee meeting: a focus on v1 roadblocks.” ClassicPress. Meeting of 2018-09-07, posted 2018-09-08. https://www.classicpress.net/committee-meeting-a-focus-on-v1-roadblocks/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- ClassicPress. “Introducing ClassicPress 1.0.0 Aurora.” ClassicPress. 2019-03-05. https://www.classicpress.net/introducing-classicpress-1-0-0-aurora/. Accessed 2026-11-14. ↩︎
- ClassicPress. “update.php,” commit b577653e. GitHub. https://github.com/ClassicPress/ClassicPress/blob/b577653eb1cf13f3bf80d4cf8e493be1b1fc5202/src/wp-includes/update.php. Accessed 2026-11-14. ↩︎
- ClassicPress. “Committee meeting: a focus on v1 roadblocks.” ClassicPress. Meeting of 2018-09-07, posted 2018-09-08. https://www.classicpress.net/committee-meeting-a-focus-on-v1-roadblocks/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Matt Mullenweg. “Secure Custom Fields.” WordPress.org News. 2024-10-12. https://wordpress.org/news/2024/10/secure-custom-fields/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- WordPress.org Plugins Team. “Detailed Plugin Guidelines,” guideline 18. WordPress Developer Resources. https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/. Accessed 2026-10-26. ↩︎
- Matt Mullenweg. “Secure Custom Fields.” WordPress.org News. 2024-10-12. https://wordpress.org/news/2024/10/secure-custom-fields/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- WPEngine v. Automattic, No. 4:24-cv-06917 (N.D. Cal.), Dkt. 64, Order Granting Preliminary Injunction. 2024-12-10. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]. Accessed 2026-10-27. ↩︎
- WPEngine v. Automattic, Dkt. 64, pp. 41 to 42. 2024-12-10. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]. Accessed 2026-10-27. ↩︎
- WPEngine v. Automattic, Dkt. 373, Order Granting Motion to Modify Summary Judgment Deadlines, 2026-09-11. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.373.0.pdf [PDF]. And Dkt. 433, endorsed DENIED, 2026-10-13. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.433.0.pdf [PDF]. Accessed 2026-10-26. ↩︎
- ClassicPress. “update.php,” commit b577653e. GitHub. https://github.com/ClassicPress/ClassicPress/blob/b577653eb1cf13f3bf80d4cf8e493be1b1fc5202/src/wp-includes/update.php. Accessed 2026-11-14. ↩︎
- Oracle. “Oracle Contributor Agreement,” version 1.5. 2010. https://openoffice-org.staged.apache.org/licenses/oca.pdf [PDF]. Accessed 2026-10-26. ↩︎
- HashiCorp. “Contributor License Agreement.” hashicorp.com. https://www.hashicorp.com/cla. Accessed 2026-11-14. ↩︎
- Armon Dadgar. “HashiCorp adopts Business Source License.” HashiCorp. 2023-08-10. https://www.hashicorp.com/en/blog/hashicorp-adopts-business-source-license. Accessed 2026-11-14. ↩︎
- OpenTofu. “The OpenTofu Manifesto.” opentofu.org. https://opentofu.org/manifesto/. Accessed 2026-11-14. ↩︎
- WordPress. “license.txt,” wordpress-develop trunk. GitHub. https://github.com/WordPress/wordpress-develop/blob/trunk/src/license.txt [TXT]. Accessed 2026-11-13. ↩︎
- ClassicPress. “Committee meeting: a focus on v1 roadblocks.” ClassicPress. Meeting of 2018-09-07, posted 2018-09-08. https://www.classicpress.net/committee-meeting-a-focus-on-v1-roadblocks/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- OpenTofu. “FAQ.” opentofu.org. https://opentofu.org/faq/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- Linux Foundation. “Node.js Foundation Advances Community Collaboration, Announces New Members and Ratified Technical Governance.” 2015-06-16. https://www.linuxfoundation.org/press/press-release/node-js-foundation-advances-community-collaboration-announces-new-members-and-ratified-technical-governance. Accessed 2026-11-14. ↩︎
- WPEngine v. Automattic, No. 4:24-cv-06917 (N.D. Cal.), Dkt. 64, Order Granting Preliminary Injunction. 2024-12-10. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.64.0.pdf [PDF]. Accessed 2026-10-27. ↩︎
- Node.js. “Node v4.0.0 (Current).” Node.js blog. 2015-09-08. https://nodejs.org/en/blog/release/v4.0.0. Accessed 2026-11-14. ↩︎
- OpenJS Foundation. “Node.js Trademarks Transferred to OpenJS Foundation.” 2022-02-14. https://openjsf.org/blog/node-js-trademarks-transferred-to-openjs-foundation. Accessed 2026-11-14. ↩︎
- Redis. “Redis Trademark Policy.” redis.io. Last updated 2026-09-15. https://redis.io/legal/trademark-policy/. Accessed 2026-11-14 and 2026-11-20. ↩︎
- MariaDB. “MariaDB 5.1.38 Release Notes.” MariaDB Documentation. 2009-10-29. https://mariadb.com/docs/release-notes/community-server/old-releases/5.1/5.1.38. Accessed 2026-11-14. ↩︎
Did you enjoy this article?
Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.