The Motion to Dismiss—a Win for WP Engine  🔗 **Source:** [The Motion to Dismiss—a Win for WP Engine](https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/) > [!note]+ Document Notes > tags: > - #wordpress > - #legal > - #WPEngine > _ #lawsuit > - #MattMullenweg > - #open_source > Author: The Delta > Source: The Delta blog > Reference: https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ > date created: 2025-09-19 00:00 > > # Title: The motion to dismiss—a win for WP Engine > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references-1) - [🗣️ 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) - [🔍 DARVO Analysis Prompt](#-darvo-analysis-prompt) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - Judge Araceli Martínez-Olguín’s order (as summarized in the article) - WP Engine v. Automattic docket (contextual, link not provided in article) ## 📝 Summary: The article argues the court’s motion to dismiss is a net win for WP Engine. Of 20 claims in WP Engine’s First Amended Complaint, 4 were unopposed and proceed; the judge ruled on 16, allowing 13 of 20 to move forward now. Five dismissed claims can be reasserted immediately, one later, and only one claim was fully dismissed without leave to amend. Attempts to sever claims against Matt Mullenweg personally were rejected. The author anticipates a Second Amended Complaint curing deficiencies and reasserting allowed claims, with the case “soldiering on.” ## 📖 Main Content: - Procedural posture: Motion to dismiss decided by Judge Martínez-Olguín. Case proceeds largely intact. - Claims breakdown: - 20 total claims in First Amended Complaint (FAC). - 4 unopposed by Automattic → proceed regardless. - Court addressed 16 and left 13 total moving forward now. - Dismissals: 5 with leave to amend now, 1 with leave to reassert later, 1 dismissed with prejudice. - Severance request denied: Court declined to sever claims applicable only to Mullenweg; they remain connected to Automattic for now. - Litigation strategy: Plead many claims; expect some pruning. WP Engine expanded from 11 (original) to 20 (FAC), and even after pruning, more claims advance than in the original filing. - Framing: Contrary to takes calling it a “win” for Automattic, the author deems it a clear win for WP Engine. ### 🗒️ Notes - Motion outcome - Majority of the case continues. - Only one claim permanently out. - Unopposed claims - 4 claims go forward by default—strong leverage for WP Engine. - Amend-and-reassert path - Immediate: 5 claims can be cured and refiled. - Later: 1 claim can be revived at a subsequent stage. - Strategic implications - Discovery on 13+ claims increases pressure to settle. - Denial of severance keeps corporate and personal allegations intertwined. - Narrative correction - Public perception vs. legal reality: dismissal ≠ defeat when leave to amend exists. - Next steps - Expect a Second Amended Complaint reasserting cured claims. - Potential narrowing later at summary judgment, but breadth remains. ## 📖 References: - The Delta. “The motion to dismiss—a win for WP Engine.” https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ - Federal civil procedure on motions to dismiss and leave to amend (FRCP 12(b)(6), 15) for background. ## 🗣️ Paraphrase: - Original gist: “Some call this a ‘win’ for Automattic and Mullenweg; that’s provably false. WP Engine can cure deficiencies, file a Second Amended Complaint, and reassert most claims, so the vast majority will likely proceed.” - Paraphrase: Despite headlines favoring Automattic, the decision largely benefits WP Engine. Because the court permits amendment, WP Engine can fix pleading issues, refile, and keep most claims alive, likely sending many to trial. - Original gist: “Lawyers plead many claims expecting some to fall. WP Engine went from 11 to 20 claims. Even if reduced to 13, that still exceeds the original filing—another sign of momentum.” - Paraphrase: It’s standard practice to cast a wide net. WP Engine expanded its causes of action from 11 to 20; even trimmed to 13, that surpasses their initial scope, indicating procedural advantage. ## 📰 Newsletter: WordPress world got a civ-pro refresher this week. Judge Martínez-Olguín’s motion to dismiss in WP Engine v. Automattic leaves 13 of 20 claims moving forward, with WP Engine granted leave to fix and reassert most of the rest—and only one claim dismissed for good. A bid to sever claims tied solely to Matt Mullenweg was denied, keeping the action bundled. Translation: discovery is coming, not a curtain call. For learners, keep sharpening your PHP/JS tooling; legal clarity often lags product reality. Community notes: contribute to docs and testing—stable open source thrives on many hands. New plugins to explore: performance profilers and AI-assisted docs tools; vet licenses and community governance before adoption. Read the breakdown: The Delta’s analysis on why this is a net win for WP Engine: https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ ## ✅ Action Items: - Prompt for aligning articles with your role/aspirations: “Analyze how this article advances open-source advocacy and contributor engagement within the WordPress ecosystem. Identify: - Governance signals (licensing, trademarks, downstream use) affecting contributors and companies. - Educational opportunities to demystify legal processes (motions to dismiss, leave to amend, discovery) for developers. - Impacts on sustainability (funding models, stewardship, community trust). - Pathways to inclusive onboarding and transparent communications during disputes. - OSPO perspective: risk management, policy clarity, escalation playbooks, and contributor safety. - Speaking/teaching angles: workshops, curriculum modules, and documentation updates bridging legal context with technical practice. Deliver a short brief linking insights to: contributor experience, OSPO maturity, and concrete educational resources.” ## 🧪 Hypotheses: - H1: Public framing of interim rulings shapes contributor trust and participation more than the rulings themselves. - H2: Denial of severance increases settlement probability by raising discovery costs and reputational risk. - H3: Granting leave to amend correlates with higher ultimate claim survival into discovery. ### 📊 Methodology: - Data sources: Court dockets (PACER/RECAP), press/blog coverage, contributor activity metrics (GitHub, Make WP), plugin adoption data. - Designs: Event study around ruling dates; sentiment analysis of community forums; survival analysis of claims post–motion to dismiss. - Analysis: Difference-in-differences on contribution rates; logistic regression predicting settlement likelihood from severance outcomes. ### ❓ Questions: - How will discovery scope affect project governance and communication norms? - Does legal uncertainty deter enterprise adoption of specific WordPress components? - What contributor safeguards are needed during high-visibility disputes? ### 🔮 Future Research: - Longitudinal effects of legal disputes on open-source project health. - Best-practice OSPO playbooks for community communications during litigation. - Impact of severance decisions on executive-personal vs. corporate liability narratives. ### 💡 Implications: - Better legal-literacy education could stabilize contributor engagement. - Clear governance and licensing guidance may mitigate chilling effects on plugin/theme ecosystems. - OSPO-aligned policies can reduce risk and maintain community cohesion. ### 🧠 Learning Styles Assessment: - Readability: Upper high-school to college-level (legal-procedural vocabulary). - Visual: Minimal; add flowcharts of case posture and claim outcomes. - Aural: Add an audio summary or podcast segment. - Verbal: Strong explanatory tone; could add analogies for legal steps. - Kinesthetic: Include “try-it” exercises (map claims to remedies; simulate a motion timeline). - Logical: Provide a claims table, timelines, and decision trees. - Social: Link to discussion forums or office hours. - Solitary: Add reflection prompts on governance lessons. - Naturalistic: N/A; could use ecosystem analogies for resilience. ### 📊 Accessibility Assessment: - Screen readers: Ensure semantic headings and descriptive link text. - Keyboard navigation: Verify focus states and skip-links. - Contrast/readability: Use high contrast and legible font sizes. - Text resizing: Ensure responsive typography without layout breakage. - Alt text: Provide for any images/diagrams if added. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - Cultural relevance: Include global community perspectives, not just US legal framing. - Inclusive language: Maintain neutral, non-adversarial tone; define legal jargon. - Neurodiversity: Break into sections with bullet points and summaries. - Representation: Feature diverse voices in examples and linked resources. - Psychological safety: Add content warnings around legal/harassment topics; set norms for respectful discussion. ### ✅ Logical validity: - Positive reasoning: - Appeal to evidence: Quantifies outcomes (13 forward, 1 fully dismissed) to support “win” framing—strengthens claims; could add a clear table. - Causal reasoning: Leave to amend → likelihood of reassertion—plausible; bolster with precedent or stats. - Counterargument handling: Acknowledges opposing “Automattic win” narrative, refutes with data—coherent; add citations to alternate takes. - Logical flow: From summary → implications → next steps—clear; include a visual timeline. - Potential weaknesses: - Possible hasty generalization: “Provably false” without direct citation to docket specifics; improve by linking the order text. - Appeal to practice: “Lawyers plead many claims” is true but could become a weak appeal to common practice; add authority or data. - Tone: Confident, corrective, advocacy-leaning for WP Engine. 🔍 DARVO Analysis Prompt - Deny: The piece disputes the framing that Automattic “won,” denying that interpretation by citing claim counts and leave to amend. - Attack: No personal attacks; critiques are directed at the narrative, not individuals. - Reverse Victim/Offender: Minimal. The article centers on procedural posture, not victimhood framing. No role reversal rhetoric detected. - Notes: Tone is assertive but not defamatory; avoids ad hominem. Any “provably false” phrasing risks overstatement; recommend adding neutral qualifiers and direct quotes from the order. ### 🔍 SEO Evaluation: - Keywords: Present opportunities—“WP Engine,” “Automattic,” “motion to dismiss,” “Judge Martínez-Olguín,” “WordPress litigation.” Integrate naturally in title, intro, H2s. - Meta description: Add a 150–160 char summary with a primary keyword. - Title tag: Current title is strong; keep within 60 chars and include “motion to dismiss.” - Headers: Use H2/H3s for Summary, Claims Breakdown, Severance, Next Steps; include keywords. - Content length: Aim 1,200–1,800 words with a claims table for depth. - Links: Add internal links to prior coverage; external links to the court order and neutral analyses. - URL: Already concise and descriptive. - Images: Include a claims/outcome table image with alt text; compress assets. - Mobile: Ensure responsive layout and fast load (minify, lazy load). - Engagement: Add TL;DR, table of contents, and CTAs to subscribe/comment. - Schema: Use Article schema; consider FAQ for common legal questions. - Social: Ensure Open Graph/Twitter Cards with summary and image. ## 🎯 Conclusion: The motion to dismiss narrows but largely preserves WP Engine’s case: 13 claims proceed now, most dismissed claims can be reasserted, and only one is gone for good. Severance was denied, keeping pressure intact. Expect a Second Amended Complaint and a discovery-heavy next phase. For the WordPress community, the key is legal literacy, transparent governance, and sustained contributor support while the case advances. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/The Motion to Dismiss—a Win for WP Engine|Full Document Contents]] ## Document Notes --- tags: - #wordpress - #legal - #WPEngine _ #lawsuit - #MattMullenweg - #open_source Author: The Delta Source: The Delta blog Reference: https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ date created: 2025-09-19 00:00 --- # Title: The motion to dismiss—a win for WP Engine ## Table of Contents: - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes]] - [[#📖 References:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items:]] - [[#🧪 Hypotheses:]] - [[#📊 Methodology:]] - [[#❓ Questions:]] - [[#🔮 Future Research:]] - [[#💡 Implications:]] - [[#🧠 Learning Styles Assessment:]] - [[#📊 Accessibility Assessment:]] - [[#🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment:]] - [[#✅ Logical validity:]] - [[#🔍 DARVO Analysis Prompt]] - [[#🔍 SEO Evaluation:]] - [[#🎯 Conclusion:]] ### References: - Judge Araceli Martínez-Olguín’s order (as summarized in the article) - WP Engine v. Automattic docket (contextual, link not provided in article) ## 📝 Summary: The article argues the court’s motion to dismiss is a net win for WP Engine. Of 20 claims in WP Engine’s First Amended Complaint, 4 were unopposed and proceed; the judge ruled on 16, allowing 13 of 20 to move forward now. Five dismissed claims can be reasserted immediately, one later, and only one claim was fully dismissed without leave to amend. Attempts to sever claims against Matt Mullenweg personally were rejected. The author anticipates a Second Amended Complaint curing deficiencies and reasserting allowed claims, with the case “soldiering on.” ## 📖 Main Content: - Procedural posture: Motion to dismiss decided by Judge Martínez-Olguín. Case proceeds largely intact. - Claims breakdown: - 20 total claims in First Amended Complaint (FAC). - 4 unopposed by Automattic → proceed regardless. - Court addressed 16 and left 13 total moving forward now. - Dismissals: 5 with leave to amend now, 1 with leave to reassert later, 1 dismissed with prejudice. - Severance request denied: Court declined to sever claims applicable only to Mullenweg; they remain connected to Automattic for now. - Litigation strategy: Plead many claims; expect some pruning. WP Engine expanded from 11 (original) to 20 (FAC), and even after pruning, more claims advance than in the original filing. - Framing: Contrary to takes calling it a “win” for Automattic, the author deems it a clear win for WP Engine. ### 🗒️ Notes - Motion outcome - Majority of the case continues. - Only one claim permanently out. - Unopposed claims - 4 claims go forward by default—strong leverage for WP Engine. - Amend-and-reassert path - Immediate: 5 claims can be cured and refiled. - Later: 1 claim can be revived at a subsequent stage. - Strategic implications - Discovery on 13+ claims increases pressure to settle. - Denial of severance keeps corporate and personal allegations intertwined. - Narrative correction - Public perception vs. legal reality: dismissal ≠ defeat when leave to amend exists. - Next steps - Expect a Second Amended Complaint reasserting cured claims. - Potential narrowing later at summary judgment, but breadth remains. ## 📖 References: - The Delta. “The motion to dismiss—a win for WP Engine.” https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ - Federal civil procedure on motions to dismiss and leave to amend (FRCP 12(b)(6), 15) for background. ## 🗣️ Paraphrase: - Original gist: “Some call this a ‘win’ for Automattic and Mullenweg; that’s provably false. WP Engine can cure deficiencies, file a Second Amended Complaint, and reassert most claims, so the vast majority will likely proceed.” - Paraphrase: Despite headlines favoring Automattic, the decision largely benefits WP Engine. Because the court permits amendment, WP Engine can fix pleading issues, refile, and keep most claims alive, likely sending many to trial. - Original gist: “Lawyers plead many claims expecting some to fall. WP Engine went from 11 to 20 claims. Even if reduced to 13, that still exceeds the original filing—another sign of momentum.” - Paraphrase: It’s standard practice to cast a wide net. WP Engine expanded its causes of action from 11 to 20; even trimmed to 13, that surpasses their initial scope, indicating procedural advantage. ## 📰 Newsletter: WordPress world got a civ-pro refresher this week. Judge Martínez-Olguín’s motion to dismiss in WP Engine v. Automattic leaves 13 of 20 claims moving forward, with WP Engine granted leave to fix and reassert most of the rest—and only one claim dismissed for good. A bid to sever claims tied solely to Matt Mullenweg was denied, keeping the action bundled. Translation: discovery is coming, not a curtain call. For learners, keep sharpening your PHP/JS tooling; legal clarity often lags product reality. Community notes: contribute to docs and testing—stable open source thrives on many hands. New plugins to explore: performance profilers and AI-assisted docs tools; vet licenses and community governance before adoption. Read the breakdown: The Delta’s analysis on why this is a net win for WP Engine: https://www.delta.blog/the-motion-to-dismiss-a-win-for-wp-engine/ ## ✅ Action Items: - Prompt for aligning articles with your role/aspirations: “Analyze how this article advances open-source advocacy and contributor engagement within the WordPress ecosystem. Identify: - Governance signals (licensing, trademarks, downstream use) affecting contributors and companies. - Educational opportunities to demystify legal processes (motions to dismiss, leave to amend, discovery) for developers. - Impacts on sustainability (funding models, stewardship, community trust). - Pathways to inclusive onboarding and transparent communications during disputes. - OSPO perspective: risk management, policy clarity, escalation playbooks, and contributor safety. - Speaking/teaching angles: workshops, curriculum modules, and documentation updates bridging legal context with technical practice. Deliver a short brief linking insights to: contributor experience, OSPO maturity, and concrete educational resources.” ## 🧪 Hypotheses: - H1: Public framing of interim rulings shapes contributor trust and participation more than the rulings themselves. - H2: Denial of severance increases settlement probability by raising discovery costs and reputational risk. - H3: Granting leave to amend correlates with higher ultimate claim survival into discovery. ### 📊 Methodology: - Data sources: Court dockets (PACER/RECAP), press/blog coverage, contributor activity metrics (GitHub, Make WP), plugin adoption data. - Designs: Event study around ruling dates; sentiment analysis of community forums; survival analysis of claims post–motion to dismiss. - Analysis: Difference-in-differences on contribution rates; logistic regression predicting settlement likelihood from severance outcomes. ### ❓ Questions: - How will discovery scope affect project governance and communication norms? - Does legal uncertainty deter enterprise adoption of specific WordPress components? - What contributor safeguards are needed during high-visibility disputes? ### 🔮 Future Research: - Longitudinal effects of legal disputes on open-source project health. - Best-practice OSPO playbooks for community communications during litigation. - Impact of severance decisions on executive-personal vs. corporate liability narratives. ### 💡 Implications: - Better legal-literacy education could stabilize contributor engagement. - Clear governance and licensing guidance may mitigate chilling effects on plugin/theme ecosystems. - OSPO-aligned policies can reduce risk and maintain community cohesion. ### 🧠 Learning Styles Assessment: - Readability: Upper high-school to college-level (legal-procedural vocabulary). - Visual: Minimal; add flowcharts of case posture and claim outcomes. - Aural: Add an audio summary or podcast segment. - Verbal: Strong explanatory tone; could add analogies for legal steps. - Kinesthetic: Include “try-it” exercises (map claims to remedies; simulate a motion timeline). - Logical: Provide a claims table, timelines, and decision trees. - Social: Link to discussion forums or office hours. - Solitary: Add reflection prompts on governance lessons. - Naturalistic: N/A; could use ecosystem analogies for resilience. ### 📊 Accessibility Assessment: - Screen readers: Ensure semantic headings and descriptive link text. - Keyboard navigation: Verify focus states and skip-links. - Contrast/readability: Use high contrast and legible font sizes. - Text resizing: Ensure responsive typography without layout breakage. - Alt text: Provide for any images/diagrams if added. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - Cultural relevance: Include global community perspectives, not just US legal framing. - Inclusive language: Maintain neutral, non-adversarial tone; define legal jargon. - Neurodiversity: Break into sections with bullet points and summaries. - Representation: Feature diverse voices in examples and linked resources. - Psychological safety: Add content warnings around legal/harassment topics; set norms for respectful discussion. ### ✅ Logical validity: - Positive reasoning: - Appeal to evidence: Quantifies outcomes (13 forward, 1 fully dismissed) to support “win” framing—strengthens claims; could add a clear table. - Causal reasoning: Leave to amend → likelihood of reassertion—plausible; bolster with precedent or stats. - Counterargument handling: Acknowledges opposing “Automattic win” narrative, refutes with data—coherent; add citations to alternate takes. - Logical flow: From summary → implications → next steps—clear; include a visual timeline. - Potential weaknesses: - Possible hasty generalization: “Provably false” without direct citation to docket specifics; improve by linking the order text. - Appeal to practice: “Lawyers plead many claims” is true but could become a weak appeal to common practice; add authority or data. - Tone: Confident, corrective, advocacy-leaning for WP Engine. 🔍 DARVO Analysis Prompt - Deny: The piece disputes the framing that Automattic “won,” denying that interpretation by citing claim counts and leave to amend. - Attack: No personal attacks; critiques are directed at the narrative, not individuals. - Reverse Victim/Offender: Minimal. The article centers on procedural posture, not victimhood framing. No role reversal rhetoric detected. - Notes: Tone is assertive but not defamatory; avoids ad hominem. Any “provably false” phrasing risks overstatement; recommend adding neutral qualifiers and direct quotes from the order. ### 🔍 SEO Evaluation: - Keywords: Present opportunities—“WP Engine,” “Automattic,” “motion to dismiss,” “Judge Martínez-Olguín,” “WordPress litigation.” Integrate naturally in title, intro, H2s. - Meta description: Add a 150–160 char summary with a primary keyword. - Title tag: Current title is strong; keep within 60 chars and include “motion to dismiss.” - Headers: Use H2/H3s for Summary, Claims Breakdown, Severance, Next Steps; include keywords. - Content length: Aim 1,200–1,800 words with a claims table for depth. - Links: Add internal links to prior coverage; external links to the court order and neutral analyses. - URL: Already concise and descriptive. - Images: Include a claims/outcome table image with alt text; compress assets. - Mobile: Ensure responsive layout and fast load (minify, lazy load). - Engagement: Add TL;DR, table of contents, and CTAs to subscribe/comment. - Schema: Use Article schema; consider FAQ for common legal questions. - Social: Ensure Open Graph/Twitter Cards with summary and image. ## 🎯 Conclusion: The motion to dismiss narrows but largely preserves WP Engine’s case: 13 claims proceed now, most dismissed claims can be reasserted, and only one is gone for good. Severance was denied, keeping pressure intact. Expect a Second Amended Complaint and a discovery-heavy next phase. For the WordPress community, the key is legal literacy, transparent governance, and sustained contributor support while the case advances. ## Highlights - The motion to dismiss—a win for WP Engine ([View Highlight](https://read.readwise.io/read/01k5gxe5tbpa1p8r7stbv4rfts)) - One thing that’s very important to keep in mind is that lawyers are taught to plead as many claims as possible, knowing that some will not make it to trial, getting dismissed for varying reasons. That is what WP Engine’s lawyers did here—their original complaint had just 11 claims, which they expanded within their First Amended Complaint to 20 claims. If, in the end, the judge narrows the case to just 13 claims—and, again, I think it’s likely that WP Engine will re-assert claims and more than 13 will make it to trial—WP Engine is moving forward with more claims than their original filing! ([View Highlight](https://read.readwise.io/read/01k5h057vvab8fh76w9h0dbw7x)) - With at least 13 claims moving to trial and just 1 claim completely dismissed, **this ruling is a significant win for WP Engine and their lawyers**.⁠⁠ That said, let’s look at the judge’s rulings individually, which I’ll cover in the same order she did. ([View Highlight](https://read.readwise.io/read/01k5gxf58ywq7yp41qz66s2n20))