They are allowed to do this because Automattic owns the trademark along with WordPress Foundation
Something I also find interesting is the WordPress foundation trademark terms were changed a couple days ago. Using "WP" was okay, to now calling out "WP Engine" specifically as being confusing: https://www.diffchecker.com/tJ29tGIn/
That’s the most childish thing out of this whole debacle. It is extremely clear that you cannot just change your terms 10 years after a company has been created in order to exclude it. Any judge would throw that case out of the window in 10 seconds.
Though I don’t know how much merit his original post had.
"WP Engine accused Automattic and Mullenweg of not keeping their promises to run WordPress open-source projects without any constraints and giving developers the freedom to build, run, modify and redistribute the software."
What promises? People make and release software using the GPL "copyleft" license because they enjoy doing so. Everybody is free to cease doing that if they no longer enjoy it. If it no longer brings them joy. And if it is costing measurable quants of money for the non-profit .org to provide back-end services to the $100 billion dollar corporation who is profiting from using the core plugins and themes etc.
Perhaps 8% of gross is a bit much, but I don't see them counter offering 1% and a way to work up over time. They were purchased for $250 million in 2018 so they have plenty o' cash. Bad faith wpengine for trying to strip-mine WordPress like that.
I struggle with this argument because so much SaaS follows this model with self-hosted community editions. It's not like .com is trying to sell you a proprietary self-hosted version.
> People are often confused about the differences between WordPress.com and WordPress.org because they sure sound similar. This workshop highlights the key differences between .Org and .Com.
— https://learn.wordpress.org/tutorial/what-is-the-difference-...