In recent weeks, WordPress – the platform responsible for powering nearly half the websites on the internet – has been embroiled in a dramatic controversy that has shocked the web development community. This drama revolves around Matt Mullenweg, the founder of WordPress and CEO of Automattic, and WP Engine, one of the largest WordPress hosting platforms. Accusations of greed, legal battles, and questionable decisions have left people questioning whether Mullenweg is losing his grip on reality or if he's simply defending the sanctity of open source.
Let’s break down the timeline of events to figure out what’s going on and decide for yourself – is Matt Mullenweg a tyrannical leader, or a misunderstood open-source advocate?
The Background: WordPress, Automattic, and WP Engine
WordPress is an open-source software project, licensed under the GNU General Public License, which allows anyone to modify and use the software freely, as long as they apply the same license to any derivatives. However, while WordPress code is free, its trademarks (including the "WordPress" name and logo) are owned by the WordPress Foundation, a charitable organization founded by Mullenweg. Automattic, Mullenweg's for-profit company, runs WordPress.com, a commercial service offering hosting and support.
One of Automattic’s largest competitors in the WordPress hosting space is WP Engine, a company that also generates hundreds of millions of dollars providing WordPress hosting services. The two companies have had a long-standing tension, especially since Automattic sold its stake in WP Engine in 2018. Things came to a head recently when Automattic decided to enforce its trademark in a way that sparked outrage.
September 20: The Trademark Showdown
On September 20, 2024, Automattic sent a legal document to WP Engine demanding that they pay an 8% royalty on their gross revenue for the use of WordPress trademarks. The argument? Automattic claimed WP Engine was making millions off WordPress while contributing little back to the nonprofit side of the ecosystem. They also pointed out that WP Engine was improperly using WordPress trademarks in its marketing materials and payment plans, potentially misleading customers.
For WP Engine, this was an unexpected and aggressive move. The company refused to sign the agreement, and things quickly spiraled from there.
September 21: Mullenweg Takes the Stage
The very next day, Mullenweg took the stage at the WordCamp US conference, where he made his feelings about WP Engine clear. He called WP Engine "a cancer to WordPress" and criticized private equity firms (like Silver Lake, which owns WP Engine) for “hollowing out” open-source communities for profit.
This public statement shocked many in the WordPress community, especially considering the close business ties the two companies once shared. But the fireworks were just getting started.
The Legal Battle Intensifies
As soon as WP Engine refused Automattic’s terms, the situation escalated. Automattic slapped WP Engine with a cease-and-desist letter, demanding they stop using the WordPress trademarks in ways that violated their guidelines. WP Engine fired back with its own cease-and-desist letter, accusing Mullenweg of slander and making “salacious and outrageous” statements.
By September 25, things had escalated even further. WP Engine was officially banned from wordpress.org, meaning that WordPress installations on WP Engine’s servers could no longer access updates or plugins from the WordPress.org repository. This action directly impacted thousands of developers and users relying on WP Engine for hosting and sparked even more outrage in the community.
The "I Am Not Affiliated with WP Engine" Checkbox
The controversy reached new heights when wordpress.org introduced a new checkbox in the login screen, labeled “I am not affiliated with WP Engine in any way financially or otherwise.” Without checking this box, users couldn't log in. The checkbox was styled with a CSS class ominously named "login-lawsuit," making it clear that this was in direct response to the ongoing legal battle.
WP Engine was forced to issue statements to clarify that their users and customers were not “affiliates” in the traditional sense, as the checkbox wording implied.
The Fallout: Forking WordPress?
The situation has caused division within the WordPress community. Some support Mullenweg's stance, arguing that WP Engine is exploiting WordPress for profit while giving little back. Others see Mullenweg’s actions as petty and vindictive, especially given Automattic’s own commercial interests.
Some developers have even started discussing the possibility of forking WordPress, creating a new version of the software free from Automattic’s influence. This would be a monumental shift in the open-source world, given WordPress’s dominance.
Conclusion: No Heroes in This War
At the end of the day, it’s hard to find a hero in this story. On one side, you have Matt Mullenweg, the man who built WordPress, but who now appears to be wielding his power in ways that some see as destructive. On the other, you have WP Engine, a company backed by private equity firms that prioritize profit over community.
The only real losers in this battle are the WordPress users – developers, content creators, and business owners who rely on WordPress every day to power their websites. As the lawsuits and legal wrangling continue, they’re the ones who stand to suffer the most from this conflict.
Only time will tell how this drama unfolds, but one thing is for sure: the WordPress community won’t be the same when it’s all over.
That's the latest in the ongoing WordPress drama – what do you think? Is Matt Mullenweg protecting open-source principles, or has he gone too far?