Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Matt Mullenweg commented that the conflict he started could eventually lead to the shutdown of WordPress.org. He argued that the only way to end the conflict was for WP Engine to drop its lawsuit, which would have the effect of allowing Mullenweg to continue his campaign to put WP Engine out of business.
A WordPress user who has published nearly 600 free WooCommerce guides and 500 newsletters over the past twelve years has called on Matt Mullenweg to question the instability he’s caused, saying it causes instability.
He chirped:
“Darling
@fotomat,We love WordPress. It’s not just software; it’s how thousands of developers, freelancers and small agencies make money. We don’t have millions like you—every change, every piece of WPdrama costs us time, clients, and money.
We need stability. We need to focus on building, supporting and growing the business, not worrying about the next big upheaval or leadership conflict. We are moving towards clarity, cooperation and transparency.
Consider pausing the current direction to listen. The community wants a strong future for WordPress — one where everyone from contributors to top sponsors can work together without fear of losing what we’ve built.
We don’t ask that lightly. Our life depends on it.
Thanks.”
Matt Mullenweg insisted that the conflict can only end if WP Engine drops its lawsuit, which was filed in response to the conflict he initiated.
Mullenweg insisted that WP Engine must drop its lawsuit:
“All I do is defend the long-term health of WordPress.
The lawsuits can only be dismissed by WPE, since it initiated them.”
Mullenweg added the following twitter:
“The lawsuits will last for years and could bankrupt me or force me to shut down WordPress.org. It also takes a lot of time — there are no ‘lawyers working on it’.”
Mullenweg subsequently chirped that the lawsuits could last two more years:
“The cases will stretch to the 26th and 27th, so it’s hard to say what the environment will be or what the court will order.”
Mullenweg’s announcement, which claimed that WP Engine’s defense suit could potentially shut down WordPress.org and drag on for years, was not well received. One travel writer even rhetorically asked if they should migrate to another CMS.
Those looking for a sign that the conflict that Mullenweg had started might end sooner rather than later were disappointed. Mullenweg seems to be suggesting that only WP Engine can end the conflict by dropping their defensive suit and allowing Mullenweg to continue its attacks designed to put them out of business. AND federal judge ruled against Matt Mullenweg granting WP Engine’s request for a preliminary injunction to block its attacks on WP Engine.
Referee he specifically disagreed with Mullenweg’s lawyers:
“The defendant’s arguments in opposition do not impose a different conclusion.
Defendants’ argument that the interference alleged by WPEngine consisted of actions that they had the right to take no better prices.
… The conduct described at length above—including the termination of WPEngine’s access to WordPress, the disruption of the ACF plugin, and the additional burdens imposed on WPEngine’s customers, such as the promise of filing—demonstrates that WPEngine has a significant interest in obtaining preliminary injunctive relief.
Defendants’ arguments in opposition do not establish that they will suffer any prejudice that outweighs WPEngine’s interest in obtaining relief. …Requiring defendants to restore access under those conditions while this action is pending represents a minimal burden.”
AND discussion on Reddit about Matt’s remarks about WordPress.org shutting down was mostly negative.
Typical Posts:
“Probably the most shocking thing to me at this point is that no one seems to be able to reason with Matt.”
“I’m personally moving my sites to Drupal or ClassicPress, but haven’t decided yet.”
“I can’t imagine a worse fate than to be swallowed up by years of multi-million lawsuits. Not to mention suffocating his baby and alienating his fans, admirers and loyal customers. Matt was in a position to just relax and enjoy his wealth and fame, but he chose another path.
It also had the ability to slowly pressure perceived “freelancers” like WPEngine and watch them squirm without recourse.”
“As a Drupal focused agency – this is simply excellent.
As someone who cares about the sustainability of open source efforts and cares about all my colleagues who make a living from WP. It’s heartbreaking to watch Matt threaten BILLIONS of dollars in livelihoods like this.”
The fact that an entire subreddit was created containing all the discussions about the conflict that Mullenweg started shows how concerned the WordPress community is about what Mullenweg did. It’s a major topic of conversation, and it’s largely unsympathetic to Mullenweg.
Featured Image Shutterstock/Studio Romantic