An Incoming Preliminary Injunction Against Automattic & Matt Mullenweg  Full Document Contents/Articles/An Incoming Preliminary Injunction Against Automattic & Matt Mullenweg.md, An Incoming Preliminary Injunction Against Automattic & Matt Mullenweg, Samuel Sidler. > [!note]+ Document Notes > tags: [legal-disputes, wordpress, wpengine, automattic, injunction, darvo] > - #legal-disputes > - #wordpress > - #wpengine > - #automattic > - #injunction > Author: [Nithin Sreeraj] > Source: [Delta Blog Post](https://www.delta.blog/an-incoming-preliminary-injunction-against-automattic-matt-mullenweg/) > Reference: [Original Article](https://www.delta.blog/an-incoming-preliminary-injunction-against-automattic-matt-mullenweg/) > date created: 2024-11-29 16:45 > > # WP Engine v. Automattic: Judge Signals Support for WP Engine in Preliminary Injunction Hearing > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) - [🗒️ Notes](#%EF%B8%8F-notes) - [📖 References](#%EF%B8%8F-references) 3. [🗣️ Paraphrase](#%EF%B8%8F-paraphrase) 4. [🔍 DARVO Analysis](#-darvo-analysis) 5. [✅ Logical Validity](#%E2%9C%85-logical-validity) 6. [🎯 Conclusion](#%F0%9F%8E%AF-conclusion) --- ## 📝 Summary: The ongoing legal battle between WP Engine and Automattic revolves around trademark licensing, blocked plugin access, and claims of unfair demands. Judge Araceli Martínez-Olguín has expressed her inclination to issue a preliminary injunction, but challenges remain in defining its specifics. Both parties are required to submit revised proposals by December 2, 2024. --- ## 📖 Main Content: ### 🗒️ Notes: #### Key Legal Issues: 1. **Preliminary Injunction**: - Judge Martínez-Olguín confirmed her intent to issue an injunction but criticized WP Engine's proposed order as excessively vague. - Both parties were instructed to collaborate or submit separate drafts for the injunction by December 2, 2024. 2. **Trademark Licensing**: - WP Engine has used WordPress.org resources freely for 15 years without paying fees. - Automattic argues WP Engine must comply with trademark licensing by either paying fees or providing volunteer hours. - Automattic revealed the existence of multiple sub-licenses, raising transparency concerns. 3. **Blocked Access**: - WP Engine’s ability to upload and manage plugins on WordPress.org was restricted. - Automattic clarified that WP Engine retains access to basic WordPress software and plugins but cannot utilize enhanced services for plugin management. 4. **Ransom Allegation**: - WP Engine labeled Automattic’s demand for 8% of its revenue ($32 million) as ransom. - Automattic justified the figure as an analysis of WP Engine’s cash flow, but no prior invoices were sent. 5. **Interim Solutions**: - WP Engine implemented a “mirror” system to maintain plugin updates but described it as costly and unsustainable. #### Observations on Judge Martínez-Olguín: - Judge AMO demonstrated preparedness, adaptability, and a willingness to ask clarifying questions. - Emphasized adherence to procedural rules, noting late filings and improper objections. #### Future Developments: - Revised injunction drafts due December 2, 2024. - Judge likely to issue a decision before the week’s end. --- ## 📖 References: - [Delta Blog Post](https://www.delta.blog/an-incoming-preliminary-injunction-against-automattic-matt-mullenweg/) - [PACER Filings](https://pacer.uscourts.gov) - [Case Law Citations](https://casetext.com) --- ## 🗣️ Paraphrase: 1. **WP Engine’s Argument**: WP Engine argued that its longstanding, free use of WordPress.org aligns with community norms. The abrupt imposition of licensing requirements jeopardized their operations. 2. **Automattic’s Counter**: Automattic defended its licensing enforcement as standard practice and dismissed allegations of extortion, emphasizing that community norms don’t exempt WP Engine from compliance. --- ## 🔍 DARVO Analysis: ### Objective: Identify instances where Deny, Attack, Reverse Victim and Offender (DARVO) tactics may have been used during the legal proceedings or in public communications. ### **1. Deny**: - **Observed Behavior**: - Automattic denied claims of ransom, framing the 8% revenue demand as a calculated business decision rather than extortion. - Automattic emphasized the availability of WordPress.org resources to counter WP Engine’s claims of restricted access. - **Impact**: - Denials attempt to diminish the gravity of WP Engine’s allegations, potentially shifting focus from the harm caused to procedural justifications. ### **2. Attack**: - **Observed Behavior**: - Automattic’s legal counsel highlighted WP Engine’s alleged trademark violations, including recent website edits to remove improper usage. - Public statements by Matt Mullenweg accused WP Engine of exaggerating claims and engaging in unhealthy competition. - **Impact**: - Attacks on WP Engine’s compliance history and business motives could undermine their credibility in court and within the WordPress community. ### **3. Reverse Victim and Offender**: - **Observed Behavior**: - Automattic framed WP Engine’s lawsuit as a baseless attempt to resist fair competition and compliance with trademark policies. - By portraying WP Engine as resistant to standard licensing practices, Automattic positioned itself as the victim of an unwarranted legal battle. - **Impact**: - Shifting blame may distract from Automattic’s responsibility to foster community trust and transparency in trademark enforcement. ### Patterns and Tone: - **Language Use**: Automattic’s legal counsel used measured but assertive language to challenge WP Engine’s claims, while Mullenweg’s public statements leaned toward dismissive and combative tones. - **Logical Fallacies**: Automattic’s arguments occasionally veered into strawman territory, mischaracterizing WP Engine’s claims as resistance to competition rather than addressing the core trademark issues. ### Recommendations: 1. Automattic should adopt a more transparent approach to trademark licensing, including public disclosure of sub-licenses. 2. Avoid personal attacks or exaggerated claims in public statements to maintain professionalism and credibility. --- ## ✅ Logical Validity: ### Strengths: - WP Engine’s historical reliance on WordPress.org aligns with community norms, bolstering their argument for consistent treatment. - Automattic’s insistence on procedural compliance reflects sound legal reasoning. ### Weaknesses: - WP Engine’s ransom allegations risk being interpreted as hyperbole without supporting evidence. - Automattic’s defense lacks sufficient explanation for the abruptness of licensing demands. --- ## 🎯 Conclusion: The WP Engine v. Automattic case highlights critical tensions between open-source community norms and trademark enforcement. Judge Martínez-Olguín’s forthcoming decision will set a precedent for managing these conflicts in the WordPress ecosystem. <!-- deep-read:sections end --> ## Highlights - Judge AMO came well-prepared, was able to adjust her temperament and tone to meet the specific situation, and was curious and willing to listen, knowing her blind spots. ([View Highlight](https://read.readwise.io/read/01jdwaxkr0qwkhrk9bdbs3wsvp)) - Given the technical complexity of this case, the judge recognizes that she is not the best person to draft the order for a preliminary injunction—it’s better if the two parties (WP Engine and Automattic) draft one together, that the judge can modify or sign as-is. ([View Highlight](https://read.readwise.io/read/01jdwazpqrdm4vh8vansx6hsyf)) - *I do not believe this will happen*. I find it incredibly unlikely that Automattic will negotiate in good faith to draft a reasonable preliminary injunction, given what we’ve seen from them over the past ~2 months. ([View Highlight](https://read.readwise.io/read/01jdwazx38ddsfx7e9ga3fsjgn)) - to the extent that she is an extension of me, you all should treat her with more respect. ([View Highlight](https://read.readwise.io/read/01jdwb2h4pvrdyj5py1bt1axk3)) - To be clear, any actions that happen after briefings are filed cannot be considered within the hearing. In this instance, the judge firmly, but politely, reminded counsel of this and kept things moving. This was never going to be a “big deal”, but it’s good to see Judge AMO establishing the bounds on both sides. ([View Highlight](https://read.readwise.io/read/01jdwb44m2qjtnz3zj5qw7gxe2)) - Let’s hope Judge AMO does not need to treat counsel like children for the *entirety* of this case. ([View Highlight](https://read.readwise.io/read/01jdwb5a1zt7ckc5kpbccqzp14)) - Early in the saga that started on September 20, we heard that Newfold Digital has a sub-license to use the WordPress trademark in specific ways. ([View Highlight](https://read.readwise.io/read/01jdwb5n0hratf673pex2qz3cc)) - It is both interesting and *refreshing* to know that Judge AMO has an upcoming antitrust trial, as it will help prepare her for making effective and balanced decisions on antitrust claims. ([View Highlight](https://read.readwise.io/read/01jdwb6xca6tmne5mtqxzbhqa9)) - In re-streaming, Mullenweg may have broken [the court rules](https://www.cand.uscourts.gov/media/court-rules-affecting-the-media/?ref=delta.blog) which, for [Zoom video conferences](https://www.cand.uscourts.gov/zoom/?ref=delta.blog), explicitly prohibit [recording or rebroadcasting of court proceedings](https://www.cand.uscourts.gov/notices/access-to-court-hearings/?ref=delta.blog) (my emphasis): ([View Highlight](https://read.readwise.io/read/01jdwb7rh3j2ngtqkbmc9zche3)) - If you share when your internet dropped maybe we can help you fill out the transcript for the parts you missed, **I think we have our own recordings**. ([View Highlight](https://read.readwise.io/read/01jdwb86qqpnx25s2re98kq9ba))