When Leadership Overrides Community: What WordPress 7.0's Governance Crisis Means for Open Source

Open source projects thrive on transparency, consensus, and community trust. So when the founder of the world's most popular CMS publicly calls the project "mediocre crap" and reverses decisions made by core committers, it's worth paying attention—not to gossip, but to understand what it signals about sustainability and governance in large open-source ecosystems.

The Akismet Incident: More Than Just a Plugin Dispute

In April 2026, Matt Mullenweg returned to catch up on development discussions and encountered a lingering disagreement about WordPress 7.0's new "Connectors" screen—specifically whether Akismet should appear as a default option.

On the surface, this seems minor. Under the hood, it's a textbook example of governance breakdown.

Here's what happened:

• An Automattic-sponsored contributor added Akismet to the Connectors screen during the release candidate phase
• Core committers from other organizations (like Human Made's John Blackbourn) flagged the decision as bypassing standard review processes
• The addition happened with limited public discussion—unusual for significant product decisions
• Mullenweg initially opposed forcing Akismet into core
• After reading the Slack discussion, Mullenweg reversed his position and directed that Akismet proceed anyway
• When reminded of his earlier stance, his response was direct: "I did say that, and have changed my mind and we're doing this"

The problem? This wasn't a technical debate that Mullenweg won on merit. It was a decision made despite the process that WordPress's own governance model is supposed to protect.

Why Process Matters (Even When You're Right)

You don't need to care about WordPress politics to understand why this matters. The issue isn't whether Akismet should be included—it's how that decision got made.

Open-source projects depend on trust. Contributors volunteer time because they believe their voice matters and that decisions follow consistent principles. When a founder overrides that process—even with good intentions—it sends a signal:

Your input only counts if leadership agrees with you.

This creates a subtle but significant problem: it incentivizes contributors to build political capital rather than technical consensus. It makes decisions feel arbitrary, even when they're not. And it breeds resentment among the people doing the unglamorous work of maintaining the codebase.

For WordPress specifically, this is complicated by the fact that Automattic (Mullenweg's company) both sponsors development and ships commercial products that integrate with WordPress. When core decisions favor Automattic products, it blurs the line between open-source governance and corporate interest.

The Bigger Picture: Is WordPress Losing Direction?

Mullenweg's critique extended beyond Akismet. He argued that WordPress has drifted from the principles that made it successful:

• The project has grown bloated with "mediocre" features rather than focused on excellence
• The governance model isn't delivering quality contributions
• Companies pledging support through Five for the Future aren't contributing meaningfully

These are fair critiques in isolation. Many long-time WordPress developers share concerns about feature bloat and quality. But they also reveal something uncomfortable: the founder of a 20-year-old project feels the need to publicly criticize what his own model has produced.

That's not a sign of healthy community dynamics.

What This Means for Developers

If you're building on WordPress, this matters in practical ways:

Dependency risk: When governance becomes personality-driven rather than process-driven, the platform becomes less predictable. Future decisions might favor different priorities without clear justification.

Community fragmentation: Watch for key contributors leaving to work on WordPress forks or alternative platforms. High-profile governance conflicts often precede talent exodus.

Feature bloat: If pressure to add features to core increases (which the Akismet decision suggests), expect more complexity and potential security surface area.

Long-term viability: Open-source projects survive founder departures and leadership changes when governance is strong. WordPress's model—where one person can override committers—is fragile by comparison.

Lessons for Any Open-Source Project

This moment is instructive for anyone building or maintaining open-source software:

1. Document your governance model and stick to it. If core committers are supposed to have decision-making power, they need to have actual power, or the system becomes theatrical.

2. Separate leadership from dictatorship. Founders should have influence, but not override mechanisms that exist specifically to prevent single points of failure.

3. Make company incentives visible. When Automattic products are integrated into core, acknowledge the conflict explicitly. Let the community debate it openly rather than discovering it through Slack messages.

4. Trust your committers, or replace them. If Mullenweg didn't trust the core committers' judgment, the answer is restructuring that team—not ignoring their input on major decisions.

The WordPress Community's Next Chapter

WordPress powers 43% of all websites. It's an incredible achievement. But that scale also means governance matters more, not less.

The project faces a choice: recommit to the process that allowed distributed decision-making and community ownership, or acknowledge that it's now a Mullenweg-guided project with committers in advisory roles.

Pretending it's the former while operating as the latter creates the worst outcome: contributors feel powerless, and users can't predict which direction the project will go.

For developers evaluating platforms, this is a reminder to look beyond features. Ask about governance. Ask how decisions get made. Ask whether a single person can override committers. Because the best technology stack in the world can become a liability if you can't trust that it will evolve predictably.

What's Your Experience?

Have you worked on WordPress core? Run into friction with the project's governance? Or are you rethinking your platform choice based on governance models?

At NameOcean, we believe transparent infrastructure—from domain management to DNS configuration to hosting architecture—should extend to the software you build with. Whether you're running WordPress or exploring alternatives, we're here to support whatever stack works best for your team.

Share your thoughts in the comments. And if you're building on alternative platforms or thinking about your own open-source governance model, we'd love to hear what matters most to you.