What can an open source fork keep, and what stays behind?

Merge ConflictsSeason 2Part 3 of 3

Who decides in an open source project, how they decide, and who can review the decision. Twelve projects, the same questions.

In this series 3 parts published
Open source fork cover for Merge Conflicts 2.3: fork equals code, not control, with name, domain and update channel.

An open source fork keeps the code. I compared seven forks, from Mambo in 2005 to Valkey in 2024. But none took the name, the trademark or the main domain with it. The difference I kept coming back to was the update channel: who runs the server your site asks for updates.

Key takeaways

  • The big picture: Every fork kept the code. But each one rebuilt its name, its trademark and its main domain.
  • Why it matters: The update channel showed how far a fork actually left. ClassicPress still asks WordPress.org about plugin updates.
  • Yes, but: Changing the license later takes ownership or permission. Oracle, HashiCorp and Redis Inc each had one or the other.
  • What to check: Before you rely on a fork, ask who runs its updates.

🍴 What an open source fork is, and what it isn’t

verified

An open source fork is a copy of a project’s code that becomes its own project. It then gets its own name, its own people and its own decisions. The license is also what makes that legal. The Free Software Definition calls it freedom 3: “The freedom to distribute copies of your modified versions to others”.1

In what an open source license decides, I showed that a license covers the code and little else. So a fork starts with the code in hand. Everything else is a packing problem.

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.

Every fork below also met the hardest problem in computer science on day one: naming things.

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

Every relationship I disclose here
  • Pantheon: my employer, a WordPress and Drupal host and a WP Engine competitor.
  • FAIR Package Manager: former member of its Technical Steering Committee.
  • GoDaddy: I managed its Five for the Future contributors until July 2026.
  • The WPOCC: a founding board member.
  • Training Team: former faculty member and rep.

🗣️ Why seven groups forked, in their own words

Each side’s stated reason comes first, before anything it did. Where I found no statement from one side, the list says so. No statement means only that.

🏢 Splits from a company’s project

  • MariaDB, 2009: Monty Widenius, whose company built the fork, wrote that MySQL “needs a different home than Oracle”.2 Oracle’s side, as the European Commission summarized it, included pledges to keep releasing MySQL under the GPL.3
  • Joomla, 2005: The Mambo Development Team, 19 developers, wrote that Miro’s new foundation “is designed to grant that control to Miro”.4 The Mambo Foundation’s newsroom answered that Miro would transfer all of Mambo’s intellectual property to the foundation outright.5
  • io.js, 2014: The fork’s FAQ promised “faster and predictable release cycles” under open governance.6 Meanwhile, I found no Joyent statement about the fork from 2014 in the records I read. By 2015, Joyent’s Scott Hammond said the project “is best governed by a neutral, community-driven forum.”7
  • OpenTofu, 2023: HashiCorp moved future releases of its products off the Mozilla Public License, saying “commercial open source models need to evolve”.8 The fork’s manifesto then said: “With no response from Hashicorp by August 25, we created a fork”.9
  • Valkey, 2024: Redis Inc said cloud providers “commoditize Redis’ investments and its open source community”.10 The Later, the Linux Foundation’s launch said Valkey would continue from Redis 7.2.4 under the BSD license.11

🏡 Splits from a community project

  • Backdrop, 2013: Jen Lampton’s announcement gave the reason: “Drupal 7 was too hard to learn.”12 Its goal was also easy porting of Drupal 7 modules and themes. I found no Drupal statement about Backdrop in the records I read.
  • ClassicPress, 2018: Scott Bowler’s founding post called it “a maintained fork of WordPress 4.9.8 without Gutenberg”.13 The post also says the author’s feedback on the new block editor went unheard. Still, I found no WordPress response from 2018. In 2024, Matt Mullenweg wrote on WordPress.org, “The last decent fork attempt for WordPress was ClassicPress in 2018.”14

🧳 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. “Not checked” means the research didn’t look. So it doesn’t mean the history is missing.

verified

