Automattic, under the leadership of its co-founder Matt Mullenweg, who also co-founded WordPress, has decided to drastically slash its weekly contribution hours from a staggering 3,988 to just 45. This shift aligns with their participation in the ‘Five for the Future’ initiative, which encourages companies to dedicate 5% of their resources back to WordPress [.org]. The focus of these remaining hours, according to Automattic, will primarily be on “security and critical updates,” a strategic pivot amidst their ongoing tussles.

The backdrop to this decision is a heated legal battle with WP Engine, a competitor in the WordPress hosting space. Mullenweg previously lambasted WP Engine for what he perceived as insufficient contributions to the WordPress ecosystem, accusing them of being a “cancer” to the community. This accusation came after WP Engine was found contributing only about 40 hours per week, a figure that pales in comparison to Automattic’s previous commitment.

The legal feud began when Mullenweg launched a public critique of WP Engine at a WordCamp event in September last year, leading to a series of retaliatory actions. Automattic blocked WP Engine from accessing WordPress [.org] resources, including crucial plugin updates, which prompted WP Engine to sue Automattic and Mullenweg for what they described as an abuse of power and attempted extortion. A California district court judge later sided with WP Engine, granting them an injunction to restore access to WordPress [.org] resources, highlighting the contentious nature of Mullenweg’s actions.

The financial and temporal toll of this legal skirmish has been cited by Automattic as a major reason for reallocating their resources:

We’ve made the decision to reallocate resources due to the lawsuits from WP Engine. This legal action diverts significant time and energy that could otherwise be directed toward supporting WordPress’s growth and health. We remain hopeful that WP Engine will reconsider this legal attack, allowing us to refocus our efforts on contributions that benefit the broader WordPress ecosystem.

Moreover, this isn’t just about legal battles. The internal response within Automattic has been telling. Last year, following Mullenweg’s aggressive stance, the company offered a severance package to employees who disagreed with the direction, leading to the exit of 159 staff members, a significant portion from the WordPress-focused division. This move was seen as an attempt to streamline the company’s direction amidst controversy.

Adding to the internal shakeup, this week saw the dissolution of WordPress’s sustainability team, a decision that has drawn criticism, including from notable tech journalist Kara Swisher. The move was justified by Mullenweg in a Slack message, stating the team had not met its goals, signaling perhaps a broader shift in focus or strategy under Automattic’s stewardship.

The community’s reaction has been mixed, with some seeing this as a necessary recalibration post-legal battles, while others worry about the future health and governance of WordPress, one of the internet’s foundational platforms. The reduction in contributions, especially in areas like core development and innovation, might lead to slower updates and less community engagement, potentially affecting WordPress’s evolution.