Rubicon  ## Metadata - Author: [[Morten Rand-Hendriksen]] - Full Title: Rubicon - Category: #articles - Document Note: --- tags: [#wordpress, #trademark, #litigation, #open-source, #community] - #wordpress - #trademark - #litigation - #opensource - #community Author: Morten Rand-Hendriksen Source: "Crossing the Rubicon" [mor10.com](https://mor10.com/rubicon/) Reference: Full article accessible at the link date created: 2024-10-15 20:00 --- # Title: WordPress Trademark Disputes and Open Source Governance Challenges ## 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 article explores the complexities surrounding trademark disputes within the WordPress ecosystem, specifically the friction between Automattic and WP Engine over the use of the WordPress name. The author examines how open-source governance models intersect with trademark law, raising questions about whether corporate influence undermines community ideals. Morten Rand-Hendriksen highlights the potential ripple effects on businesses, contributors, and the future of WordPress governance if the balance between control and openness shifts too far. --- ## 📖 Main Content: ### 🗒️ Notes #### 1. **Overview of the Conflict** - **Automattic's Control**: The company retains commercial control over WordPress trademarks despite transferring ownership to the non-profit WordPress Foundation. - **WP Engine’s Lawsuit**: A declaratory judgment case aims to challenge Automattic’s control, seeking clarity on the legal use of the WordPress brand in commercial services. #### 2. **Historical Context** - **2010 Trademark Transfer**: Public messaging emphasized community ownership, but a hidden licensing agreement allowed Automattic to retain commercial privileges. - **Community Betrayal**: The discrepancy between public promises and private arrangements has fueled frustration among developers and contributors. #### 3. **Impact on the Ecosystem** - **Business Rebranding Risks**: Hosting providers and plugin developers may face costly rebranding efforts. - **Community Fragmentation**: The dispute could alienate contributors, reducing participation in the open-source project. #### 4. **Legal and Strategic Aspects** - **Laches Doctrine**: WP Engine argues that Automattic’s delay in enforcing trademarks renders sudden enforcement unfair. - **Unclean Hands Doctrine**: Automattic faces accusations of bad faith for promoting community control while retaining private benefits. #### 5. **Public Reactions and Statements** - **Community Backlash**: Mullenweg’s statements have been criticized for inconsistency, deepening mistrust. - **Dashboard Messaging**: Automattic's use of the admin dashboard to communicate legal matters was viewed as overreach. --- ## 📖 References: - [Crossing the Rubicon by Morten Rand-Hendriksen](https://mor10.com/rubicon/) --- ## 🗣️ Paraphrase: 1. **Original**: “The dispute raises a critical question: Can an open-source community thrive under corporate control?” **Paraphrase**: The central issue is whether corporate control can coexist with the principles of an open-source community. 2. **Original**: “Stricter enforcement could force smaller businesses to rethink their branding strategies, creating barriers to entry.” **Paraphrase**: Tightening trademark enforcement might push small businesses to change their branding, making it harder for newcomers to join the market. --- ## 📰 Newsletter: **Headline**: “WordPress Trademark Battle Heats Up: What It Means for Developers” This month, we dive into the ongoing trademark dispute between WP Engine and Automattic. The case highlights how open-source values clash with corporate interests, leaving developers and businesses uncertain about the future of the WordPress brand. Will this legal battle reshape governance in the open-source world? Stay informed with the latest updates and learn how it could impact your business strategy. --- ## ✅ Action Items: 1. **Follow court developments** to understand how the case will influence trademark policies. 2. **Collaborate with community leaders** to advocate for greater transparency in governance. 3. **Engage with developers and businesses** to provide guidance on trademark compliance. --- ## 🧪 Hypotheses: - Stricter trademark policies could reduce innovation in the WordPress ecosystem. - A favorable ruling for WP Engine may encourage other projects to rethink their governance models. ### 📊 Methodology: - **Data Collection**: Analyze legal documents, community discussions, and public statements. - **Research Design**: Conduct interviews with business owners and contributors to gauge the impact of trademark enforcement. --- ## ❓ Questions: - How can the WordPress community ensure transparency and trust in governance? - What lessons can other open-source projects learn from this dispute? --- ## 🔮 Future Research: - Examine governance challenges in other open-source communities facing similar trademark issues. - Explore models for balancing community ownership with corporate interests. --- ## 💡 Implications: The outcome of this case will have significant implications for how trademarks are managed in open-source projects. A shift toward stricter control could alter the relationship between developers, contributors, and businesses, potentially hindering collaboration. --- ## 🧠 Learning Styles Assessment: - **Visual Learners**: Include infographics showing the timeline of the dispute. - **Aural Learners**: Offer podcasts or webinars discussing the legal complexities. - **Kinesthetic Learners**: Develop workshops on trademark compliance strategies. --- ## 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all legal documents and community posts are accessible. - **Keyboard Navigation**: Improve site navigation to accommodate keyboard-only users. --- ## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Incorporate diverse perspectives on governance challenges. - **Inclusive Language**: Avoid jargon and ensure language is accessible to non-native speakers. --- ## ✅ Logical validity: - **Sound Reasoning**: WP Engine’s arguments around delayed enforcement align with the laches doctrine. - **Potential Fallacy**: Automattic’s warnings of ecosystem fragmentation could be seen as a slippery slope. --- ## 🔍 SEO Evaluation: - **Keywords**: "WordPress trademark dispute," "WP Engine vs. Automattic," "open-source governance." - **Meta Description**: Ensure the summary emphasizes key points to attract readers. --- ## 🎯 Conclusion: The WordPress trademark dispute highlights the tension between open-source ideals and corporate interests. The outcome will influence governance models, not just within WordPress but across the open-source landscape. Community members, developers, and businesses must remain engaged to navigate these changes and ensure a sustainable, inclusive future. - Document Tags: [[matt mullenweg]] [[Matt Mullenweg]] [[moro]] [[open source contribution]] [[open source corporate contribution]] [[wordpress]] [[wpdrama]] - Summary: On Saturday October 12, 2024, a line was crossed in the WordPress open source project that I fear will have a lasting and irrevocable impact on open - URL: https://mor10.com/rubicon/ The lighthouse at World's End, Norway. *On Saturday October 12, 2024, a line was crossed in the WordPress open source project that I fear will have a lasting and irrevocable impact on open source as a whole.* After [locking out developers](https://wordpress.org/news/2024/09/wp-engine-banned/) from rival hosting company [WP Engine](https://wpengine.com) over a [trademark dispute](https://slate.com/technology/2024/10/wordpress-wpengine-matt-mullenweg-drama-explained.html), [project lead Matt Mullenweg announced the “Advanced Custom Fields” plugin had been forked](https://wordpress.org/news/2024/10/secure-custom-fields/) and a new version titled “Secure Custom Fields” substituted into the supply chain to be automatically installed on every site running the plugin. As a result, some 2 million websites, through no action of their own, now potentially run a new plugin maintained by an unknown group of developers unfamiliar with its design and function, while the original developers desperately try to [reach their customers to ensure they get the latest updates from the original plugin](https://www.advancedcustomfields.com/blog/acf-plugin-no-longer-available-on-wordpress-org/). For some website owners, the change will cause confusion: They installed “Advanced Custom Fields,” and now they find a new plugin called “Secure Custom Fields” in its place. For others, the change will manifest as a security alert, or a function change, or even a [system error](https://news.ycombinator.com/item?id=41830709). And for most, the change will be invisible – a silent substitution of a trusted product for an untrusted one. In any other context, this would be considered a [supply chain attack](https://fossa.com/blog/polyfill-supply-chain-attack-details-fixes/), and for many enterprise, institution, and government users of WordPress it will be read as such. In my opinion, this action sets an indefensible precedent for WordPress and open source: [Expropriating](https://www.merriam-webster.com/dictionary/expropriation) an actively maintained plugin breaks any reasonable trust open source developers can have in distributing their plugins and themes through supply chain services like WordPress.org that are not under transparent and accountable management. Forcibly replacing a plugin on millions of websites is contrary to the reasonable expectations of users that the software they are using is provided and maintained by their creators or appointed successors. When one person can unilaterally block access to any developer, carbon copy their work, take over the software’s primary location and associated history (support forums, reviews, etc.), and then distribute the new version to existing users, no one can have a reasonable expectation that code posted to that service is safe. These actions are the very behaviours open source adherents so deeply despise in closed-source platforms: the claiming of other people’s content and work as their own. This is the richest kid in the neighbourhood saying he alone decides who gets to play in the sandbox, and if he takes your toy, it is your fault for not playing the way he likes. This is the community waking up to the real tragedy: They were never in a commons, they were on private land, and the owner has decided he no longer sees value in keeping up the pretence. In the oft cited ([and too seldom read](https://mor10.com/a-fatal-flaw-in-the-bazaars-foundations/)) book “[The Cathedral and the Bazaar](http://www.catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/),” open source ideologue Eric S. Raymond uses the ill-fated [Maginot Line](https://en.wikipedia.org/wiki/Maginot_Line) as a metaphor to describe how traditional software development approaches are too rigid and static to adapt to the fast-moving and dynamic environment software operates in. Raymond proposes open source as a more adaptable and decentralized alternative. What Raymond did not predict was a new Maginot Line forming within open source, manifested as centralized control of the commons by project creators turned [“Benevolent Dictators For Life”](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life). Open source is at an inevitable crossroad: It won the battle for web supremacy, but [lost the plot when it comes to who gets to extract financial value from the work](https://mor10.com/on-the-corporate-takeover-of-the-cathedral-and-the-bazaar/). As a result of the resulting massive inequity, the supply of people willing and able to volunteer their time and work to open source software is dwindling, and open source projects have become dependent on corporate support – the [exact thing Raymond and his ideological compatriot Stallman said open source would rid the world of](https://www.gnu.org/gnu/manifesto.en.html). Meanwhile, open source project founders have built vast wealth and power on their creations. They extract massive amounts of capital from the volunteer labor of unpaid contributors, and invest some of it back into the project, often by populating central positions with paid staff that steer the direction of the project in ways that ensure continued corporate benefit for the founder and their friends. > At the BDFL-level it appears conflict of interest is considered a virtue. > > The future of open source depends on what those with power choose to do with that power. Do they build an equitable system of governance where those who do the work are consulted about and compensated from the riches extracted from their work? Or do they submit to the allure of chokehold capitalism by crushing what is left of their communities with the iron fist of a dictator who no longer sees benevolence as a worthwhile investment. The Usurping of ACF may set in motion events beyond the control of the WordPress community and even the greater web community. Ignored by the owner of .org and .com and his ilk, [there are wolves at the doors to the open web](https://heatherburns.tech/2022/07/15/the-week-the-open-web-won/) and they are itching to get in. Big Tech platforms and their lobbyists invest billions to convince lawmakers that the wild and open web is a threat to the safety of children and stability of society. They say only their walled gardens can be trusted, and lawmakers listen. Internal chaos in open source already has real-world impact outside the community: [Mess with critical infrastructure, and you invite deep scrutiny](https://www.cnn.com/2021/12/23/politics/white-house-log4j-tech-firms-meeting/index.html). Both WordPress and ACF have become critical infrastructure, powering sites for enterprise level businesses, educational institutions, and government entities small and large. [To lawmakers informed by Big Tech lobbyists the solution is obvious: Outside corporate control](https://mor10.com/open-source-considered-harmful/). For WordPress, what happens next is largely in the hands of a single man who is increasingly isolating himself and consolidating his power. His choice: Tighten the grip, or let governance in. Time will tell if the Rubicon has been crossed. I fear we are past the point of no return, but [I have hope and faith in the open source community and in their mutual solidarity](https://www.thewpcommunitycollective.com/). And to me, hope is a catalyst. I know it can be for you too. Stay true to your values my friends, and build the world you want to live in. #### By Morten Rand-Hendriksen Morten Rand-Hendriksen is a Senior Staff Instructor at [LinkedIn Learning](https://lnkd.in/mor10) (formerly [lynda.com](http://lynda.com/mor10) specializing in AI, bleeding edge web technologies, and the intersection between technology and humanity. He also occasionally teaches at [Emily Carr University of Art and Design](https://www.ecuad.ca/people/profile/304279). He is a popular conference and workshop speaker on all things tech ethics, AI, web technologies, and open source. [View Archive →](https://mor10.com/author/mor10-2/), Rubicon, Morten Rand-Hendriksen, 01ja8jax6y1exvddc5kg29mqz7.