ForkSplitCode and history at the splitName and domain at the splitUpdates by first releaseWho could relicense later
Backdrop2013Kept, with historyNewOwn server by 1.0 (2015); first pointed at Drupal’sNo single holder; authors keep copyright
ClassicPress2018Kept, with historyNewOwn core server by 1.0 (2019); plugin and theme checks still go to WordPress.orgNo single holder; authors keep copyright
io.js2014Kept, with historyNewOwn downloads at 1.0 (2015); the npm registry sharedNo single holder; MIT notices kept
Joomla2005Code kept; history not checkedNewOwn downloads and project forge at 1.0 (2005)Miro, then the Mambo Foundation, for Mambo’s code
MariaDB2009Kept, with historyNewOwn releases from the first beta (2009)Oracle, for MySQL, as copyright owner and through its contributor agreement
OpenTofu2023Code kept; history not checkedNewOwn registry at 1.6.0 (2024); HashiCorp provider names keptHashiCorp, for Terraform, through contributor permission
Valkey2024Code kept; history not checkedNewOwn releases and images at 7.2.5 (2024)Redis Inc, for Redis; older code stays BSD
What 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

Every fork started from the original’s code. Four of them carry the original’s history, so the authors’ names travel with the code.

  • Backdrop: more than 19,000 commits from before the fork, with Drupal history back to 2000.15
  • ClassicPress: WordPress history back to the repository’s start on 2003-04-01.16
  • io.js: its 1.0.0 README said it “began as a GitHub fork of joyent/node.”17
  • Joomla: version 1.0 was Mambo 4.5.2.3, “given it a spring clean and named it Joomla! 1.0.”18
  • MariaDB: its first beta, on 2009-10-29, was “based on MySQL 5.1.38”.19

Still, code you keep isn’t code you maintain. Later, in 2024, ClassicPress released version 2.0, a fresh fork based on WordPress 6.2.3. Merge Conflicts 2.2 covers how that call was made.

analysis

This series also tracks exit, leaving with the code, as one way people can hold a project to account. Here’s what the record shows for exit so far:

  • MariaDB: the fork kept the code and the people. But it didn’t get the name or the right to sell MySQL under other licenses.
  • Backdrop: it kept the history and also built a new name and domain.
  • RubyGems: former maintainers built a new server, but the registry stayed put.
  • WordPress: not covered here. Who holds wordpress.org rests on a sworn court statement, and Merge Conflicts 2.13 covers ownership.

🏷️ What no fork took: the name, the mark and the domain

Not one open source fork in this list left with the original’s name. The trademark policies explain why.

verified

  • Drupal: its policy names a Drupal fork called “ImprovedDrupal” as a use that doesn’t qualify for its automatic license.20
  • MySQL: Oracle’s guidelines bar its marks from the name of an open source distribution without permission.21
  • Redis: its current policy lets a fork say it’s “based on a fork of Redis® Open Source version XX.”22 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.”23 It also asks people not to put WordPress in a domain name.

🗓️ Forks build their names early

verified

So forks build their names early. MariaDB registered mariadb.org on 2009-03-04, about eight months before its first beta.24 Backdrop’s trademark claims first use on 2013-08-15, a month before the announcement.25 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.26

analysis

So MariaDB rebuilt the name, and a smaller version of the old arrangement came with it. A company holds the mark, while a nonprofit holds a license to use it. The name is the one thing a fork can’t take. It’s also the first thing a fork has to invent.

🔌 The update channel a fork can’t pack

By update channel I mean three things. There’s the server that says an update exists, the place the download comes from and the registry that lists packages. For example, every WordPress site asks a server whether its plugins have updates. Whoever runs that server decides what your site hears, so it shows how far an open source fork left.

I used to sit on FAIR’s technical steering committee. FAIR builds another way to deliver WordPress plugins and themes.

