Is Matt Mullenweg defending WordPress or sabotaging it?
Matt Mullenweg faces backlash for criticizing WP Engine, leading to a legal dispute and allegations of extortion. Critics highlight his conflict of interest, raising concerns about WordPress's future.
Read original articleMatt Mullenweg, the co-founder of WordPress, is facing scrutiny over his recent actions that some perceive as detrimental to the open-source community he helped create. Tensions escalated after Mullenweg criticized WP Engine, a major hosting provider, for not contributing sufficiently to the WordPress ecosystem. His remarks at WordCamp and subsequent blog post labeled WP Engine as a "cancer to WordPress," leading to a legal dispute where WP Engine accused Mullenweg of using his control over WordPress trademarks to extort money. Mullenweg allegedly offered to soften his public stance if WP Engine agreed to pay Automattic, his for-profit company, a percentage of its revenue. Critics argue that Mullenweg's dual role as a nonprofit founder and a CEO of a competing corporation creates a conflict of interest, undermining the principles of the open-source community. The situation has raised concerns about the future of WordPress and its community, with many feeling that Mullenweg's actions prioritize personal and corporate interests over the collective well-being of the WordPress ecosystem.
- Matt Mullenweg's recent comments have sparked controversy within the WordPress community.
- He criticized WP Engine for not contributing to the open-source ecosystem, leading to a legal dispute.
- Allegations of extortion have emerged, with Mullenweg reportedly offering to alter his public statements for financial compensation.
- Critics highlight a conflict of interest due to Mullenweg's dual roles in a nonprofit and a for-profit company.
- The ongoing situation raises concerns about the future of WordPress and its community dynamics.
Related
If WordPress is to survive, Matt Mullenweg must be removed
Matt Mullenweg faces criticism for pressuring WP Engine after a rejected licensing proposal, with calls for his removal from leadership due to concerns over ethical conduct affecting the WordPress community.
The messy WordPress drama, explained
Matt Mullenweg criticized WP Engine for exploiting the WordPress ecosystem, leading to legal threats and access restrictions for its customers, while the community remains divided over the implications for WordPress's future.
Matt Mullenweg: 'WordPress.org just belongs to me'
Matt Mullenweg asserts control over WordPress and is in a lawsuit with WP Engine over trademark infringement and inadequate support, raising concerns about the impact on the open-source community.
The Pettiest Drama in the Tech World Is Taking Place at... WordPress?
Matt Mullenweg criticized WP Engine for exploiting WordPress, leading to a cease-and-desist letter and a lawsuit from WP Engine against Mullenweg and Automattic, raising concerns about conflicts of interest.
About that brawl between the WordPress co-founder and WP Engine
The conflict between Matt Mullenweg and WP Engine escalated over accusations of exploitation, leading to legal actions, internal dissent at Automattic, and broader tensions in the open-source community.
- Matt, under various guises, is shifting blame to different entities that are effectively himself.
- Automattic is Matt. Matt is the CEO of Automattic.
- The WordPress Foundation is, effectively, Matt.
- The problem is Matt. Maybe he's right about WP Engine, but the way he has and continues to handle everything has been disastrous.
If somebody doesn't fork WordPress soon, it will be decades before WordPress is purged from the web and in the meantime a lot of those remaining sites will devolve into bot-net members and malware hosts.
Because that's how Mullenwegs crusade is going to end: With the death of WordPress.
> you can just continue to use WordPress without any impact
That's nice—
> on any other host than WP Engine
That's the whole point, Matt.
WordPress is itself a fork of a previous open-source GPL license. Meaning Mullenweg couldn't make it close source even if he wanted to.
He makes it pretty clear that he thinks all of WordPress should belong to him. So he's intentionally closing out the ecosystem by making it as hostile to third-parties as possible.
As some like to say, "the cruelty is the point".
No one with money at stake will allow their Wordpress install to be subject to random sabotage by the whims of unhinged behavior. I don't know if a fork is the solution, but Matt can't have admin access to so many installs.
It doesn’t matter what he thinks he’s doing (my belief is that he’s just frustrated that someone else is profiting more than he thinks is “fair” and is using everything else as a cover, but maybe he does actually believe WPE is causing harm).
But here’s the problem I have with the whole position he’s taken. If this were actually about “Wordpress the project/community” the payment would be to the non profit not his personal for-profit company. If it was about trademarks, he should not have made the prior claims that the trademarks were not the property of his for profit when they functionally are. He would have not misrepresented the non profit as an independent entity (a fiction demonstrated clearly by the requirement to compensate his for profit).
if WPEngine is not contributing a “fair” amount to an open source project that sucks, but that’s always a risk if you want to build a for profit business on an OSS basis. But you can’t then unilaterally and retroactively change the rules later on, and act like it’s a “protecting the community” nonsense. You sure as shit don’t get to just engage in explicit extortion.[1]
Again, maybe wpengine was not contributing a fair share back to “the community”, but that’s just how OSS works, not everyone is a contributor.
[1] something I’ve found myself wondering about: my understanding is that under the law a contract signed under duress is not valid. Given the threats Matt was making, if WPE had signed it, would they be able to then go to court and say it was not enforceable due to the threat being leveled at them?
But then I regained my senses... I don't have any kind of reputation or extensive proof of accomplishments or character outside of my resume and real-life social circle. Any company that would cold-contact someone like me is 100% dealing with either abnormally low offer acceptance or abnormally high employee turnover, or both. I also remember reading (on Reddit and such) from previous employees that the CEO was best described as "mercurial."
There were enough bright waving red flags that I did not bother to respond.
(Not that the previous model was foolproof, but they were usually a lot easier to get rid of when they went rogue; for instance see Léo Apotheker.)
But, obviously, this is currently looking like a disaster of PR and community.
So, hopefully they can figure out:
* solutions to the open source sustainability challenges,
* a solution to the harm done by recent mistakes, and
* how to try to prevent mistakes like that from happening again.
Matt responds: > WP Engine is a “competitor”, but so is every other web host in the world. Automattic and WordPress.org have had good relations with all the others for 21 years. WordPress.org recommends a number of hosts.
It seems Matt is forgetting his "friendly" spat with GoDaddy a few years ago.
Matt continues: > His criticism of certain practices focuses on maintaining the platform’s integrity and open-source commitment to ensure the community can grow further with sustainable investments.
Let's assume this is all true. It doesn't change the fact that he's attacking a direct competitor.
Matt continues: > Silver Lake is far wealthier than Matt or Automattic.
This is how you know that Matt wrote the response. It's the same ego defending behavior that he used when responding to DHH.
Matt is very, very bad at PR. It's really time he learns that and lets others take over those roles. And it's time he learns to shut up. He hurts more than he helps.
Maybe its a newfound persona, maybe its a new marketing angle, or maybe its just someone going a little unhinged. But all isn’t right in the WordPress world
Related
If WordPress is to survive, Matt Mullenweg must be removed
Matt Mullenweg faces criticism for pressuring WP Engine after a rejected licensing proposal, with calls for his removal from leadership due to concerns over ethical conduct affecting the WordPress community.
The messy WordPress drama, explained
Matt Mullenweg criticized WP Engine for exploiting the WordPress ecosystem, leading to legal threats and access restrictions for its customers, while the community remains divided over the implications for WordPress's future.
Matt Mullenweg: 'WordPress.org just belongs to me'
Matt Mullenweg asserts control over WordPress and is in a lawsuit with WP Engine over trademark infringement and inadequate support, raising concerns about the impact on the open-source community.
The Pettiest Drama in the Tech World Is Taking Place at... WordPress?
Matt Mullenweg criticized WP Engine for exploiting WordPress, leading to a cease-and-desist letter and a lawsuit from WP Engine against Mullenweg and Automattic, raising concerns about conflicts of interest.
About that brawl between the WordPress co-founder and WP Engine
The conflict between Matt Mullenweg and WP Engine escalated over accusations of exploitation, leading to legal actions, internal dissent at Automattic, and broader tensions in the open-source community.