Catching up on Slack messages during a flight home from WordCamp Asia, Matt Mullenweg found a ten-day-old message about a disputed ticket involving Akismet and WordPress 7.0. What followed was not a quiet resolution. Mullenweg posted a wide-ranging critique in the core committers channel, described WordPress’s recent output as “boring or mediocre crap,” said “the wheels have fallen off” in terms of how the project operates, and then reversed a decision that core committers had already made, directing that Akismet appear on the WordPress 7.0 Connectors screen.
The underlying dispute centered on process rather than the feature itself. An Automattic-sponsored contributor had committed Akismet as a default connector during the release candidate phase without the standard review and consensus-building that significant additions to core typically require. Core committers, including John Blackbourn from Human Made, objected on those grounds. Mullenweg had previously indicated he opposed forcing Akismet into the Connectors screen. After reviewing the thread, he reversed that position entirely. When someone noted his earlier stance, his response was direct: “I did say that, and have changed my mind and we’re doing this.”
The result is that Akismet, an Automattic product, will ship on the WordPress 7.0 Connectors screen on May 20, following a process that multiple core committers flagged as bypassing standard governance.
Separately, Mullenweg described Five for the Future contribution tracking data as “worse than useless” and called for a broader rethink of how corporate contributions factor into WordPress development.
Developer Josh Collinsworth published a widely circulated post titled “If WordPress is to survive, Matt Mullenweg must be removed,” which reflects how seriously parts of the community read the incident.
The governance structure underneath all of this is the BDFL model, where Mullenweg holds effective authority over both the WordPress Foundation and Automattic simultaneously. That model functions quietly during stable periods. Under pressure, and weeks before a major release, it produces a situation where the person most publicly critical of the project is also the person with unilateral authority to override its maintainers.
For businesses and hosting providers built on WordPress, the software ships May 20 regardless. The questions this incident raises are about process, not code, and those tend to outlast any individual release cycle.
