WPEngine, Inc. v. Automatic Inc. et al.  ## Metadata - Author: [[WPEngine, Inc., Automatic Inc., Matthew Mullenweg]] - Full Title: WPEngine, Inc. v. Automatic Inc. et al. - Category: #articles - Document Note: --- tags: [#WordPress, #Litigation, #Antitrust] Author: Jointly submitted by WPEngine, Inc. and Automattic Inc. Source: United States District Court, N.D. California Reference: Case No. 3:24-cv-06917-AMO, ECF No. 154 date created: 2025-08-08 12:15 --- # Title: WPEngine, Inc. v. Automattic Inc. et al. – Joint Letter Brief on Discovery Disputes ## 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-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: This joint letter brief presents a discovery dispute between **WPEngine, Inc. (WPE)** and **Automattic Inc. & Matthew Mullenweg (Defendants)** over responses to specific Requests for Production (RFPs). WPE alleges Defendants engaged in a "nuclear war" to harm WPE’s business—cutting off access to WordPress.org, interfering with customers, and making defamatory statements. Defendants argue WPE is overreaching in scope and timelines, refusing compromises, and ignoring proportionality principles. --- ## 📖 Main Content: ### 🗒️ Notes **[0:00–Section I: WPE’s Position]** - WPE claims Defendants: - Ignored RFPs for ~4 months, waiving objections. - Imposed arbitrary limits to avoid disclosing pre/post-"war" conduct. - Restricted to “sufficient to show” documents, obscuring evidence scope. - Core claims involve: - **Tortious interference** with customers (RFPs 12–15, 19, 98, 100). - **Market manipulation** and control of WordPress.org (RFPs 71, 103–105). - **Defamation** (RFPs 50, 88, 90–91). - **Extortion disguised as trademark licensing** (RFPs 17, 23, 114–115). **[Customer Interference RFPs]** - WPE wants documents beyond Dec 10, 2024 (post-PI order) to detect ongoing violations. - Objects to Defendants’ conditions & “sufficient to show” limits. **[Market Manipulation RFPs]** - Wants continuous WordPress.org metrics, not one-day snapshot. - Rejects arbitrary date limits (wants 2005–present for some RFPs). **[Defamation RFPs]** - Seeks proof Defendants knew statements (“parasitic,” “40 hours/week,” “$75k”) were false. - Wants records dating back to 2010. **[Extortion RFPs]** - Seeks planning docs for alleged 8% revenue demand under guise of trademark license. **Relief Requested:** Full production within 21 days. --- **[0:00–Section II: Defendants’ Position]** - Argue WPE: - Has produced far fewer docs (4,007 vs. Defendants’ 16,000+). - Is prematurely escalating issues without compromise. - Court already rejected WPE’s “waiver” argument. - Propose: - **Customer RFPs:** Jan 1, 2023–Dec 10, 2024. - **Trademark RFPs:** Jan 1, 2010–present, all negotiations covered under broader RFP 45. - **WordPress.org RFPs:** 2020–present; 20-year scope is disproportionate. - **Defamation RFPs:** Six-year lookback (align with RFP 92). - **End Dates:** Dec 10, 2024 cutoff unless ongoing conduct proven. - Label some WPE issues as “nonissues.” --- ## 📖 References: - WPEngine, Inc. v. Automattic Inc. et al., No. 3:24-cv-06917-AMO, N.D. Cal. - Relevant statutes: 15 U.S.C. § 15b (antitrust statute of limitations). --- ## 🗣️ Paraphrase: 1. **WPE’s stance:** Defendants have dodged producing critical discovery for eight months, hiding the breadth of their anti-competitive “war,” including customer poaching, WordPress.org exclusion, and defamatory attacks. They must produce all responsive documents without arbitrary cutoffs or “sufficient to show” limitations. 2. **Defendants’ stance:** WPE is exaggerating disputes and stonewalling itself. The proposed timeframes and scope are reasonable and proportional. Broader requests are unnecessary and burdensome. --- ## 📰 Newsletter: **⚖️ WP Legal Watch:** Big developments in the WPEngine vs. Automattic case. WPE claims Automattic waged a “nuclear war” — poaching customers, blocking WordPress.org access, and spreading falsehoods. Automattic counters that WPE’s discovery demands are overbroad and disproportionate. The fight now centers on how far back document searches must go (WPE wants up to 20 years, Automattic says 4–6). This battle could shape how competitive practices in open-source ecosystems are litigated. 🔗 [Case Docket](#) --- ## ✅ Action Items: - Track case for potential precedent on open-source platform control. - Prepare thought leadership on **governance and competitive fairness** in open-source. - Use findings to inform **WordPress community governance** talks. - Highlight for OSPO director pathway—case is a real-world test of **platform power disputes**. --- ## 🧪 Hypotheses: - If courts compel broader historical data, discovery norms in open-source antitrust cases may expand. - Limiting end dates could shield ongoing anti-competitive behavior. ### 📊 Methodology: - Legal document review, deposition analysis, expert economic modeling. ### ❓ Questions: - How will the court balance proportionality vs. completeness? - Could this case set antitrust precedent in open-source governance? ### 🔮 Future Research: - Historical role of centralized repositories in market control. - Comparative governance models mitigating monopolization risks. ### 💡 Implications: - Broader discovery could expose long-term competitive strategies. - Narrow rulings may embolden dominant players. --- ## 🧠 Learning Styles Assessment: - **Visual:** None in doc; suggest timeline charts of alleged conduct. - **Aural:** No audio—could use court audio summaries. - **Verbal:** Strong legal narrative, but dense; could add layperson glossary. - **Kinesthetic:** No interactive—could create discovery scope mapping exercise. - **Logical:** Arguments structured, but could benefit from data tables. - **Social:** Cooperative negotiation examples limited; could model better meet-and-confer processes. - **Solitary:** Allows for deep individual study. - **Naturalistic:** No environmental analogies; could add to explain ecosystem impacts. --- ## 📊 Accessibility Assessment: - **Screen Reader:** Likely fine (text-only). - **Keyboard Navigation:** Not relevant here. - **Contrast:** Court docs in black/white—accessible. - **Improvement:** Provide alt text for any referenced charts in public filings. --- ## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance:** Neutral legal tone. - **Inclusive Language:** Formal and gender-neutral. - **Neurodiversity:** Dense blocks could be broken down for clarity. - **Representation:** Not applicable—focus is on corporate entities. --- ## ✅ Logical validity: - **WPE’s reasoning:** Strong causal link arguments; risk of *appeal to emotion* with “nuclear war” framing. - **Defendants’ reasoning:** Strong proportionality argument; possible *red herring* when comparing document counts without addressing relevance. --- ## 🔍 DARVO Analysis: - **Deny:** Defendants deny overreach, shift blame to WPE for low production. - **Attack:** Suggest WPE is acting unreasonably, exaggerating. - **Reverse Victim/Offender:** Portray WPE as aggressor in discovery, not victim. --- ## 🔍 SEO Evaluation: - **Keywords:** “WordPress.org,” “discovery dispute,” “antitrust,” “tortious interference.” - **Meta Description:** Should highlight “WPEngine alleges Automattic engaged in anti-competitive conduct in WordPress.org access.” - **Title Tag:** Include “WPEngine v Automattic – Discovery Dispute.” - **Internal Links:** Link to case docket and related filings. --- ## 🎯 Conclusion: This filing encapsulates a broader struggle over discovery scope in a high-profile open-source antitrust case. The outcome could influence how courts handle historical data - URL: https://readwise.io/reader/document_raw_content/348621867 Full text of this document omitted because this document is a PDF [Download original file →](https://readwise.io/reader/document_raw_content/348621867), WPEngine, Inc. v. Automatic Inc. et al., WPEngine, Inc., Automatic Inc., Matthew Mullenweg, 01k257bxa78k58jr9dj6pw39zf.