verified

  • Backdrop: on the day of the announcement, its code still asked updates.drupal.org.27 A commit on 2014-12-21 switched it to updates.backdropcms.org, a month before 1.0.28 That’s git blame at its purest: one line, two commits, about 15 months apart.
  • ClassicPress: in 2018, its committee agreed to use WordPress endpoints for plugin checks, once a review confirmed it was allowed.29 Version 1.0 then sent update notices from its own servers, with downloads hosted on GitHub.30 Today its code still sends plugin and theme checks to api.wordpress.org.31
  • io.js: it shipped the npm client and promised releases “compatible with the npm ecosystem.”32 But a separate company ran that registry.
  • OpenTofu: it built registry.opentofu.org and kept short provider names like hashicorp/aws.33 Its FAQ also says plainly: “OpenTofu will not have its own providers.”34
  • RubyGems: former maintainers launched gem.coop, a gem server and mirror. But the rubygems.org registry stayed with Ruby Central.35

🧪 Check it yourself, and what the record leaves out

verified

Check it yourself: open ClassicPress’s update code on GitHub and search for api.wordpress.org. In that version, from 2026-11-14, it sits on lines 381 and 657.

unknown

ClassicPress’s committee notes record the decision, but not a full reason for it.

source-derived

The Terraform Registry’s terms now limit its use to Terraform, according to TechTarget’s report on the change.36 That’s a terms restriction instead of a technical block, and OpenTofu built its own registry anyway.

🔀 2024: a fork that kept the update channel

Pantheon, where I work, competes with WP Engine, which owns Advanced Custom Fields (ACF).

verified

On 2024-10-12, a WordPress.org news post by Matt Mullenweg said WordPress.org was “invoking point 18 of the plugin directory guidelines.”37 It then forked ACF as Secure Custom Fields. The post also said the fork removed commercial upsells and fixed a security problem. It blamed WP Engine’s legal attacks for a rare situation. ACF sites still updating from WordPress.org received the fork through the existing listing, by automatic or manual update.38 Guideline 18 lets the directory change plugin code “without developer consent, in the interest of public safety.”39

⚖️ 2024: what the court ordered

verified

The court record, by what each order did:

  • Relief ordered: on 2024-12-10, a preliminary injunction (Dkt. 64) ordered the ACF listing restored “as it existed as of September 20, 2024”.40
  • Limit on that relief: the same order leaves WordPress.org able to protect its site’s security under the policies in place on 2024-09-20. It’s a limit, not a ruling on the fork.41
  • Pleading stage, 2026-09-24 (Dkt. 410): the court dismissed one WP Engine computer fraud claim without leave to amend. It also let WP Engine’s antitrust claims go forward, which isn’t a finding that they’re proved.42
  • Where it stands: a 2026-09-11 order (Dkt. 373) set trial for 2027-10-19, and that date still stood on 2026-10-13.43

analysis

This is the one record in the post where a fork reached the original’s existing users through the original’s update channel. It could, because the fork’s maker ran the directory. The court then ordered the ACF listing restored.

unknown

However, the orders I read don’t decide whether the security claim was right. Today, both listings still exist.

Open source fork as moving day: two people carry a box labeled code past a house sign, mailbox and cable that stay.
Moving day. The box of code leaves, while the name, the domain and the updates stay with the house. The house and its people are fictional. Illustration made with ChatGPT at my direction from the series cast.
Text description of the moving day illustration

What this illustration shows

  • Subject: A single comic panel of moving day at a small house. It stands for an open source fork leaving its original project.
  • The house: A wooden sign by the front door reads “Name.” Meanwhile, a mailbox at the end of the walk reads “Domain.” Then a cable runs into a gray box on the wall, tagged “Updates.”
  • The people: The maintainer from another project, in a blue hoodie, carries a box labeled “Code” down a wooden ramp. Beside him, the developer rolls down the ramp in a manual wheelchair and looks back at the sign.
  • Relationships: In short, only the box leaves. The sign, the mailbox and the cable stay with the house.
  • Not shown: No real project, company or person. Finally, the scene is an illustrative story, not a record of any fork.

©️ Who can change the license after the fork

An open source fork keeps the license on the code it copied. But changing the license on future releases takes one of two things: owning the copyright, or permission from the people who do.

