SECURITY Signal 38
Automattic reportedly removes board members after failed attempt to oust CEO Matt Mullenweg
Automattic’s board members who voted to place CEO Matt Mullenweg on leave have reportedly been removed from their positions
This board shakeup shifts governance control to Mullenweg, potentially altering Automattic’s strategic direction and internal decision-making. For engineers relying on WordPress or Automattic’s ecosystem, the stability of leadership and open-source commitments may now face renewed scrutiny.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The board members who voted to oust Mullenweg were reportedly removed after his return to the CEO role
Automattic’s leadership confirmed Mullenweg’s reinstatement but declined to comment on specific board changes
The failed ouster attempt follows an ongoing lawsuit with WP Engine over WordPress trademark and contribution disputes
THE READ
What the cluster adds up to.
Automattic’s board has been restructured following an internal conflict where a majority of members voted to place CEO Matt Mullenweg on leave. The removal of these board members, reportedly those who supported the ouster, consolidates Mullenweg’s authority over the company. This shift may resolve immediate governance disputes but raises questions about long-term oversight and accountability within Automattic’s leadership.
The timing of this shakeup coincides with an ongoing legal battle between Automattic and WP Engine, a WordPress hosting provider. Mullenweg has accused WP Engine of trademark infringement and insufficient contributions to the open-source WordPress project, while WP Engine has countered with allegations of evidence destruction. The board’s attempt to oust Mullenweg may have been influenced by these external pressures, though the exact motivations remain unclear.
For engineers and organizations dependent on WordPress or Automattic’s tools, this leadership change could signal a period of instability or renewed focus on Mullenweg’s vision. The removal of dissenting board members suggests a more centralized decision-making process, which may accelerate or disrupt existing roadmaps. However, the lack of transparency around the board’s removal leaves open questions about future governance and stakeholder trust.
The broader implications for the WordPress ecosystem are uncertain. Mullenweg’s reinstatement reaffirms his control over Automattic’s direction, but the failed ouster attempt highlights underlying tensions. If these tensions persist, they could impact collaboration with external contributors, plugin developers, or hosting partners. The outcome of the WP Engine lawsuit may further shape Automattic’s stance on open-source contributions and trademark enforcement.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