Backlash Against Matt Mullenweg Highlights Tensions in WordPress Community

The WordPress community has found itself at a crossroads following a controversial keynote speech by co-founder Matt Mullenweg at WordCamp USA.

Mullenweg openly criticised WP Engine, a prominent managed WordPress hosting company, for their perceived insufficient contributions to the open-source WordPress project.

His remarks, both during his closing address and in a subsequent blog post, have led to significant backlash, with many in the community expressing support for WP Engine and condemning Mullenweg’s public approach.

Emphasising Open Source Contributions

Mullenweg’s speech highlighted the importance of companies benefiting from WordPress to give back to its open-source development, particularly through the “Five for the Future” program, which encourages organizations to contribute 5% of their resources to the project.

He called out WP Engine for sponsoring a mere 40 hours per week towards improving the WordPress core, a figure he deemed insufficient given their scale and success.

Public Shaming vs. Private Dialogue

The crux of the controversy lies in Mullenweg’s choice to publicly shame WP Engine rather than opting for a private dialogue to address these concerns. This approach has sparked disapproval across the WordPress community. Kevin Geary, a WordPress agency owner, vocally questioned this strategy, asking, “The question now becomes, is public ridicule and shame a valid approach? And should this ridicule and shame get delivered in the closing talk at a WordCamp?”

Divergent Views on Contributions

While Mullenweg emphasized financial contributions and dedicated development hours, others argue that WP Engine’s support for WordCamps, provision of free plugins, and active community engagement also represent significant contributions.

This divergence of views underscores ongoing debates within the community regarding what forms of support and contribution are most valuable and necessary for WordPress’s growth.

Potential Impact on WordPress Ecosystem

Concerns have also been raised about the potential damage Mullenweg’s actions may inflict on the WordPress ecosystem. Some users worry that his public approach may foster division within the community and discourage potential contributors from getting involved.

“No one I spoke with at #wcus sympathized with @photomatt’s take on @wpengine’s contributions to WP,” shared Matt Cromwell, co-Founder of GiveWP.

A Call to Action

Mullenweg’s impassioned plea for the community to “vote with their wallets” by supporting companies that contribute more to WordPress has been met with mixed reactions. He urged attendees, saying, “So it’s at this point that I ask everyone in the WordPress community to go vote with your wallet.

Who are you giving your money to? Someone who is going to nourish the ecosystem or someone is going to frack every bit of value out of it until it withers?”

Conclusion

The fallout from Mullenweg’s criticism of WP Engine is a stark reminder of the tensions that can arise within open-source communities regarding contribution and stewardship. While his dedication to securing the project’s future is clear, the community’s overwhelmingly negative response suggests that his methods may need to be reconsidered.

As WordPress moves forward, the discussion about how best to support and sustain open-source development continues, with a need for both unity and constructive dialogue.

The recent events serve as a critical point of reflection for the WordPress community, highlighting the need for balance between advocating for greater contributions and maintaining respectful, private channels for resolving disputes.

Tags: Wordpress