verified

  • MySQL: Oracle’s rule reads “Without a submitted and approved OCA, Oracle cannot integrate your contribution”.44 (OCA is the Oracle Contributor Agreement.) Earlier, its 2010 version gave Oracle joint ownership of each contribution.45
  • Terraform: HashiCorp’s agreement takes a broad license, and contributors keep ownership: “You reserve all right, title, and interest in and to Your Contributions”.46 In 2023, HashiCorp moved future product releases to the Business Source License. However, APIs, SDKs and most libraries stayed on the Mozilla license.47
  • Redis: Redis Inc moved Redis 7.4 to two source available licenses in 2024.48 Later, in May 2025, it added the AGPLv3, starting with Redis 8.49 Its contributions file says code from before 7.4 stays available under the BSD license.50
  • Backdrop: an early README says the code is “Copyright 2001 – 2013 by the original authors”.51
  • ClassicPress: GPL version 2 or later, with the WordPress contributors’ notice kept.52
  • WordPress: license.txt reads “Copyright 2011-2026 by the contributors”.53

🔑 Where the power to relicense came from

analysis

So the power to relicense came from two places: shared ownership at Oracle, and broad permission at HashiCorp and Redis. Redis’s older code was BSD, a permissive license that already lets anyone ship it inside other terms. Under the GPL, as at Backdrop, ClassicPress and WordPress, nobody can take the code proprietary alone. Instead, people can only pick a later GPL version. Both relicensing forks here, OpenTofu and Valkey, continued from openly licensed code available at the split.

🏠 The one fork that went home: io.js

verified

io.js shipped 1.0.0 on 2015-01-14. By June 2015, the Linux Foundation announced that the Node.js and io.js technical committees would merge into one.54 Then Node.js 4.0.0 arrived in September 2015, “now combined in a single codebase.”55

Ownership of the name moved last. Finally, in February 2022, the OpenJS Foundation took ownership of the Node.js trademarks. Joyent had granted the foundation “a perpetual, free license” for six years before that.56

analysis

So the fork’s code line and its committee joined the merged project. Still, ownership of the name took about six and a half more years.

verified

Joyent’s 2014 trademark policy, posted at nodejs.org, listed “Confusingly similar software product names” among uses that need a license.57

In December 2014, npm’s Isaac Z. Schlueter wrote that Joyent’s chief executive had called the earlier fork repository a violation of Joyent’s trademark. The fork then took a new name.58 But I found no Joyent statement about that request itself.

❓ Questions to ask before you fork an open source project

These work for any project, and for any open source fork of it. The first five match the packing list. The last two, though, are about living with the result.

  1. Name: Who holds the trademark, and does the policy mention forks?
  2. Domain: Who holds the main domain?
  3. Updates: Which server do sites ask for updates, and can a site change that address?
  4. Registry: Who runs the package registry, and what do its terms allow?
  5. Copyright: Who holds it, and is there a contributor agreement?
  6. Switching: What would a site have to test, back up and change to switch, and how would it switch back?
  7. Upkeep: Who reviews security fixes, signs releases and pays for the servers?

You can start an open source fork of the code in an afternoon. But the rest of this list takes longer.

🙋 Frequently asked questions

Can an open source fork use the original project’s name?

Usually not. In this record, every fork rebuilt its name. Still, a trademark owner can grant permission, and Redis’s policy lets a fork state its origin.

What does a fork keep for free?

An open source fork keeps the code, because the license grants that to anyone who gets it. The git history comes along when the project publishes it, as it did for four of these forks.

Can a fork and its original merge again?

Yes. The io.js open source fork and Node.js merged in 2015 under the Node.js Foundation.

Next up, 2.4 asks whether sponsorship buys a seat.

