What's Going on With WordPress?  ## Metadata - Author: [[Craylor Made]] - Full Title: What's Going on With WordPress? - Category: #articles - Document Note: ```markdown --- tags: [#WordPress, #MattMullenweg, #WPEngine, #OpenSource, #CommunityExodus, #LegalBattle, #WordPressGovernance] - #WordPressDrama - #CommunityReform - #LeadershipIssues Author: Merlin AI Source: YouTube Reference: [Video Link](https://www.youtube.com/watch?v=QesekZr4G0I) date created: {{date:2024-12-24}} {{time:12:00}} --- # Title: Recent WordPress Drama: Mullenweg's Controversial Actions Against WP Engine Spark Widespread Community Exodus and Resignations ## Table of Contents: - [📖 Conflict Overview](#conflict-overview) - [💥 Impacts on the Community](#impacts-on-the-community) - [⚖️ Legal Developments](#legal-developments) - [🔮 Long-Term Concerns](#long-term-concerns) - [🛠️ Community and Leadership Reform](#community-and-leadership-reform) - [📖 References](#references) ### References: - [YouTube Video](https://www.youtube.com/watch?v=QesekZr4G0I) ## 📝 Summary: The WordPress community is in turmoil due to a public conflict between Matt Mullenweg, the founder of WordPress, and WP Engine, a leading WordPress hosting company. Mullenweg's actions, including hijacking the Advanced Custom Fields (ACF) plugin listing and a mandatory login checkbox requiring users to disavow WP Engine, have caused a massive exodus of contributors and developers. Legal action was taken, and a California judge ruled that Mullenweg and Automattic must cease interference with WP Engine’s operations. This situation has raised concerns about the future governance of WordPress, its security, and its long-term viability. ## 📖 Main Content: The WordPress ecosystem has recently experienced significant conflict, with the primary dispute involving Matt Mullenweg's aggressive tactics against WP Engine. This included creating a fork of the Advanced Custom Fields (ACF) plugin and hijacking its listing, resulting in confusion and frustration among users. Mullenweg’s actions escalated when he introduced a mandatory checkbox on the WordPress.org login page that prevented WP Engine users from accessing resources, causing further alienation. The fallout from Mullenweg's controversial actions led to a mass exodus from the WordPress community. Developers pulled their plugins and themes, while key figures, such as Josephia, the executive director of WordPress Product at Automattic, resigned. The community’s response to Mullenweg's approach raises important questions about leadership and governance within the WordPress Foundation, and whether the community can continue to thrive under its current management. A California judge intervened, granting WP Engine an injunction that required Mullenweg and Automattic to cease interfering with WP Engine’s business. This ruling reflects the court’s acknowledgment that Mullenweg may be overstepping his control over WordPress resources. The situation remains unresolved, with the legal battle set to continue in the coming months. However, the conflict has already sparked significant debate about the long-term sustainability and fragmentation of WordPress. ### 🗒️ Notes: - **Conflict Overview**: - Mullenweg's aggressive actions against WP Engine included hijacking the ACF plugin listing, creating Secure Custom Fields (SCF), and redirecting users to the new fork. - WP Engine filed a 62-page legal complaint to resolve the conflict, further escalating tensions. - **Impacts on the Community**: - A mass exodus of developers and contributors, with many pulling their plugins and themes from WordPress.org. - Josephia, a key figure in the WordPress community, resigned from Automattic due to the growing unrest. - A mandatory login checkbox added by Mullenweg further isolated WP Engine users, contributing to the exodus. - **Legal Developments**: - A California judge ruled in favor of WP Engine, granting them an injunction against Mullenweg and Automattic, forcing them to cease interference. - The injunction led to the restoration of ACF to the plugin repository and the removal of the mandatory login checkbox. - **Long-Term Concerns**: - The situation has raised concerns about WordPress’s centralization, as Mullenweg’s control over WordPress.org was called into question. - The dependency on centralized control and potential fragmentation of the platform poses a risk to WordPress’s stability and security. - **Community and Leadership Reform**: - There are growing calls for leadership reform within the WordPress Foundation, with many questioning Mullenweg’s approach to governance. - The community’s trust in WordPress leadership has been severely damaged, and there is a need for transparency and better leadership practices. ## 📖 References: - [YouTube Video](https://www.youtube.com/watch?v=QesekZr4G0I) ## 🗣️ Paraphrase: 1. **Original**: "Matt Mullenweg initiated aggressive actions against WP Engine, impacting WordPress sites hosted there." - **Paraphrase**: "Matt Mullenweg took hostile actions against WP Engine, disrupting the WordPress sites hosted on their platform." 2. **Original**: "Mullenweg's control over WordPress faces scrutiny due to Trademark issues with the WordPress Foundation." - **Paraphrase**: "Mullenweg's authority over WordPress is being questioned, especially regarding trademark disputes with the WordPress Foundation." ## 📰 Newsletter: **WordPress Drama Escalates as Mullenweg’s Actions Spark Community Exodus** The WordPress ecosystem is in turmoil following Matt Mullenweg’s controversial actions against WP Engine. In a dramatic escalation, Mullenweg hijacked the Advanced Custom Fields plugin listing, creating a fork and redirecting users to his version. This led to widespread frustration, with many developers pulling their plugins and themes from WordPress.org. Legal action followed, resulting in a temporary injunction against Mullenweg and Automattic. As the legal battle continues, the WordPress community faces a pivotal moment, with calls for leadership reform and concerns about the platform’s future stability. [Read more about the latest developments here.](https://www.youtube.com/watch?v=QesekZr4G0I) ## ✅ Action Items: - **Encourage WordPress Community Dialogue**: Foster open discussions around leadership changes within the WordPress Foundation and governance reforms. - **Support Contributor Rights**: Advocate for the rights of WordPress contributors and ensure that future decisions are made transparently and with input from the community. - **Promote Sustainable Practices**: Engage in conversations around the financial sustainability of WordPress and explore ways to distribute server costs equitably among stakeholders. ## 🧪 Hypotheses: - The ongoing conflict could lead to more open-source projects adopting decentralized governance models to avoid similar disputes. - If WordPress leadership reforms, the platform could regain trust from the developer community and stabilize its position in the open-source ecosystem. ### 📊 Methodology: - Conduct surveys among WordPress contributors and users to assess the impact of Mullenweg’s actions on community engagement. - Analyze migration trends from WordPress to other platforms to evaluate the potential long-term effects on WordPress usage. ### ❓ Questions: - How can WordPress leadership rebuild trust with its community after such significant disputes? - What governance changes would be necessary for WordPress to remain competitive in an increasingly fragmented open-source ecosystem? ### 🔮 Future Research: - Investigate the potential for decentralized governance structures in open-source communities and their impact on stability and growth. - Examine the role of trademark and trademark enforcement in open-source projects and its potential for abuse by centralized entities. ### 💡 Implications: Future research could provide insights into improving leadership structures in open-source communities, promoting fairer practices, and ensuring the longevity of projects like WordPress. The focus could be on creating frameworks that balance community contributions with corporate interests while maintaining transparency. ### 🧠 Learning Styles Assessment: 1. **Visual Learners**: - **Present**: The article lacks visual aids but provides a s - Document Tags: [[matt mullenweg]] [[wordpress]] [[wpdrama]] [[wp engine]] - Summary: No-code website builder comparison: https://youtu.be/rx9n9GmStDo Original WordPress drama breakdown: https://youtu.be/4G_3lZQlxHQ Seriously, what's going on with WordPress? Matt Mullenweg waged a war with WP Engine over a dispute regarding trademark licensing. It's become clear that Matt Mullenweg will do everything he can to damage WP Engine's business, and a California judge wasn't fond of that. Here's the update on the situation. 💻 Best Web Hosting: https://craylor.link/hosting 🔒 Best VPN: https://craylor.link/vpn 🌐 Learn how to build a WordPress website for FREE: https://craylor.academy 💬 Join the Craylor Community on Discord (it's free!): https://craylor.link/discord 🧢 Get a Craylor Hat: https://craylor.shop 📞 Book a consultation (we can chat about anything!): https://craylor.link/consultation 🎥 Gear I use: https://craylor.link/kit ☕️ Like my content? You can buy me a coffee! https://craylor.link/coffee Connect with me: ➞ https://craylormade.com ➞ https://craylor.link/twitter ➞ https://craylor.link/instagram ➞ https://craylor.link/tiktok 0:00 - The drama continues 4:37 - The court order 6:05 - The real-world implications Affiliate link disclosure: most of my videos include affiliate links in the description. When you click an affiliate link, I may receive a commission for any products or services you purchase through that link. It doesn't cost you anything extra, and in some cases, you may receive a discount through my links. All my opinions are 100% honest, and you are welcome to purchase things by finding them on your browser instead of my links. Thank you for supporting the channel! - URL: https://youtube.com/watch?v=QesekZr4G0I&si=7m3_Gfz9TohOAb3G - For the past few months, things in the world of WordPress have been a hot mess. If you missed the drama, the founder of WordPress recently picked a fight with WP Engine, one of the biggest WordPress hosting companies in the world. Instead of waiting to resolve this conflict in court, Matt Mullenweg took what he self-described as the nuclear option, doing everything in his power to affect WordPress sites hosted on WP Engine. I already did a video explaining the initial reasons behind the conflict and my speculation on what I think might happen, but a lot has developed between October and now. Since that video, Matt Mullenweg has done some crazy stuff. Instead of just removing the Advanced Custom Fields plugin from wordpress.org, which is owned and maintained by WP Engine, he hijacked the listing, creating a fork of Advanced Custom Fields called Secure Custom Fields and hosting it on the same plugin listing as ACF. Now, look, whether you agree with it or not, Matt Mullenweg is within his right to fork ACF because it is an open source project. But last I checked, forking an open source project doesn't involve hijacking the repository listing and renaming it. This was a full-on supply chain attack. Anyone with ACF installed suddenly received updates for SCF and all the reviews on the ACF listing, yep, those carried right over to SCF. A day after I released my last video, WP Engine filed a 62-page complaint with the Californian court to demand a trial to resolve the conflict. Yet Mullenweg refused to stop there. He then added a mandatory checkbox to the login page of wordpress.org, forcing users to confirm that they were not affiliated with WP Engine in any way, financially or otherwise. This vague statement iced a lot of people out of accessing wordpress.org. On one hand, you could interpret this to mean just WP Engine stakeholders, but on the other hand, one could argue that this includes WP Engine employees, affiliates, and even customers. There's always been some kind of drama in the WordPress community, and I'll admit that I haven't been deeply involved in the community for that long, but I've never seen a mass exodus like the one that followed these actions. Some of the top talent contributing to WordPress left. Developers began pulling their plugins and themes from wordpress.org, and Josepha, the executive director of the WordPress product, resigned from Automatic after nearly 10 years of employment. Matt Mullenweg escalated things quickly after his initial presentation at WordCamp US. At first, many users were on his side. He expressed his opinion that WP Engine wasn't contributing enough to WordPress and simply asked customers to consider their options when their plan came up for renewal. But everything Matt has done since that point makes WP Engine employees, affiliates, and customers the enemy. That's evident with the login checkbox on wordpress.org. And this makes no sense because the wordpress.org website outlines four core freedoms: the freedom to run the program for any purpose, the freedom to study how the program works and change it to make it do what you wish, the freedom to redistribute, and the freedom to distribute your modified versions to others. So you're free to run the program for any purpose, yet you're not free to log into wordpress.org just because you're a WP Engine employee? When this was brought up, Matt Mullenweg made it very clear that he personally controls and operates wordpress.org and that the WordPress software itself remains free and open source to everyone accessible via GitHub. Well, first of all, the four core freedoms of WordPress are listed on wordpress.org, the very website that Matt claims ownership of, so I don't think he actually believes in these freedoms. Second, what on earth does the WordPress Foundation even do? I always assumed that the WordPress Foundation owned and controlled wordpress.org. The WordPress Foundation website says that the foundation will be responsible for protecting the WordPress, WordCamp, and related trademarks. On the trademark page, it outlines that there are acceptable ways that you can use the WordPress trademark in non-commercial scenario, but you cannot use WordPress or WordCamp as part of a domain name. Okay, makes sense to me. Except for the fact that the WordPress Foundation doesn't own or operate wordpress.org. Matt Mullenweg does. And just because he's Matt Mullenweg doesn't mean he gets special access to the trademark. Matt Mullenweg does not own the WordPress trademark. The WordPress Foundation does. It seems that Matt Mullenweg is in direct violation of the WordPress trademark, and the more you go down this path, the more you realize that WordPress is basically controlled by Matt Mullenweg. Or is it? Last week, a California judge ordered Matt Mullenweg and Automatic to stop interfering with WP Engine's business, at least until this lawsuit is settled. As a result, Mullenweg was forced to roll back everything. WP Engine once again has access to wordpress.org, ACF has been restored to the plugin repository, and the mandatory login checkbox on wordpress.org was changed from the WP Engine disclosure to forcing users to agree that pineapple is delicious on pizza. Yes, it's literally a required checkbox. Really, Matt, why? I mean, yeah, pineapple is delicious on pizza, but it shouldn't be required. Now, the drama is far from over because the injunction order is only valid until there's an official outcome in the case. The case is currently scheduled to begin in March, and I'm not a lawyer, but I'm guessing it will probably take months to years to play out. With that being said, judges generally grant injunction orders only when they genuinely believe there is legal precedent to do so. By the judge granting WP Engine's injunction request, it was an acknowledgement that Matt Mullenweg may not be able to legally do whatever he feels like with his so-called personal website. After all, WordPress powers over 43% of the entire internet, including sites as prestigious as whitehouse.gov. So it's a bit concerning that one person is pulling these strings and manipulating who is and isn't able to access the accompanying services. Now, before the um actually warriors storm the comments, yes, it is technically correct that wordpress.org is not necessary at all to run the WordPress software. wordpress.org hosts the official plugin repository, theme repository, and support forum for the WordPress project. However, WordPress core does not contain a way for users to easily switch to an alternate repository. In other words, API calls back to wordpress.org are baked into the software. So while Mullenweg makes the argument that he can flip the switch and cut off access to anyone he wants, this feels incredibly unfair when there are no user-friendly ways to switch to alternative sources, especially given the massive market share of WordPress. Should web hosts pay a fee to access WordPress.org's resources? Maybe. I think that's a legitimately fair discussion to have since running servers is expensive. It is true that Matt Mullenweg has personally been footing the bill for wordpress.org since its inception, but all of this escalated way too quickly. If Matt Mullenweg wanted companies to start chipping into the wordpress.org server bill, he could have brought this up slowly, launching a gradual campaign over the span of a year or two and making it overwhelmingly clear to the big players that if they didn't start contributing by the deadline, they would lose their access to WordPress.org's resources. But instead, we went from the general public having no idea that Matt Mullenweg and WP Engine were having disagreements to all WP Engine customers being discriminated against and eradicated from the WordPress community in a matter of weeks. Regardless of your views on WP Engine, I think we can all agree that the WordPress Foundation and wordpress.org needs serious leadership reform. I hope the outcome of this legal battle leads to permanent safeguards protecting against this type of behavior, but I'm afraid WordPress has gone down a path that will make the experience worse for everyone. What Matt Mullenweg signaled, whether intentional or not, is that wordpress.org is no longer a reliable, trustworthy source to lean on to host plugins, themes, and download WordPress updates. In response to this, we're sure to see alternative repositories created, and it's only a matter of time until we have flavors of WordPress in the same way we have Linux distros. While there's nothing inherently wrong with this and it goes with the spirit of most open-source projects, it's going to introduce new security challenges. There will no longer be one source of truth. If these alternative repositories are mirrors of wordpress.org, how up to date will they really be? If a developer pushes a zero-day patch to their plugin on wordpress.org, how long until someone using an alternative repository receives the update? Matt Mullenweg had the opportunity to make his case to the WordPress community and gracefully allow the community to see his side of the story, but instead, he alienated the very community he wanted to protect. So where do we go from here? What does this drama mean for WordPress in the short and long term? In the short term, at least while the injunction is in place, it seems we get to enjoy the old status quo, WordPress as it once was. But in the long term, I'm concerned that WordPress is going to get even more fragmented and less secure than it already is, potentially causing a downward spiral in usage. In other words, I fear that we're going to see the slow, painful death of WordPress over many years. I don't want to be dramatic. WordPress is going to be around for a very long time. It powers nearly half of the entire internet. I can't stress that enough. But technology is ever-changing, ever-improving, and we adapt and move on to newer, better software over time. And unfortunately for WordPress, I don't see it standing the test of time unless we see significant changes in leadership. However, I also acknowledge that there aren't great open source alternatives yet. Don't get me wrong, there are alternatives. Modern no-code website builders like Webflow and Wix Studio give WordPress a serious run for its money. But if you like the mission of open source and want to be able to take your website with you anywhere, WordPress is still the platform to use. If you actively use WordPress, leave a comment below sharing your thoughts. Will you continue to use WordPress without hesitation or are you keeping an eye out for the next alternative? Personally, I'm going to keep using WordPress for as long as it makes sense. I think it's got a while longer to shine as creating a genuinely competitive alternative won't be quick or easy. But in 5, 10, or 20 years from now, WordPress may very well lose its majority market share. And if it can get better leadership, maybe it can stay on top. If you want to try a WordPress alternative, I recently compared Webflow, Wix Studio, and Framer. You can check out that video here., What's Going on With WordPress?, Craylor Made, 01jfr79vpn4bs095v4m8b7a8w7.