The blocked resources in question? Automatic security and features updates and plugin/theme repository access. Matt Mullenweg reasserted his claim that this was a trademark issue. In tandem, WordPress.org updated its Trademark Policy page to forbid WP Engine specifically (way after the Cease & Desist): from “you are free to use [‘WP’] n any way you see fit” to a diatribe:
The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.
https://techcrunch.com/2024/09/26/wordpress-vs-wp-engine-drama-explained attempts to provide a full chronology so far.
Edit:
The WordPress Foundation, which owns the trademark, has also filed to trademark “Managed WordPress” and “Hosted WordPress.” Developers and providers are worried that if these trademarks are granted, they could be used against them.
Yeah, open source licenses don’t entitle you to use trademarks.
This looks pretty bad to me.
Like JohnEdwa said, using a trademark to refer to someone else’s product is considered nominative fair use: “referencing a mark to identify the actual goods and services that the trademark holder identifies with the mark.”
They’re very obviously using the trademark in a manner that implies endorsement.
That is absolutely trademark infringement.
At most, they just ambiguously used “Powered by WordPress Experts” once. I don’t see how the evidence misleads people into thinking there was an endorsement.
IMO, dumb people confuse stuff all the time, like the Minecraft Gamepedia with the Minecraft Wikia back then. The meager amount of evidence presented does not convince me that WP Engine has done any actual harm to the WordPress brand.
But yeah, the smart way out would’ve been adding a “WP Engine is not associated with WordPress.org”, at least one below the “WP ENGINE®, VELOCITIZE®, TORQUE®, EVERCACHE®, and the cog logo service marks are owned by WPEngine, Inc.” footer. All in the past now, though. At the best both companies are tomfools.
They explicitly call their engine Wordpress more than once in those examples. You cannot do that.
Yes they can. It’s actually WordPress, so it’s nominative.
No, they can’t, because no, it isn’t. That’s what trademarks are for. You can’t use a trademarked name to refer to your competing product.
Open source projects are generally permissive in terms of people repackaging their code for distribution for different platforms within reasonable guidelines, but even that is a sufficient change that they aren’t obligated to allow their trademarks to be used that way.
It is no longer Wordpress once it’s modified. That’s what trademark is for.
I think we should agree to disagree that it was modified enough here.
Wow Matt really looking bad on this one. This just reeks of trying to push out a major business competitor to wordpress.com and abusing control over wordpress.org to do it.
ThePrimeagen invited Matt to explain what’s going on.
TL;DW Matt’s claim is that he tried to get WP Engine to pay for a Trademark license (or whatever it’s called - I’m recalling from watching yesterday), over several months, and they tried to legally block him in every way. Their self-claimed contributions to Wordpress were (as he tells it) that they held conferences where they promoted their own stuff only - code contributions have been minimal.
So the combination of not willing to pay for the trademark + not contributing back (not in code, not in helping the community) is Matt’s reasoning for blocking them from using Wordpress’ resources.
He also mentioned that he has good relations with other Wordpress hosts, so it’s not like he’s trying to block anyone else from hosting, but they were all willing to pay for the use of the Trademark (and/or contribute back).
This is accurate, but also, “minimal” here is 40 hours of code contributions per week compared to Automattic’s near-4000. Additionally, WP Engine is the biggest Wordpress.com competitor.
Would it be wrong to hope they manage to commit some gross act of mutual destruction, and that the outcome would be that I never have to deal with Wordpress ever again?
deleted by creator
Fuck WordPress, but also it kinda sounds like WordPress is more in the right here.
Nah. WordPress is GPL, they can’t bitch about someone else reselling it. That would be like Linus Thorvalds blocking a company that sells linux distro because he doesn’t like them.
And also wordpress is a piece of trash.
GPL doesn’t give you any rights to trademarks.
What does WP stand for then?
I must be old - it’s WordPerfect to me.
WordPress is total garbage and businesses should really stop outsourcing web development to a bunch of 3rd world outsourcing companies who hire “developers” for poverty wages that can’t even write a single line of code. Sites are getting stuffed with dozens of useless freemium plugins, everything uses jQuery, and it’s one giant security risk. Often times a static site generator can do the job just fine or use a headless CMS like payload. There are plenty of alternatives: https://jamstack.org/headless-cms/. WordPress, Drupal, Joomla, Wix, and all the other mutant leftover abominations belong in the trash and set on fire. Fucking normies and corpo boomers.
Drupal…damn it’s been years since someone mentioned Drupal. I remember it being the next big thing…