Footnotes (58)
  1. Free Software Foundation. “What is Free Software?” GNU Operating System. https://www.gnu.org/philosophy/free-sw.html. Accessed 2026-11-13. ↩︎
  2. 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. ↩︎
  3. European Commission. “Mergers: Commission clears Oracle’s proposed acquisition of Sun Microsystems.” IP/10/40. 2010-01-21. https://ec.europa.eu/commission/presscorner/detail/en/IP_10_40. Accessed 2026-11-14. ↩︎
  4. 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. ↩︎
  5. Mambo Foundation. “Miro transfers Mambo Copyright and Trademark to the Mambo Foundation.” Mambo Foundation newsroom. 2005-08-23. Archived 2005-12-23. https://web.archive.org/web/20051223150908/http://mambo-foundation.org/content/blogcategory/1/51/. Accessed 2026-11-14. ↩︎
  6. io.js. “FAQ.” iojs.org source repository. https://raw.githubusercontent.com/nodejs/iojs.org/master/content/en/faq.md. Accessed 2026-11-14. ↩︎
  7. 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. ↩︎
  8. 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. ↩︎
  9. OpenTofu. “The OpenTofu Manifesto.” opentofu.org. https://opentofu.org/manifesto/. Accessed 2026-11-14. ↩︎
  10. Redis. “Redis Adopts Dual Source-Available Licensing.” Redis blog. 2024-03-20. https://redis.io/blog/redis-adopts-dual-source-available-licensing/. Accessed 2026-11-14. ↩︎
  11. 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. ↩︎
  12. 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. ↩︎
  13. 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. ↩︎
  14. Matt Mullenweg. “Forking is Beautiful.” WordPress.org News. 2024-10-10. https://wordpress.org/news/2024/10/spoon/. Accessed 2026-11-14. ↩︎
  15. 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. ↩︎
  16. 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. ↩︎
  17. 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. ↩︎
  18. Open Source Matters. “Introducing Joomla! 1.0.” joomla.org. 2005-09-15. Archived 2005-09-24. https://web.archive.org/web/20050924093136/http://joomla.org:80/. Accessed 2026-11-14. ↩︎
  19. 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. ↩︎
  20. Dries Buytaert. “Drupal trademark and logo policy.” Drupal.org. https://www.drupal.org/about/trademark. Accessed 2026-11-14. ↩︎
  21. Oracle. “Oracle Trademarks.” oracle.com. https://www.oracle.com/legal/trademarks/. Accessed 2026-10-26. ↩︎
  22. Redis. “Redis Trademark Policy.” redis.io. Last updated 2026-09-15. https://redis.io/legal/trademark-policy/. Accessed 2026-11-14. ↩︎
  23. WordPress Foundation. “Trademark Policy.” wordpressfoundation.org. https://wordpressfoundation.org/trademark-policy/. Accessed 2026-11-14. ↩︎
  24. Public Interest Registry. RDAP record for mariadb.org. https://rdap.publicinterestregistry.org/rdap/domain/mariadb.org. Accessed 2026-11-14. ↩︎
  25. 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. ↩︎
  26. MariaDB Foundation. “MariaDB Trademark.” mariadb.org. https://mariadb.org/about/trademark/. Accessed 2026-11-14. ↩︎
  27. 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. ↩︎
  28. 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. ↩︎
  29. ClassicPress. “Committee meeting: a focus on v1 roadblocks.” ClassicPress. 2018-09-08. https://www.classicpress.net/committee-meeting-a-focus-on-v1-roadblocks/. Accessed 2026-11-14. ↩︎
  30. 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. ↩︎
  31. ClassicPress. “update.php,” commit b577653e. GitHub. https://github.com/ClassicPress/ClassicPress/blob/b577653eb1cf13f3bf80d4cf8e493be1b1fc5202/src/wp-includes/update.php. Accessed 2026-11-14. ↩︎
  32. io.js. “README.md” at v1.0.0, project goals section. GitHub. 2015-01-14. https://github.com/nodejs/node/blob/v1.0.0/README.md. Accessed 2026-11-14. ↩︎
  33. OpenTofu. “Provider Requirements.” OpenTofu documentation. https://opentofu.org/docs/language/providers/requirements/. Accessed 2026-11-14. ↩︎
  34. OpenTofu. “FAQ.” opentofu.org. https://opentofu.org/faq/. Accessed 2026-11-14. ↩︎
  35. Gem Cooperative. “gem.coop.” https://gem.coop/. Accessed 2026-10-26. And Ruby Central board. “A New Chapter for Ruby Central.” 2026-04-16. https://rubycentral.org/news/a-new-chapter-for-ruby-central/. Accessed 2026-10-27. ↩︎
  36. TechTarget. “Terraform Registry TOS change stokes open source ire.” 2023-10-11. https://www.techtarget.com/searchitoperations/news/366555192/Terraform-Registry-TOS-change-stokes-open-source-ire. Accessed 2026-11-14. ↩︎
  37. Matt Mullenweg. “Secure Custom Fields.” WordPress.org News. 2024-10-12. https://wordpress.org/news/2024/10/secure-custom-fields/. Accessed 2026-11-14. ↩︎
  38. 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. ↩︎
  39. 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. ↩︎
  40. 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. ↩︎
  41. 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. ↩︎
  42. WPEngine v. Automattic, Dkt. 410, Order re Motions to Dismiss. 2026-09-24. https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.410.0.pdf [PDF]. Accessed 2026-10-26. ↩︎
  43. 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. ↩︎
  44. Oracle. “Contributing to MySQL.” MySQL. https://dev.mysql.com/community/contributing/. Accessed 2026-11-14. ↩︎
  45. Oracle. “Oracle Contributor Agreement,” version 1.5. 2010. https://openoffice-org.staged.apache.org/licenses/oca.pdf [PDF]. Accessed 2026-10-26. ↩︎
  46. HashiCorp. “Contributor License Agreement.” hashicorp.com. https://www.hashicorp.com/cla. Accessed 2026-11-14. ↩︎
  47. 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. ↩︎
  48. Redis. “Redis Adopts Dual Source-Available Licensing.” Redis blog. 2024-03-20. https://redis.io/blog/redis-adopts-dual-source-available-licensing/. Accessed 2026-11-14. ↩︎
  49. Rowan Trollope. “Redis is now available under the AGPLv3 open source license.” Redis blog. 2025-05-01. https://redis.io/blog/agplv3/. Accessed 2026-11-14. ↩︎
  50. Redis. “REDISCONTRIBUTIONS.txt.” GitHub, redis/redis. https://github.com/redis/redis/blob/unstable/REDISCONTRIBUTIONS.txt [TXT]. Accessed 2026-11-14. ↩︎
  51. Backdrop CMS. “README.md” at commit 2136eff0, 2013-09-16; the line was added 2013-09-13 in commit 32f99965, “Restore copyright information.” GitHub. https://github.com/backdrop/backdrop/blob/2136eff03f38930a8c9b04ee32737c174661aaa5/README.md. Accessed 2026-11-14. ↩︎
  52. ClassicPress. “license.txt,” develop branch. GitHub. https://github.com/ClassicPress/ClassicPress/blob/develop/src/license.txt [TXT]. Accessed 2026-11-14. ↩︎
  53. WordPress. “license.txt,” wordpress-develop trunk. GitHub. https://github.com/WordPress/wordpress-develop/blob/trunk/src/license.txt [TXT]. Accessed 2026-11-13. ↩︎
  54. 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. ↩︎
  55. 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. ↩︎
  56. 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. ↩︎
  57. Joyent. “Node.js Project Trademark Policy.” PDF, created 2014-06-12. nodejs.org, archived 2014-12-06. https://web.archive.org/web/20141206005744/http://nodejs.org/trademark-policy.pdf [PDF]. Accessed 2026-11-14. ↩︎
  58. Isaac Z. Schlueter. “io.js.” blog.izs.me. 2014-12-08. https://blog.izs.me/2014/12/iojs/. Accessed 2026-11-14. ↩︎

FIELD NOTES

Get the next field note in your inbox

A weekly note from the open-source frontier — what I’m building, breaking, and learning. No spam, no AI summaries, real writing from a real human.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Your post must include a link to this post.

How does this work?
Write a response on your own website and include a link to this post. Then submit your response’s URL here. Your response may appear here after moderation. To update or remove it, edit or delete your original post and submit the same URL again. Learn more about Webmentions.