Settlement conference On 9 July, a settlement conference was held in the court hearing the WPEngine v Automattic proceedings (proceedings that are now so well-known that there’s no need to describe them). Unfortunately, no settlement was reached. The court’s ‘Minute Entry’ records: Minute Entry for proceedings held before Magistrate Judge Laurel Beeler: Settlement Conference held on 7/9/2025. Settlement conference held today. The case did not settle. The court asks the parties to confer with their clients, including decision-makers who were not at the settlement conference, to see whether a session with principals makes sense to identify if there is a path forward short of litigation. There is a utility to discussing settlement now: the parties should have a good understanding of the timeline that led up to the litigation, and discovery is not going to change that. The court envisions a process with the decision-makers and in-house counsel only. If this is something that could work, the parties should discuss it and circle back in the next couple of weeks with their proposals on timing. …

We have no entitlement to WordPress The first thing to get out of the way, before descending into feudalism, is that we have no entitlement to WordPress. Three forces may combine to give people a sense of entitlement, but the truth is something different. The three forces The three forces are the GPL, longevity, and community: Force 1 – the GPL: Anyone who gets their hands on a copy of WordPress can do whatever they want with it as long as they comply with the terms of the GPL (and don’t do anything that, properly construed, infringes the WordPress trademarks). They can turn features off and on, host it as a SaaS offering, fork it, etc. That’s the beauty of the GPL. Force 2 – longevity: When people have been using WordPress for so long, and with so many free benefits, it’s natural perhaps to develop a feeling of ‘WordPress will always be there when I want it’. For theme and plugin developers and WordPress hosts, that includes access to WordPress.org, despite the fact that …

Question from a reader I had decided to end my posts on the Automattic-WP Engine saga but, following changes by WP Engine to its website in response to the trademark infringement allegations against them, a reader has asked for my views on why it has done this. First things first The first thing to note is that I have no contact with WP Engine on this and so my thoughts are opinion only. I could be wrong. The changes The changes WP Engine has made include: changing the hero text from “We power the freedom to create on WordPress” to “We power the freedom to create” changing the text underneath the hero text from “Build, power, manage and optimize extraordinary WordPress, WooCommerce and headless sites with the world’s #1 platform” to “Build, power, manage, and optimize your WordPress¹, Headless and WooCommerce¹ sites with the #1 hosting platform” (with the footnote ¹ linking to the disclaimer set out below) changing the text “The most trusted WordPress platform” to “The most trusted platform for WordPress” removing phrases …

I can read I am not a US trademark lawyer. I am, however, a lawyer who has practised in three jurisdictions, and I know how to read. I remain of the view that, if Automattic’s infringement claims were to go to court, nominative fair use would be one of the central issues, coupled with issues relating to confusion and alleged attempts to suggest a relationship with Automattic/WordPress.com, as well as other potential defences (on which I express no firm view). Novel issues may arise as well. In an earlier post, I proffered my preliminary view that much of the asserted trademark infringement might be categorised as nominative fair use. I should, perhaps, have said more, including that whether that defence is available would depend on a number of factors, including what each party is able to establish to the required standard (Automattic in relation to the elements it needs to establish for its claim, and WP Engine in relation to defence elements it needs to establish). Some points I do feel reasonably confident in making …

A letter, of sorts Dear WP Engine I am a long-time customer. I moved my sites to WP Engine a long time ago, and have built many sites since, due to (among other things) the security you offer (and after a site that was up-to-date was hacked on another company’s inferior hosting due to a server issue). For a range of reasons, I liked the service you provide, and I still do. Having used WP Engine for so long, I don’t want to shift off it and, unless the current problems get worse and impact site availability or performance, I have no plans to do so. Many of your customers will be aware of your cease-and-desist response to the attack on WP Engine at WCUS (personally I think it’s fair to characterise it as an ‘attack’), of Automattic’s response asserting trademark infringement, of the block on WP Engine having server-to-server access to WordPress.org, and of today’s temporary lifting of that block. I’m mindful, though, that the lifting of the block is only until “October 1, …

The WordPress trademarks With all this talk of Automattic, WP Engine, and trademarks, I thought it might help to share a table I’ve created that lists the WordPress trademarks, when they were registered, the goods and services or classes of activity they cover, the original owner, the current owner, and whether there have been any ‘assignments’ (transfers and the like). All information comes from the United States Patent and Trademark Office. Here it is (the text of the exclusive licence to Automattic is set out after the table): * The licence was (get ready for some legal verbiage): “an exclusive, fully-paid, royalty-free, perpetual, irrevocable, worldwide, sublicensable right and licence to use and otherwise exploit the trademarks identified in Exhibit A [attached to the transfer], and any and all related or similar names, marks, designs, domain names, and other rights (excluding www.wordpress.org, www.wordcamp.org and www.wordpressfoundation.org), along with all associated applications, registration and goodwill (the “Trademarks”), in connection with the hosting of blogs and websites that utilise any version or component of the WordPress open source publishing …

Hats off Hats off to Matt. Despite all the heat in the community at the moment, yesterday he turned up on ThePrimeTime for an interview with ThePrimeagen to talk about the controversy. What’s more, he did that when – clearly – he was pretty exhausted. Seven things To my mind, some of the things he said are quite telling or otherwise warrant comment. I want to focus on seven of them. 1. Confusion over ‘WP’ When asked about the recent change in the WordPress Trademark Policy (see WordPress Foundation changes Trademark Policy to criticise WP Engine) and why there had been a change to the previous statement about ‘WP’ not being protected by the trademarks and people being able to use ‘WP’ however they want, he said: “It still says that. So you can still use WP. You can, like I said, WP beginner, there’s lots of WP plugins. There’s lots of WP things. Just how they [WP Engine] were doing it is an egregious violation of trademarks. And as a trademark holder, you know, …