WordPress Co-Founder Matt Mullenweg Faces Backlash After Controversial WordCamp USA Keynote
WordPress co-founder Matt Mullenweg sparked controversy at WordCamp USA 2024 by criticizing WP Engine's contributions to the platform, leading to widespread backlash on social media. His comments ignited a debate on the role of companies in open source communities and the future of WordPress.
Matt Mullenweg, co-founder of WordPress.org and CEO of Automattic, found himself at the center of controversy following his closing keynote at the 2024 WordCamp USA. His sharp criticism of managed WordPress web host WP Engine sparked a wave of backlash, with many in the WordPress community reacting negatively both to his speech and a follow-up blog post. The fallout was so widespread that âWordPressâ became the number one trending topic on X (formerly Twitter).
What Happened: A Community-Centric Event Ends on a Sour Note
WordPress, which powers over 40% of the web, is built on the foundation of open source collaboration, creating a vast ecosystem of jobs, services, and markets worldwide. WordCamp, a volunteer-driven conference, is an embodiment of this community spirit, offering a space for WordPress users and developers to share ideas and innovations. Typically, WordCamp is an inspiring event, but the tone shifted dramatically during Mullenweg's keynote, which closed out the conference held from September 17th to 20th, 2024.
In his speech, Mullenweg praised the WordPress community for its contributions to the open source platform, particularly through initiatives like the "Five for the Future" program, where companies are encouraged to allocate 5% of their resources toward WordPress development. However, he then sharply criticized WP Engine, accusing the hosting company of not contributing enough to the WordPress core, despite benefiting from the ecosystem.
He likened companies that fail to give back to "extracting oil from the ground," accusing WP Engine of extracting value without adequately reinvesting in the platform. His comments particularly targeted Silver Lake, a private equity firm that controls WP Engine, saying the firm "doesnât care about open source ideals" and prioritizes profits over community contributions.
The Fallout: A Divided Response
Mullenwegâs remarks stunned the audience, with some attendees openly expressing discomfort. His suggestion that the WordPress community âvote with your walletâ and consider switching hosts stirred significant controversy. While he didnât directly call for a boycott, the implication was clear, and it did not sit well with many in attendance.
The reaction on social media was swift, with many expressing disappointment in Mullenweg's handling of the situation. For instance, Matt Cromwell, co-founder of GiveWP, tweeted that no one he spoke with at WordCamp agreed with Mullenwegâs take on WP Engineâs contributions, emphasizing that public criticism wasnât the right approach to encourage more involvement in the WordPress ecosystem.
Others in the WordPress community echoed this sentiment, feeling that Mullenwegâs attack on WP Engine did more harm than good, and potentially damaged the collaborative spirit that WordPress was built on.
Mullenweg Doubles Down
The controversy didnât end with the keynote. Mullenweg followed up with a blog post on the official WordPress.org website, further elaborating on his criticism of WP Engine and Silver Lake. In the post, he claimed that Silver Lake was eroding trust within the open source community by prioritizing profits over the well-being of WordPress.
This additional commentary fueled further backlash, with some users on X and Facebook even calling for Mullenweg to step down from his leadership role. WordPress agency owner Kevin Geary, among others, questioned whether public ridicule was a valid approach for addressing perceived issues within the community, particularly at an event designed to unite and inspire WordPress users.
WP Engine's Contributions and the Broader Debate
Many in the community felt that Mullenwegâs focus on WP Engineâs contribution to WordPress core development was unfair. WP Engine, which sponsors 40 hours per week for WordPress core work, also contributes to the ecosystem in other ways, including sponsoring WordCamp events and developing widely-used free plugins like Advanced Custom Fields, LocalWP, and WPGraphQL.
Critics of Mullenwegâs stance pointed out that contribution to open source projects can take many forms, and measuring it solely by hours committed to core development overlooks other significant contributions. Some argued that his remarks could discourage companies from participating in the ecosystem, fearing public shaming for not meeting arbitrary standards of involvement.
Community Backlash Continues
The backlash extended into private forums like the Dynamic WordPress Facebook group, where many members voiced their disapproval of Mullenwegâs keynote. Some attendees remarked on the shocked reactions at WordCamp, while others expressed concern that Mullenweg's leadership could threaten the future of WordPress. Many in the community have called for a more constructive and inclusive approach to fostering contributions rather than singling out companies in a public setting.
The controversy underscores a broader challenge facing open source communities: how-to balance the need for financial sustainability with the collaborative and community-driven ethos that powers projects like WordPress. Mullenwegâs criticism of WP Engine has reignited this debate, with many calling for a more nuanced discussion on how companies can contribute to open source projects in ways that align with their business goals while still supporting the broader ecosystem.
As the dust settles, it remains to be seen how Mullenweg and the WordPress community will move forward from this pivotal moment.