Automattic's board forces CEO Matt Mullenweg into leave of absence
Automattic’s board has placed CEO and WordPress co‑founder Matt Mullenweg on a paid leave of absence after years of increasingly erratic public behavior and a highly contentious legal and PR battle with hosting provider WP Engine. Commenters debate whether his actions stem from burnout, arrogance, or legitimate grievances over “free‑riding” on WordPress, but broadly agree that his recent decisions have damaged trust in the WordPress ecosystem and forced the board’s hand. Many see the move as both overdue and risky, given his outsized control over the project and the platform’s importance to a large share of the web.
Immediate reactions to the leave of absence
- Many see the “paid leave” as a de facto firing, noting that public accusations against the board in a company-wide channel make a return unlikely.
- Some express relief, arguing his recent actions have been harmful to WordPress and Automattic’s reputation; others call it “unfortunate” given his past positive impact.
- A minority defend him as a major contributor to open source and a good leader internally, and view the pile-on as unfair or rooted in jealousy.
Executive behavior, accountability, and optics
- Commenters note that top executives are almost never “fired” publicly; they “step down,” “take a break,” or “spend more time with family” to avoid lawsuits and PR damage.
- There’s debate over whether executives face too few real consequences compared to low-level workers, with some prioritizing shareholder value, others prioritizing “truth and justice” even at financial cost.
Mental health vs personality
- Several argue his recent conduct (erratic public posts, self-sabotaging legal moves) looks like burnout or serious mental health trouble and hope he gets help.
- Others push back, saying this is armchair diagnosis and that his behavior can be explained by arrogance, vindictiveness, or simple unprofessionalism.
WP Engine, plugins, and trademark disputes
- A major chunk of discussion centers on his aggressive campaign against WP Engine: lawsuits, public shaming, plugin repository bans, and forking/hijacking of the ACF plugin slug.
- Opinions split: some see WP Engine as leeching off the ecosystem; others stress GPL means no obligation to “give back,” and that WP Engine contributed via plugins and the wider ecosystem.
- The “claiming the word ‘automatic’” narrative is seen by some as exaggerated; others still view the Automatic.css trademark move as overreach, though plausibly arguable in trademark law terms.
State of WordPress and future direction
- Many say WordPress “enshittified” years ago (Gutenberg criticism, plugin ecosystem bloat, security issues), though its dominance and WooCommerce still matter.
- Static site generators, alternative CMSes, Shopify, and tools like Webflow are repeatedly mentioned as more attractive options.
- Some think this board action is necessary to settle the WP Engine case and refocus on existential threats (including AI-driven changes to web publishing).
Governance and control questions
- There is confusion and debate about how a board can sideline a founder with huge voting control, with references to investor agreements, fiduciary duties, and the risk of a “corporate civil war” if he tries to fire the board.