If WordPress is to survive, Matt Mullenweg must be removed
A backlash is growing over the WordPress co‑founder’s attempt to pressure hosting provider WP Engine using trademark threats and by temporarily cutting its customers off from WordPress.org updates. Commenters argue that even if WP Engine is a free‑rider on the open‑source ecosystem, weaponizing the WordPress trademark and infrastructure against a competitor—and thereby harming uninvolved site owners—undermines trust in the project’s governance. The broader debate centers on how much commercial users “owe” to open source, the legal and ethical limits of trademark enforcement, and whether control of key community infrastructure should remain so tightly tied to a single for‑profit leader.
Tone and Conduct of WordPress Leadership
- Many see the founder/CEO’s posts and livestream as an impulsive, “unhinged” escalation unbecoming of someone stewarding a major open‑source project and a large company.
- Others argue he’s long been generous to the ecosystem and is justified in finally drawing a hard line, even if the optics are bad.
- Some commenters suggest he’s having a public breakdown or at least a serious lapse in judgment; a minority interpret it as principled, if clumsy, defense of the project.
Trademark, Licensing, and Governance
- Big debate over whether WP Engine’s branding (“Core/Essential/Enterprise WordPress”, “Most Trusted WordPress …”) crosses from nominative use into trademark infringement.
- Several note the unusual structure: a nonprofit owns the trademark but gives an exclusive commercial license to a for‑profit competitor run by the same person, creating conflicts of interest.
- There’s disagreement on whether long‑standing non‑enforcement against many hosts weakens the current trademark case.
- Some worry the nonprofit and for‑profit are too entangled, potentially raising ethical or even regulatory issues.
“Freeloading” vs. Open‑Source Norms
- One camp: large companies profiting directly from WordPress (like WP Engine) have a moral duty to contribute money or engineering time; refusing while consuming free infrastructure makes them leeches.
- Opposing camp: open‑source licenses don’t require this; you can’t retroactively impose a “tax” (e.g., 8% of revenue) or use trademarks and infrastructure as leverage. Otherwise it looks like extortion, even if not criminal.
Impact on Users and Ecosystem Trust
- Strong criticism of cutting WP Engine customers off from the official plugin/theme/update APIs with little notice, harming nontechnical nonprofits and small businesses who did nothing wrong.
- Others reply that sites keep running, WP Engine could host its own mirrors, and customers can move hosts.
- Broader concern: if access to critical infrastructure can be withdrawn at one person’s whim, WordPress.org is a dangerous single point of failure.
Views on WP Engine and Article Bias
- Several dislike WP Engine’s business practices and private‑equity ownership, and think criticism underplays that.
- Others argue the blog post was transparent about prior employment and focused correctly on WordPress governance, not on defending WP Engine per se.
Meta: Future of WordPress
- Some commenters hope this forces decentralization (alternate repos, mirrors) or even a move away from WordPress.
- Others insist WordPress will outlast this drama, and that viable non‑proprietary replacements are limited.