😱 Matt Mullenweg vs. WPEngine [Part 1]  ## Metadata - Author: [[Chris Pearson]] - Full Title: 😱 Matt Mullenweg vs. WPEngine [Part 1] - Category: #articles - Document Note: --- tags: [#WordPress, #WPEngine, #MattMullenweg] Author: Merlin Source: YouTube, Transcript of Merlin's Video Series on Matt Mullenweg vs. WP Engine Reference: [Link to the original video series](https://www.youtube.com) date created: 2024-09-27 15:45 --- # Title: Matt Mullenweg vs. WP Engine: Drama and Disputes in the WordPress Ecosystem ## Table of Contents:  - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: This article summarizes a series of disputes between Matt Mullenweg, the founder of WordPress, and WP Engine, a major managed WordPress hosting provider. The conflict involves accusations of insufficient community contributions, trademark misuse, and coercion. Automatic, Mullenweg's for-profit company, allegedly attempted to pressure WP Engine into paying substantial sums under the guise of supporting open source. WP Engine retaliated with a cease-and-desist letter, which prompted Mullenweg to block WP Engine customers' access to WordPress repositories temporarily. ## 📖 Main Content: The relationship between Matt Mullenweg, Automatic, and WP Engine has long been complicated by shared goals, conflicting interests, and competition for influence within the WordPress ecosystem. This recent dispute sheds light on the power dynamics, expectations, and governance struggles within the WordPress community. Below are detailed insights into key aspects of the conflict: ### **1. Background of the Conflict** The feud between Mullenweg and WP Engine didn't emerge out of nowhere. WP Engine, a significant player in WordPress hosting, has been accused by Mullenweg of exploiting the WordPress community without sufficient contribution to the core project. This friction dates back to earlier disputes, including a notable issue concerning the licensing of the "Thesis" theme in 2010, when Mullenweg pushed for GPL compliance across the ecosystem. - **Licensing Disputes**: Earlier clashes between WP Engine and Mullenweg involved debates about GPL licensing. In particular, WP Engine was criticized for allegedly using the "WordPress" trademark without properly contributing to its open-source project. - **Monetary Contributions and Expectations**: Mullenweg has publicly stated his belief that companies profiting from WordPress should financially support the core project or contribute code, leading to expectations that WP Engine pay a significant sum. This is part of a broader advocacy by Mullenweg for companies to fund open-source initiatives that benefit their businesses. ### **2. Coercion and Cease-and-Desist** The tipping point of this conflict was marked by Mullenweg allegedly attempting to demand payments from WP Engine in a manner perceived by WP Engine as coercive. - **Ultimatum from Matt Mullenweg**: WP Engine claims that Mullenweg issued an ultimatum: either pay a substantial sum to Automatic, or risk negative remarks during a major keynote at WordCamp US. This ultimatum was presented as "necessary support" for the community, but WP Engine perceived it as an abuse of influence. - **WP Engine's Legal Action**: WP Engine’s response was to issue a cease-and-desist letter, accusing Mullenweg of misusing his influence and making threats under the guise of community advocacy. This move was intended to prevent any defamation or perceived retaliation during the WordCamp event. ### **3. The Retaliatory Blockade** In retaliation, Mullenweg temporarily restricted WP Engine customers from accessing WordPress updates, which highlighted the extent of influence Automatic wields over WordPress infrastructure. - **Restricted Access to WordPress Updates**: For several days, WP Engine users found themselves unable to access updates to WordPress plugins and themes through their usual interfaces. This blockage disrupted service for a significant portion of the WordPress user base, triggering outrage and confusion among WP Engine customers. - **Community Response**: The response from the community was mixed. While some backed Mullenweg's decision as a stance against what they saw as freeloading, others were critical of using customers as leverage in a corporate feud. Many questioned whether such actions were appropriate for a community-driven open-source project. ### **4. Trademark Misuse Allegations** Mullenweg's argument also involved allegations of WP Engine misusing WordPress trademarks. He claimed that by using terms like "WordPress hosting," WP Engine falsely implied official affiliation with WordPress, which he found misleading for consumers. - **WordPress vs. WP**: Historically, using the term "WP" has been tolerated, but Mullenweg argued that direct use of "WordPress" for commercial gain without permission crossed a line. He referenced long-standing community guidelines regarding the trademark, pointing out that WP Engine should have known better. - **Historical Acceptance and Change of Tone**: For over a decade, this practice was widely accepted, which made the recent accusations seem like a sudden change of policy aimed specifically at WP Engine. WP Engine argued that it was being singled out, perhaps due to its rapid growth and perceived competition with Automatic. ### **5. Broader Implications for the Ecosystem** This dispute has significant implications for the broader WordPress ecosystem, affecting trust, governance, and community dynamics. - **Monopolistic Tendencies**: Mullenweg’s actions sparked concerns about the monopolistic tendencies of Automatic. Critics argue that the centralization of power around Mullenweg and his companies is a risk to the health of WordPress as an open-source platform. - **Contributor Expectations**: The dispute brings to light questions about what constitutes meaningful contribution to open-source projects. Should companies profiting from WordPress be required to contribute in a specific way, either through code or financial support? The lack of clear guidelines on contributions has led to tensions and confusion about expectations. ### **6. WP Engine's Contribution Defense** WP Engine has been trying to position itself as a responsible community member by acquiring distressed plugins and making them viable again, arguing that these actions are in service of the community. - **Distressed Plugin Acquisition**: WP Engine pointed to its track record of acquiring plugins that were no longer maintained by developers and reinvesting in them to bring them back to life. They argued that this kind of support should be recognized as a meaningful contribution to the community. - **Investment by Mullenweg**: WP Engine also highlighted the hypocrisy of Mullenweg’s demands by pointing out his initial investment in WP Engine and his endorsement of their business model at the time. They emphasized that their approach had not significantly changed since his endorsement. ### **7. The Fallout** The dispute didn’t just end with WP Engine issuing a cease-and-desist letter. It led to considerable backlash on both sides, with community members, developers, and hosting partners weighing in. - **Community Backlash**: Some members of the WordPress community were concerned that Mullenweg's actions reflected poorly on the open-source project's leadership. They feared this might create a chilling effect where companies are deterred from engaging with WordPress due to fears of coercion or conflicts with Automatic. - **Temporary Reinstatement**: Access to WordPress repositories was reinstated after a few days, but Mullenweg imposed a deadline for WP Engine to “resolve - Summary: What the heck is going on? And how did we get here? - URL: https://www.youtube.com/watch?v=C_wb01v-CA0&t=192s what's up gang WordPress news doesn't travel around the same way it used to so I don't know if you've heard about this yet but this week uh the WordPress ecosystem exploded with drama so here's the story WordPress founder Matt mullenweg has gotten himself in hot water again by making uh what I consider to be kind of a crazy stand okay and we're I'm going to go through all this for you but basically what he's done is he has attacked the most prominent WordPress adjacent hosting company in the world it's called WP engine he has attacked WP engine and says that they are not in good standing in the WordPress Community because according to Matt in his uh first public statements he said they do don't contribute back to the WordPress ecosystem in the form of uh providing code for the WordPress core I'll talk more a little bit more about what that means in a little while but uh so he says word WP engine which has huge profits it's a very successful company he says they don't give back enough to Wordpress okay there's other companies many other companies that uh have you know generated tons of money off WordPress through the years but they don't always get uh put in in the crosshairs in Matt's crosshairs and so you definitely like before you even dive into anything you have to you have to ask yourself well why is he attacking only this entity he's saying that they say they're managed WordPress hosting and that they're WordPress hosting and that they are potentially confusing to customers who might think that WP engine is WordPress but of course this this issue goes back 15 years uh back in 2010 some of you may recall that I had a big spat with Matt uh Matt in the summer of 2010 when he wanted me to put a specific type of Licensing on the thesis theme which I refused to do because I I had tons of people saying hey Chris if you put that licensing on your theme I'm going to steal it right away so that didn't seem too good I wasn't too thrilled about uh creating licensing that others could then use against me that seemed really dumb at the time since I was in the crosshairs of a lot of people it's like you don't make yourself more vulnerable when you're already being attacked that's super dumb anyhow that was an issue of coercion Matt wanted to force me to make some changes so that I was operating in the way that he wanted me to operate now there were no uh rules in the WordPress community at that time it was just sort of a loose Coalition and it was supposed to be open which is a joke which you now know if you've done this for any length of time but um so anyway he wanted to coers me to you know have certain types of Licensing and all that and then in the wake of this they started making all kinds of changes they started doing uh these word camps which were these events and they were like local there'd be one there'd be a a a US word camp there' be a European word Camp there'd be local ones like in Phoenix or you know in San Francisco or something like this there were there were there were local ones too so like a a circuit of events so he started this Circuit of events and then he said well you can't be invited you're not allowed to attend any of these if you're not in good standing so he basically makes the rules and says okay you if these people try to get in they can't get in anyone else is okay so it's a it's a closed system to try and get your open Community to behave the way you want like you should already be seeing the absurdity here but we're going to keep going so in in during that time when WordPress was making all these adjustments with word camp and everything else they also had to take a stand about trademarks and specifically trademarks concerning the usage of the word WordPress in Commerce and the big conclusion at that time was that any company selling products or Services adjacent to Wordpress stuff that helped with word you know help you run WordPress had to use could not use use WordPress fully spelled out in the name of the business or the domain name used to promote the products they had to use the abbreviation WP and say thing use verbiage like whatever for WP and you could even say for WordPress I believe that was a acceptable use at the time or when during when this was first established saying for WP or for WordPress was totally okay all right and WP engine who Matt is attacking now he they received his Blessing and funding from his company his private company automatic which builds stuff on WordPress and kind of steers the WordPress ship it's a it's a murky thing there's not supposed to be any Crossing of streams here between private and nonprofit and foundation and all that stuff but there is definitely some Crossing of streams and uh conflict of interest especially as it comes to leadership and Matt's position okay so he gave WordPress engine startup capital back in 2010 or 2011 I don't know when that money was actually exchanged and a blessing to use WP in the name because that was that was the conclusion of that whole era was you could use WP in the in the name of the business so WP engine was born WP engine became the number one managed WordPress hosting company as far as I know uh they're headquartered here in Austin Texas I know a lot of those guys and they've been super successful there's no way around it like it doesn't matter how anyone feels about their product like they they've been a reliable host for tons of people and that's that you know people pay for things they vote for products voluntarily with their money if wpon sucked or was breaking the rules or was lying or cheating people then this would have been exposed long ago and they would they would be out of business they wouldn't be having amazing growth they wouldn't be posting these huge profit numbers they wouldn't be acquiring um skins and uh SK themes and plugins in the WordPress community and keeping them alive like these are like this we got to we got to talk about stuff like that because a lot of this goes on so plugins will die over time because they usually the creators don't make enough money but some of these plugins are vital to the the EOS the WordPress ecosystem they might have hundreds of thousands or millions of users and so some of these companies like WP engine will step in and buy some of these properties from time to time and keep them alive that is doing a huge service to the community I have to tell people this all the time who want to whine about changes I make in my business uh but the reality is you have to make changes to survive over time if you don't the stuff will be gone and then you have to ask yourself is it better that stuff dies and all these users are left hanging and like their stuff stops working is that better or is it better that somebody like WP engine comes in with a lot of capital and buys up some of these distressed properties and keeps them alive so that users experience continuity on their sites uh I see that as a big service to the community and something that certainly should not be glossed over in any situation like this all right so there's the backstory all that stuff's out of the way now you know what the details are like you know how we got here and what the terms are and now I want to go through the cease and assist letter that WP engine sent to Matt mullenweg and his company automatic because it reveals just crazy behavior like you have to see this to believe it, 😱 Matt Mullenweg vs. WPEngine [Part 1], Chris Pearson, 01j8wkhj8bqmxjd0rt3ar3rakg.