Matt vs WP Engine: Too Far?  ## Metadata - Author: [[🌐 Justin's Blog]] - Full Title: Matt vs WP Engine: Too Far? - Category: #articles - Document Note: --- tags: [#WordPress, #community, #WP-Engine] - #WordPress - #community - #WP-Engine Author: Justin Ferriman Source: Matt vs WP Engine: Too Far? Reference: [Matt vs WP Engine: Too Far?](https://justinferriman.com/matt-vs-wp-engine-too-far) date created: 2024-09-23 11:00 --- # Title: Matt vs WP Engine: Too Far? ## 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-assessment) - [✅ Logical Validity](#✅-logical-validity) - [🔍 SEO Evaluation](#🔍-seo-evaluation) - [🎯 Conclusion](#🎯-conclusion) ### References: - [Justin Ferriman: Matt vs WP Engine: Too Far?](https://justinferriman.com/matt-vs-wp-engine-too-far) ## 📝 Summary: In this article, Justin Ferriman discusses a controversy involving Matt Mullenweg and WP Engine over a conflict regarding ethics and transparency in the WordPress ecosystem. Mullenweg’s remarks toward WP Engine sparked debate within the community about whether his criticism was justified or went too far. The article analyzes the incident and its broader implications for open-source governance, community trust, and business relationships in the WordPress world. ## 📖 Main Content: The article delves into the recent public dispute between Matt Mullenweg, WordPress co-founder, and WP Engine, a managed WordPress hosting provider. Mullenweg openly criticized WP Engine’s actions, accusing them of acting against the values of open-source collaboration. Ferriman argues that while Mullenweg’s concerns may be valid, his approach could alienate key players in the WordPress ecosystem, undermining community cohesion. The article also questions whether personal attacks are productive in fostering a more inclusive and transparent open-source environment. ### 🗒️ Notes - **Context of the Dispute**: - Mullenweg criticizes WP Engine for alleged unethical business practices. - Accusations revolve around licensing and contributions to the WordPress project. - **Community Reactions**: - Mixed responses: some agree with Mullenweg’s stance, while others believe his approach was harsh. - Concerns about trust within the WordPress business ecosystem. - **Broader Implications**: - Raises questions about leadership in the open-source community. - Potential long-term effects on partnerships and collaborations within the WordPress ecosystem. ## 📖 References: - Justin Ferriman: [Matt vs WP Engine: Too Far?](https://justinferriman.com/matt-vs-wp-engine-too-far) ## 🗣️ Paraphrase:  1. "Mullenweg’s criticism of WP Engine suggests deeper issues within the WordPress ecosystem regarding how large companies interact with the open-source community. It raises questions about whether profit motives conflict with the collaborative spirit of WordPress." - Mullenweg’s comments reflect larger concerns about the tension between corporate interests and the open-source ethos within WordPress, questioning whether businesses can balance profit with community values. 2. "The public nature of the dispute risks alienating important partners in the ecosystem, potentially creating fractures in the community and hindering collaboration moving forward." - By addressing the issue so publicly, Mullenweg might be driving a wedge between key players in WordPress, threatening future cooperation and community unity. ## 📰 Newsletter: This week in WordPress, the spotlight is on a brewing controversy between Matt Mullenweg and WP Engine. In an article by Justin Ferriman, the conflict centers around ethical practices and transparency within the WordPress ecosystem. Mullenweg called out WP Engine, sparking debate on whether his criticism was justified or over the line. With mixed reactions from the community, this story brings up key questions about leadership, open-source governance, and the future of WordPress partnerships. Check out the full discussion [here](https://justinferriman.com/matt-vs-wp-engine-too-far). ## ✅ Action Items: This article directly connects to my role as a Developer Advocate focusing on open-source advocacy and contributor engagement. It highlights the delicate balance between fostering community trust and managing business relationships in the WordPress ecosystem. As I work toward creating more inclusive and sustainable contributor pathways, this article underscores the importance of transparency and ethical practices. The issues raised here are particularly relevant as I aim for an OSPO director role, where guiding ethical collaboration is crucial. ## 🧪 Hypotheses: 1. Publicly addressing conflicts within open-source communities may decrease trust between contributors and organizations. 2. Ethical transparency in business dealings directly impacts the retention of contributors in open-source ecosystems. ### 📊 Methodology: 1. **Survey**: Conduct surveys to gauge community trust in leadership and businesses after public disputes. 2. **Case Study**: Analyze previous open-source controversies to assess long-term effects on collaboration. ### ❓ Questions: 1. How can the WordPress community ensure transparency while avoiding divisive public disputes? 2. What role should corporate entities play in maintaining open-source values while pursuing profit? ### 🔮 Future Research: - Explore the effects of leadership disputes on community trust and contributor retention. - Investigate strategies for conflict resolution in large open-source projects without alienating key partners. ### 💡 Implications: Understanding how public disputes affect the open-source community can guide future efforts in conflict resolution and contributor engagement. This research could influence open-source policies and leadership strategies within WordPress and similar ecosystems. ### 🧠 Learning Styles Assessment: 1. **Visual Learners**: - **Present**: The article lacks visual aids or diagrams. - **Improve**: Adding flowcharts or visual representations of the conflict could help visual learners understand the dynamics. 2. **Aural Learners**: - **Improve**: Provide an audio version of the article or link to related podcasts for a more engaging experience. 3. **Verbal Learners**: - **Present**: The language is clear and uses analogies, but more storytelling could enhance engagement. - **Improve**: Introduce more analogies to explain complex concepts like open-source governance. 4. **Physical Learners**: - **Improve**: Suggest actionable steps for readers to take, such as how to engage in community discussions. 5. **Logical Learners**: - **Present**: The argument follows a logical flow, but lacks data to support claims. - **Improve**: Provide data on the impact of public disputes on open-source ecosystems. 6. **Social Learners**: - **Present**: The article discusses community reactions, but lacks opportunities for engagement. - **Improve**: Add prompts for group discussions or links to community forums. 7. **Solitary Learners**: - **Improve**: Encourage reflection on how conflicts like this affect individual contributors and community engagement. 8. **Naturalistic Learners**: - **Improve**: Include examples from nature to help illustrate balance and conflict in ecosystems, as a metaphor for open-source communities. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure alt-text for any future images or graphs. - **Keyboard Navigation**: Confirm all interactive elements are accessible via keyboard. - **Contrast and Readability**: Improve font contrast for readers with visual impairments. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: The article doesn’t address cultural diversity in the WordPress community. - **Improve**: Incorporate examples fro - Document Tags: [[open source corporate contribution]] [[wordpress]] [[wpdrama]] [[wp engine]] - Summary: WordPress co-founder, Matt Mullenweg, picks a fight with WP Engine, even calling them a "cancer". Did you catch Matt's keynote talk at W... - URL: https://justinferriman.com/matt-vs-wp-engine-too-far WordPress co-founder, Matt Mullenweg, picks a fight with WP Engine, even calling them a "cancer".  Did you catch Matt's keynote talk at WordCamp U.S. this year? It was pretty boilerplate, as far as his talks usually go, but there was one part that stood out to nearly everyone, and that was his comments towards WP Engine and their lack of contribution to the WordPress project. Matt expressed his annoyance at the contributions made by WP Engine to WordPress, comparing their 47 hours per week to Automattic's 3,786 hours per week. > *“Those of us who are makers, who create the source, need to be wary of those who would take our creations and squeeze out the juice. They’re grifters who will hop onto the next fad, but we’re trying to build something big here, something long term—something that lasts for generations. Think about that next time it comes up to renew your hosting or domain, weigh your dollars towards companies that give back more, because you’ll get back more, too. Freedom isn’t free.”* Those are some pretty strong words, and I'm sure it doesn't feel good to be called out in a negative light at one of the biggest WordPress events of the year. As such, I was curious to see the response from WP Engine, as these were some harsh words from the man at the top. I [put a tweet out](https://x.com/JustinFerriman/status/1837099459483759078) saying the same:  That post (which cited an article on [WPTavern](https://wptavern.com/matt-mullenwegs-ecosystem-thinking-for-open-source-success)) started a lively discussion about the point raised by Matt during his talk. As you would expect, WP Engine wasn't far behind with their response. In summary, they said something to the effect of: * WP Engine has contributed to WordPress innovation for over a decade, advancing the ecosystem and supporting developers and millions of websites. * They invest heavily in the community through sponsorships, educational events like DE{CODE}, and development tools such as Faust.js and WPGraphQL. * WP Engine is committed to fostering creativity and empowering WordPress developers to keep the CMS at the forefront of web development. For more, see [WP Engine's article](https://wpengine.com/blog/highlighting-wordpress-innovation-contribution/). #### The Point vs The Delivery Matt has become far more divisive in recent years. Call it the size of WordPress, or maybe just the demeanor of someone who has been the focus of so many attacks for two decades. Whatever the reason, he's clearly tired of being politically correct all the time. What often happens is that he will make a point, people argue the point for a moment, then they start to get angry at the way the point was raised. They attack the messenger, for lack of a better term. But it's not like it isn't warranted at times. I've been around WordPress long enough to have seen Matt air out personal vendettas rather publicly, wrapped up in some kind of “I'm looking out for what's best for everyone” sentiment. This actually ends up having the opposite effect in that the focus shifts to Matt (the person), not what it is he's trying to point out. Because, look, as far as I can tell *there is* a valid point there. [This post by Noel](https://x.com/noeltock/status/1837423892303851951) does a pretty good job outlining that point:  I think what's pretty telling, though, is that this comment by Noel was a response to [a poll that Matt ran](https://x.com/photomatt/status/1837303425106837784), and it shows how the majority of folks disagree with his take on WP Engine's role within WordPress.  ##### But it keeps going... Matt has been popping up across various channels, seemingly defending his view and attempting to make points about WP Engine's lack of contributions despite their size and financial resources. Unfortunately, those points are now falling upon deaf ears because of the manner and frequency in which the “attacks” are coming. Matt [published this post](https://wordpress.org/news/2024/09/wp-engine/) on the official WordPress.org news about how WP Engine turns off revision history, an important feature in WordPress core, to save money. To drive home another point, he used a mini-story about his mom confusing the two brands (WP Engine and WordPress), which was the basis for the title of the post. To cap it off, he referred to WP Engine as “a cancer”. Yikes. This made me wonder a few things: 1. Are a lot of people confusing WP Engine (the brand) with WordPress? 2. Is it ever okay to call businesses, and the people working there, “cancer”? 3. Should this have been posted on his personal blog, instead? Speaking of the personal blog, Matt did write a [blog post about investors](https://ma.tt/2024/09/are-investors-bad/), and if they are inherently “bad”. Something he likely wanted to touch on because of WP Engine's impressive investment over the years. He contends: * Investors are essential for entrepreneurship, but there are both good and bad investors. It's important to evaluate their track record and actions after investing. * Private equity investors can be beneficial, especially when they respect open-source values and support the community, as seen with Automattic's investors. * Actions matter more than words; companies should be judged based on how their behavior impacts communities and ecosystems over time. I'm not surprised by his viewpoint given that Automattic has taken its fair share of investment, though I do take exception to his claim that investors are essential for entrepreneurship. That is not true at all. Just speaking from my own experience, I never had a single investor, and LearnDash not only did well, it thrived. In fact, we **absolutely destroyed** Automattic's competing product to LearnDash (Sensei). I didn't even consider them a credible competitor. #### His Mind is Made Up Matt has always taken on the role of “open source protector”, and whenever he feels that it is being taken advantage of, he attacks — and his attacks can be quite harsh. He clearly feels that this is happening with WP Engine, though it also has an adverse effect for him in that the community starts to [highlight some hypocrisy](https://x.com/keithdevon/status/1837878862966853911):  History has shown that when Matt makes his mind up about something, nothing will shake him from it. If anything, backlash makes him dig in further. He will go down on that ship, but he knows that the ship will never go down, because the ocean is the community that contributes to, and depends on, WordPress in their daily lives. #### Qualifying Contributions is in Poor Taste If I take the time to separate the inflammatory rhetoric and poor choice of message delivery, I do think that there is an important point that Matt is bringing to the community's attention. WP Engine indeed does have the fortunate position to contribute more to WordPress in terms of hours. What I don't like, however, is that Matt is outlining what he considers to be an acceptable contribution. Sponsoring WordCamps? That doesn't count. Not to him, anyway. This has a way of polarizing the less visible in the community. The individual developer who has a small plugin business is proud to sponsor his local WordCamp, but the message being sent from the boardroom is that this is a “meh” form of contribution. In other words, don't feel too good about it. It's not really valued. Matt has come down hard on WordPress hosts for some time. GoDaddy, Pagely (now part of GoDaddy), and Pantheon come to mind. I think he has a higher expectation of them than the “average” WordPress user. And maybe we all should. They are the ones with the money and resources to *really* move the needle for the WordPress project. To date, it doesn't appear like any host is living up to Matt's unspoken expectation. [#WordPress](https://justinferriman.com/tag:WordPress) [Justin Ferriman](https://justinferriman.com/) Amateur blogger for over 20 years. I write about life, happiness, entrepreneurship, and politics. [Full bio](https://justinferriman.com/about)., Matt vs WP Engine: Too Far?, 🌐 Justin's Blog, 01j8fv27k56nqxwhrkq4mnsjvs.