Matt Mullenweg, co-founder of WordPress and CEO of Automattic, has taken a decisive step by directing core committers to include the Akismet spam plugin on the new Connectors screen in WordPress 7.0. This move overrules a previous decision to revert the plugin’s inclusion, a decision that had been supported by several core committers.
## The Akismet Plugin and WordPress
Akismet, developed by Automattic, is a widely-used spam filtering plugin designed to protect WordPress sites from unwanted content. It has been part of the WordPress ecosystem for two decades, blocking billions of spam attempts. The decision to include Akismet as a default connector on the Connectors screen, even before activation, aligns it with AI service providers like OpenAI and Google. This inclusion aims to streamline user experience by allowing activation and key entry directly from the Connectors screen.
## Context and Controversy
The decision to include Akismet sparked debate within the WordPress community. Core committer Peter Wilson argued that Akismet should register its own connector via the plugin API, as other plugins do. Concerns were also raised about potential duplicate entries and the lack of public discussion prior to the commit. The debate intensified when it was revealed that the commit had been made during the release candidate period without formal approval.
Matt Mullenweg’s intervention highlighted the long-standing contributions of Akismet and Automattic to WordPress. He questioned why similar scrutiny was not applied to other connectors like OpenAI and Anthropic, which have not contributed to the WordPress project. Mullenweg’s comments emphasized the need to recognize contributions rather than obstruct them.
## Implications for the Industry
This development underscores the ongoing tensions in open-source communities regarding governance and decision-making processes. The inclusion of Akismet as a default connector reflects a broader trend of integrating essential services directly into core platforms to enhance user experience. It also raises questions about the criteria for inclusion and the processes that govern such decisions.
The controversy may prompt a reevaluation of how plugins are integrated into WordPress, potentially leading to new guidelines in future releases. The broader policy question of how non-AI plugins should register connectors has been deferred to the 7.1 cycle, indicating that discussions will continue.
As WordPress continues to evolve, the handling of this situation may influence future governance decisions and the role of key contributors like Automattic in shaping the platform’s direction.
