/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Automattic plans to cut its WordPress contributions to ~45 hours per week “due to the lawsuits from WP Engine”, focusing mostly on security and critical updates

Automattic has always been deeply committed to the success of WordPress, dedicating significant resources and talent to its development for almost two decades.

Automattic

Context & Ripple Effects

The cut follows a dispute in which Automattic sought a revenue-linked trademark arrangement from WP Engine, which WP Engine declined, before WP Engine sued Automattic and WordPress co-founder Matt Mullenweg.

The conflict has already raised questions about the project’s open-source governance after criticism of Automattic’s revenue demand from WP Engine. Redirecting work toward security and critical updates makes the operational cost of that dispute more visible to the broader WordPress ecosystem.

First-order effects

  • WordPress loses most of Automattic’s discretionary development time for now; the company says its remaining work will concentrate on security and critical updates.
  • Automattic shifts its WordPress contribution posture from broad stewardship toward a narrower maintenance role while the WP Engine litigation is unresolved.

Second-order effects

  • Hosting companies, plugin makers, and other WordPress contributors may need to absorb more of the work behind non-critical improvements that Automattic would otherwise have supported.
  • A security-first upstream focus increases the importance of coordinated patching across the ecosystem, even as feature development receives less attention.

Third-order effects

  • If litigation repeatedly changes the level of contribution from a major sponsor, WordPress’s governance model faces a sharper test: whether community and commercial participants can sustain development without relying on one company’s discretionary labor.
  • The dispute points to a broader tension in open source between trademark and platform control on one side and the expectations of commercial ecosystem participants on the other.

The trend: Open-source platforms are being tested by whether legal and commercial disputes can disrupt the stewardship resources that their wider ecosystems depend on.

Discussion

  • @gergely.pragmaticengineer.com Gergely Orosz on bluesky
    Full announcement: automattic.com/2025/01/09/a...  Anyone looking for a stable ecosystem - with players acting rationally - will likely keep steering away from WordPress.  —  A summary of stranger and stranger events within WordPress: blog.pragmaticengineer.com/did- automatt...
  • @ernie.tedium.co Ernie Smith on bluesky
    Talk about taking your ball and going home.  —  automattic.com/2025/01/09/a...
  • @tante.cc @tante.cc on bluesky
    Matt Mullenweg is still in his midlife crisis, 2025 edition:  —  Automattic publicly announces it will massively reduce its contributions to the WordPress open source project and focus on their proprietary offerings.  —  automattic.com/2025/01/09/a...
  • @adrienneleigh Adrienne on bluesky
    @eaton.fyi @questauthority.bsky.social ahahahahahahah Matt continues to throw his toys out of the pram:
  • @josh412.com Josh Pollock on bluesky
    LOL, WordPress announcing that they were no longer contributing to WordPress was actually something I had on my 2025 Bingo card.
  • r/WPDrama r on reddit
    Automattic will reduce its contributions to WordPress to 45 hours a week, focus on for-profit projects within Automattic instead: WordPress.com, Pressable, WPVIP, Jetpack, and WooCommerce
  • r/Wordpress r on reddit
    Automattic will reduce its contributions to WordPress to 45 hours a week, focus on for-profit projects within Automattic instead: WordPress.com, Pressable, WPVIP, Jetpack, and WooCommerce