WordPress Drama Explained  ## Metadata - Author: [[Syed Balkhi]] - Full Title: WordPress Drama Explained - Category: #articles - Document Note: --- tags: [#wordpress, #litigation, #open-source, #trademark, #community] - #wordpress - #litigation - #opensource - #trademark - #community Author: Merlin Source: "The Litigation Disaster Tourism Hour" [YouTube stream](https://www.youtube.com/watch?v=joxZaP-rfqM) Reference: Transcript in litigation.txt date created: 2024-10-15 18:00 --- # Title: WordPress Trademark Litigation and Its Impact on the Community ## 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 (Diversity, Equity, Inclusion, and Belonging) Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: This transcript delves into the legal tensions between WP Engine and Automattic, exploring the trademark dispute over the WordPress brand. It examines the interplay between Automattic’s commercial interests and open-source principles, which has raised concerns among developers and contributors. Key issues include the shifting control of WordPress trademarks, the integrity of the WordPress Foundation, and how legal proceedings may influence the broader open-source community. --- ## 📖 Main Content: ### 🗒️ Notes #### 1. **Overview of the Lawsuit**: - **Primary Conflict**: WP Engine challenges Automattic’s control over WordPress trademarks, arguing that Automattic violated promises of community-driven governance. - **Declaratory Judgment**: WP Engine preemptively seeks a court ruling to invalidate Automattic’s trademark enforcement, ensuring companies using “WordPress” can avoid future legal threats. #### 2. **Historical Background**: - **2010 Trademark Transfer**: Automattic moved WordPress trademarks to the WordPress Foundation to ease public concerns about corporate control. - **Hidden Licensing Agreement**: On the same day, Automattic secured a perpetual, royalty-free commercial license, keeping effective control over the brand. #### 3. **Impact on the Ecosystem**: - **Developers and Service Providers at Risk**: Stricter trademark enforcement could force rebranding and increased legal costs for businesses. - **Erosion of Trust**: The dispute risks alienating contributors and fragmenting the community. #### 4. **Legal Strategies and Implications**: - **Doctrine of Laches**: WP Engine argues Automattic delayed enforcement too long, making sudden actions unjust. - **Unclean Hands Doctrine**: Automattic is accused of acting in bad faith, promoting community governance while retaining profit-oriented control. #### 5. **Public Reaction**: - **Mixed Messaging**: Mullenweg’s statements have sparked backlash, with developers frustrated by Automattic’s use of the WordPress admin dashboard for legal messaging. --- ## 📖 References: - [Transcript of YouTube Stream](https://www.youtube.com/watch?v=joxZaP-rfqM) - Legal filings from the Northern District of California --- ## 🗣️ Paraphrase: 1. "The legal challenge questions Automattic’s attempt to monopolize the WordPress brand under the guise of community ownership, threatening the ecosystem’s open-source principles." 2. "If Automattic enforces stricter control, businesses and developers might need to rebrand their services, increasing operational burdens and disrupting innovation." --- ## 📰 Newsletter: **Headline**: "Legal Battle Over WordPress Trademarks Heats Up" In a pivotal move, WP Engine has taken Automattic to court over the control of WordPress trademarks. The dispute centers around whether Automattic’s actions align with the open-source principles the community was built on. With potential implications for developers, hosting services, and contributors, this case highlights the need for clear trademark governance in the open-source ecosystem. Stay informed and explore legal guidance if your business relies on WordPress branding. --- ## ✅ Action Items: 1. Monitor legal proceedings and inform community members about potential outcomes. 2. Collaborate with legal experts to ensure compliance with trademark rules. 3. Advocate for greater transparency in WordPress governance, aligning with open-source values. --- ## 🧪 Hypotheses: - Automattic’s enforcement will lead to a shift in open-source project governance. - Businesses will face increased legal and marketing costs if stricter trademark policies are implemented. ### 📊 Methodology: - **Data Collection**: Review court filings, community discussions, and public statements. - **Analysis**: Conduct sentiment analysis on community responses and examine the financial impact on businesses. --- ## ❓ Questions: - How will this dispute affect future open-source project governance? - What role should the WordPress Foundation play in maintaining community trust? --- ## 🔮 Future Research: - Investigate governance models in other open-source projects facing trademark conflicts. - Explore how legal outcomes influence contributor participation in open-source communities. --- ## 💡 Implications: This case could redefine how trademarks are managed within open-source projects, potentially limiting innovation and altering the relationship between foundations and contributors. --- ## 🧠 Learning Styles Assessment: - **Visual Learners**: Provide flowcharts showing the timeline of trademark disputes. - **Aural Learners**: Offer podcasts covering the legal implications. - **Logical Learners**: Include step-by-step analyses of legal doctrines involved. --- ## 📊 Accessibility Assessment: - Ensure legal filings are screen-reader friendly with proper alt text for images. - Optimize the user experience for keyboard navigation and text resizing. --- ## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - Use inclusive language in legal and community communications. - Include diverse perspectives in discussions about governance and trademarks. --- ## ✅ Logical validity: The arguments highlight both sound reasoning and potential fallacies. WP Engine’s reliance on the **laches doctrine** is valid, but the **slippery slope** argument regarding potential fragmentation might overstate the consequences. --- ## 🔍 SEO Evaluation: - **Keywords**: "WordPress trademark dispute," "open-source governance," "WP Engine lawsuit." - **Title Tag**: Clear and optimized for search engines. - **Internal Links**: Connect to related community discussions and legal resources. --- ## 🎯 Conclusion: The ongoing legal battle between WP Engine and Automattic could reshape the governance of WordPress and other open-source projects. Developers, businesses, and contributors must remain vigilant as the case unfolds to ensure that community values are preserved. - Document Tags: [[Matt Mullenweg]] [[open source corporate contribution]] [[wpdrama]] [[wp engine]] - Summary: There's a lot of misinformation and fear being spread about WordPress. Here's an objective overview of the latest WordPress drama, and how it may affect your website. - URL: https://www.wpbeginner.com/news/wordpress-drama-explained-and-how-it-may-affect-your-website/ It’s weird to receive texts like “is this WordPress drama crazy or is it being blown out of proportion”. In the 15 years of running WPBeginner, I never thought I would have to write a blog post covering any WordPress industry drama. My focus with the blog has always been to provide high quality free WordPress tutorials for non-techy beginner users and small business owners. But unfortunately, we are at a point where a lot of misinformation and fear is being spread about WordPress by media outlets and influencers who’re hungry for clicks. This is causing panic among some website owners, agencies, as well as people in enterprise companies. Some folks are asking questions like whether WordPress is still safe and should they search for an [alternative CMS option](https://www.wpbeginner.com/showcase/best-cms-platforms-compared/) for their websites. In this post, I want to explain what this latest WordPress drama is about, who it impacts, and what you can do to protect your websites. **TLDR:** No, this is NOT the end of WordPress, and your websites are safe.  **My Disclaimer:** I’m not a trademark lawyer or legal expert. I’m writing this post for WPBeginner blog readers who are concerned about what’s going on. I have spent the last 18 years in this community, and I love WordPress. These are my opinions based on my industry experience and what I have been reading online. I have no insider knowledge of the situation. I reserve the right to change my opinions should I learn new information. With that out of the way, let’s jump right into what’s happening around this WordPress drama involving WP Engine vs. Automattic. ###### What is This WordPress Drama All About? (Short Summary) **Quick Summary:** There is a lawsuit between two WordPress companies (WP Engine and Automattic) around a trademark dispute. Due to their influence, there have been escalations which has led to a lot of negative PR for the WordPress ecosystem. Vast majority of WordPress sites are NOT impacted by this at all. This whole thing started because two big companies in the WordPress industry are in a legal battle over a trademark dispute. Automattic is a company started by WordPress co-founder, Matt Mullenweg. They are the creators of WooCommerce, WordPress.com hosting service, Jetpack plugin, and more. WP Engine is a [managed WordPress hosting](https://www.wpbeginner.com/managed-wordpress-hosting/) company owned by a large private equity firm Silver Lake. Automattic has the exclusive commercial rights to use the “WordPress” trademark. They asked WP Engine to negotiate a licensing agreement which involved either payments to Automattic OR increased contributions to the free open source WordPress project. Because the parties failed to come to an agreement, Matt publicized the dispute at the annual WordCamp US conference where [he claimed](https://wordpress.org/news/2024/09/wp-engine/) that WP Engine despite being a $400M+ revenue company does not give back enough to the free open source WordPress project. As things escalated, both companies sent each other a formal legal Cease and Desist (C&D) letter. Due to the legal threats, Matt as co-founder of WordPress, [banned WP Engine](https://wordpress.org/news/2024/09/wp-engine-banned/) from accessing WordPress.org servers. This meant that any customer with websites on WP Engine hosting were no longer able to receive updates from WordPress.org servers. The ban was later [reverted *temporarily*](https://wordpress.org/news/2024/09/wp-engine-reprieve/) to protect users and allow WP Engine to build their own update servers. Since WordPress is open source, the WP Engine team was able to build their own updater to ensure users on their hosting platform can get software updates. The server block officially went back into effect on October 1st. Shortly after, WP Engine filed a federal lawsuit against Automattic and Matt Mullenweg. Due to the escalation, WP Engine’s team were banned from accessing their WordPress.org accounts. This means the WP Engine team is no longer able to release updates to their WordPress plugins from the official WordPress.org servers. One of the plugins owned by WP Engine is Advanced Custom Fields (ACF) which is popular among developers and used by over 2 million websites. To ensure security updates are available to all users, WordPress.org team [forked the ACF plugin](https://wordpress.org/news/2024/10/secure-custom-fields/), renamed it to Secure Custom Fields (SCF), and took over the original ACF plugin directory page without the consent of WP Engine. The reasons given for this was to maintain and provide updates to users who are unaware of the drama. This decision was not well received and garnered a lot of negative comments from developers, influencers, and press outlets. At the time of writing this post, all other WP Engine plugins are still available for download on WordPress.org plugin directory however WP Engine team is still banned, so they are not able to use WordPress.org servers to issue updates. In summary, at the root of this WordPress drama is a heated legal trademark dispute between WP Engine hosting company, Automattic, and Matt Mullenweg (co-founder of WordPress). Since there is a federal lawsuit filed by WP Engine against Automattic, I believe only the courts can decide the outcome unless the parties come to an amicable resolution outside of courts. The official WordPress twitter account tweeted that the situation can be resolved under the following conditions:  [WordPress](https://twitter.com/WordPress) [@WordPress](https://twitter.com/WordPress) If WP Engine dropped its lawsuits, apologized, and got in good standing with its trademark use, you are welcome to have access to the plugin directory listing. In the meantime, Secure Custom Fields is a community plugin and open for contribution. We know you can't log into .org right now, but if you have any code changes you'd like to make get in touch and we'll set up an alternative pathway for you. We want the best, most secure code for our users. [Posted Oct 14, 2024 at 3:11AM](https://twitter.com/WordPress/status/1845663751342883195) ###### Is this the End of WordPress? The answer is NO. Absolutely not. WordPress powers **over 43% of websites** on the internet, and it’s bigger than any one person or company. The vast majority of small business owners and users of WordPress don’t even know about this ongoing drama because it simply doesn’t impact them. I talked with a local small business owner who’s my personal trainer, and he wasn’t aware of the negative press around WordPress at all. When I briefly told him about it, here is what he said: > “I am not going to switch from WordPress because some big companies are having a trademark dispute. What matters to me is that my website is working and my business is growing.” – Sean Nelson, Founder of [Hustle Training 360](https://hustletraining360.com/). > > The reality is that the WordPress software you built your website with hasn’t changed. If you’re using popular plugins like Elementor, [WPForms](https://wpforms.com), WooCommerce, [AIOSEO](https://aioseo.com), [Duplicator](https://duplicator.com) and literally 60,000+ others, they are still the same. Something as big as WordPress simply doesn’t end because two companies have a trademark dispute. In the grand scheme of things, there are a small portion of users who are impacted, and I will share how you can find out if your website is impacted, and what you can do about it. ###### Is My Website Affected by All of This? The vast majority of users and websites using WordPress are **NOT** impacted by this legal dispute between Automattic and WP Engine. If you are using a free plugin that was developed by WP Engine, and you are NOT on their hosting platform, then your websites are impacted because you will not be able to receive updates for those free plugins from WordPress.org. Here are the popular free plugins built by WP Engine that are blocked from sending updates from WordPress.org servers: * Advanced Custom Fields * Nitropack * Better Search Replace * WP Migrate Lite * WP Offload SES Lite * Frost * Genesis Blocks * Genesis Custom Blocks * For the full list, see [plugins built by WP Engine](https://wpengine.com/support/installing-and-updating-free-wp-engine-plugins-and-themes/). ###### What Can You Do to Protect Your WordPress Site? As I said earlier, if you’re not using the plugins made by WP Engine, then you don’t need to do anything. Your WordPress site is safe and good to go. Although, I always recommend having [regular WordPress backups](https://www.wpbeginner.com/beginners-guide/how-to-backup-your-wordpress-site/) and using a firewall like Cloudflare (see [more WordPress security tips](https://www.wpbeginner.com/wordpress-security/)). Now, if you’re using the plugins built by WP Engine, then you will need to either install the [WP Engine updater plugin](https://wpengine.com/support/installing-and-updating-free-wp-engine-plugins-and-themes/) to continue receiving updates or find an alternative, depending on your personal preference. ###### What Should I Do as a WordPress Agency with Concerned clients? You can send them a link to this blog post and re-assure them that WordPress is still safe and by far the best open source CMS option in the market. A legal trademark dispute between two companies **does NOT** change the fact that WordPress is powered by 43% of all websites (and growing). There are 60,000+ free WordPress plugins, and thousands of free WordPress themes available in the market that makes it easy to build any type of website they want. WordPress core development progress continues, and [WordPress 6.7 is coming soon](https://www.wpbeginner.com/news/whats-coming-in-wordpress-6-7-features-and-screenshots/). Here are some more insights on [WordPress market share and trends](https://www.wpbeginner.com/research/ultimate-list-of-wordpress-stats-facts-and-other-research/). ###### My Final Thoughts Despite everything that’s going on right now, I still love WordPress, and I believe in our amazing WordPress community. I have spent more than half of my life in the WordPress community, and I will continue to do everything in my power to support the community and our users. See my recent post on [contributing to the WordPress ecosystem](https://www.wpbeginner.com/opinion/contributing-to-the-wordpress-ecosystem-my-thoughts/). Lastly, I truly hope that the two respected companies involved in the lawsuit can come to an agreement soon, so we can all focus on growing WordPress and helping democratize publishing & commerce across the world. As always, I want to thank you for your continued support of WPBeginner, and I look forward to continuing serving you for years to come. Yours Truly, Syed Balkhi Founder of WPBeginner ###### References: * [WP Engine Cease & Desist Letter](https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf) * [Automattic Cease & Desist Letter](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) * [WP Engine formal lawsuit](https://wpengine.com/wp-content/uploads/2024/10/Complaint-WP-Engine-v-Automattic-et-al.pdf) against Automattic and Matt Mullenweg * A full list of commentary [on The WP Minute](https://thewpminute.com/automattic-vs-wp-engine-heres-what-we-know/), WordPress Drama Explained, Syed Balkhi, 01ja92ryevbjc0td08peqm64yt.