-
AuthorPosts
-
-
-
You can negotiate in good faith and work that out as best as possible, or you can refuse and experience the consequences of not agreeing to play fair. WPEngine didn’t even negotiate in good faith, they strung Automattic along, and then acted surprised when a hard deadline was communicated and a cease and desist was delivered.
There’s trademark law and nominative fair use, and then there’s taking advantage of past relationships, negotiations, and stringing along that deepens the divide and creates the need for a serious copyright infringement response. Trying to blame the other party and playing the victim isn’t going to alleviate the legal ramifications of the past actions and the consequences of neglecting to act in the best long term interests during those negotiations.
Sad to say it sounds like there’s a lot of legal terms being thrown around that don’t fit in an initial lawsuit that amounts to defamation, as there isn’t a legal grounding in who is deemed a monopoly or not, first amendent speech versus extortion, etc.
-
-
-
Since I started using WordPress in 2010 I have been fascinated with it’s story.
I have watched and read about the ebbs and flows about how it (the entire ecosystem) works and it’s management.
The fact that it just gets better and better to use, the freedoms and wealth generation it has created is, in history, quite unrivaled.
So many have benefited from using WordPress.org for free and it has helped many, many startups with only some basic rules to follow.
I have seen Matt say a few things that I may have put differently, done a few things I might have done differently, especially with crystal clear hindsight, but have always marveled at how much the man has contributed.
With all this going on it all continues to function and improve. We will all update to the latest version of WordPress and enjoy the benefits, and will do the same again in the New Year.
Well done with your life to date Matt.
-
-
WordPress is an open source GPL licensed software CMS. You can’t sue me for typing in “WordPress” in this comment nor can you sue me for using WP software on my host; even if it is “altered.” That is what the credo of FOSS is all about. Use to create something wonderful, as the quote goes.
WPEngine is losing thousands of customers every day. Customer are moving their site to another host—whom I’m sure, use WP installed by Softaculous or some other installer. So what is the logic for moving away from WPE. Yes WPE has its own “version” of WP but that is exactly what Open Source allows.
Yes the host is making money from WP and as said, they may not be contributing “enough” to [Matt] but, bottom line is that hosts like WP Engine and Siteground and Cloudawys and Kinsta (I could go on all day) use WP to make money with. So in the bigger picture of who’s hurting who: Any host brings “business” and gravity to WordPress. Regardless of any abilities to contribute. Hosting that many websites IS A CONTRIBUTION.
-
-
The updated legal complaint by WP Engine against Automattic and Matt Mullenweg highlights significant tensions in the WordPress ecosystem. It’s a reminder of the complexities in balancing business interests within open-source communities. Hopefully, this situation encourages constructive dialogue and a resolution that prioritizes the platform’s growth and the community’s well-being.
-
The Mullenweg bootlickers are out in force, and it wouldn’t surprise me if these were alt accounts from Mullenweg himself.
The fact is that WordPress itself operates under the GNU Public License. It’s open source software, and WPE is under no obligation to contribute to the source code that Mullenweg has already destroyed with his inept opinions about software architecture.
This is nothing more than a case a megalomaniacal moron attempting to extort a company that was able to capitalize on a piece of software that Mullenweg himself was too stupid to figure out how to monetize. Wrapping up his software with cutesy, meaningless catchphrases like “Code is Poetry” doesn’t change the fact that Mullenweg is incompetent at best, and dangerously narcissistic at worst.
In all likelihood, he’s both and I hope WPE buries him in litigation for the foreseeable future until he steps down to allow for more intelligent and forward-thinking direction.
https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html#SEC1
-
This legal dispute between WP Engine and Automattic underscores the challenges of balancing competition, collaboration, and community within the open-source ecosystem. While Automattic’s defense highlights the broader mission of WordPress and the importance of safeguarding its values, WP Engine’s allegations raise serious questions about the interplay of trademarks, antitrust concerns, and the ethics of competition in a shared ecosystem.
WP Engine’s claims of anticompetitive behavior and trademark misuse touch on critical issues for the open-source community, particularly when it comes to fostering innovation and ensuring fair opportunities for contributors and businesses. On the other hand, Automattic’s framing of their actions as necessary to defend WordPress’s core principles speaks to the tension between preserving community standards and addressing perceived threats.
This case could set an important precedent for how open-source projects navigate disputes between major players while maintaining the ethos of transparency, collaboration, and freedom that defines the movement. The outcome will likely have far-reaching implications for the WordPress ecosystem and similar communities, emphasizing the need for clear boundaries, shared values, and responsible leadership.
-
As someone who’s been following the WordPress ecosystem for years, this situation is quite concerning. It’s disheartening to see two major players in our community locked in such a serious legal battle. The irony of Matt’s previous endorsement of WP Engine’s name usage versus the current situation really stands out. I sincerely hope both parties can find a resolution that doesn’t harm the broader WordPress community and the open-source values we all benefit from. This kind of conflict could have lasting impacts on everyone who relies on WordPress for their businesses.
-
-
AuthorPosts
- You must be logged in to reply to this topic.
