Automattic says it will resume contributing to the WordPress project, after announcing a pause in April
· — After pausing our contributions to regroup, rethink … Bluesky: Ernie Smith / @ernie.tedium.co : Not exactly giving folks a clear idea of what's what [embedded post] X: David Risley / @davidrisley : Good decision. But, frankly, seems like the good decisions lately are just reversals of Matt's hissy fits. @automattic : After pausing our contributions to regroup, rethink, and plan strategically, we're ready to press play again and return fully to the WordPress project. Expect to find our contributions across all of the greatest hits—WordPress Core, Gutenberg, Playground, Openverse, and Kevin Jahns / @kevin_jahns : This message really made my day. @Automattic continues to invest in Open Source, even if their competitors do not. I feel that this is a really strong stance to take. Prashant Baldha / @prashant_baldha : @automattic Thank you for resuming your contributions to WordPress. WordPress's future is bright, thanks to the contribution of @automattic. I hope that @automattic will become the most significant contributor company to @WordPress soon. I hope that WordPress reach beyond the 50% market Katie Keith / @katiekeithbarn2 : Wonderful and unexpected news - a positive sign for the future of WordPress. I'm curious about what led to the change in direction. I suspect Mary's been more involved lately and if so, it's great to see her being listened to and empowered to make decisions. Forums: Msmash / Slashdot : Automattic Says It Will Start Contributing To WordPress Again After Pause
Context & Ripple Effects
Automattic’s return reverses its January plan to reduce WordPress work to roughly 45 hours a week amid litigation with WP Engine, a move that had narrowed its stated focus to security and critical updates. The subsequent 16% workforce reduction adds operational context for why the pause and restart matter to projects maintained by Automattic teams.
The decision also follows the dispute in which WordPress took control of the Advanced Custom Fields plugin from WP Engine. Together, the episodes have put unusual attention on how much the project’s development cadence depends on Automattic’s choices.
First-order effects
- Automattic will again direct staff contributions across WordPress Core, Gutenberg, Playground and Openverse, restoring capacity after the April pause.
- WordPress contributors and users regain a clearer signal that Automattic intends to participate broadly rather than limit work to essential maintenance.
Second-order effects
- Plugin developers, hosts and agencies can plan against a less constrained upstream roadmap, particularly around the named WordPress components.
- The reversal may intensify scrutiny of Automattic’s influence over project priorities: the earlier reduction in contributions showed how a corporate participant’s resource decisions can quickly affect a community project.
Third-order effects
- If contribution levels continue to swing with Automattic’s commercial and legal priorities, WordPress’s nominally open-source governance will face recurring questions about resilience and the distribution of maintainer power.
- The broader test is whether the ecosystem develops more independent maintenance capacity or remains structurally reliant on one company’s staffing decisions.
The trend: This is one instance of open-source infrastructure becoming more visibly shaped by the strategic constraints of its largest corporate steward.