Mullenweg says WordPress.org “belongs to me personally”, as his WP Engine feud blurs the lines between WordPress.org, the WordPress Foundation, and Automattic
Matt Mullenweg: ‘WordPress.org just belongs to me’ — https://www.theverge.com/... #WordPress #opensource #Automattic @Khrys@mamot.fr : Matt Mullenweg: ‘WordPress.org just belongs to me’ — https://www.theverge.com/... The lines between the WordPress open-source project, the nonprofit backing it, and the commercial arm owned by Automattic are blurring. Rob Zazueta / @robz@toot.robzazueta.com : “'WordPress.org just belongs to me personally,' Mullenweg said during an interview with The Verge.” — https://www.theverge.com/... Listen to him: — It doesn't belong to the community of contributors. — It doesn't belong to the community of committed users - many of whom modify the code in some way to fit their needs, even if it's just a template. … Jason Lefkowitz / @jalefkowit@vmst.io : MATT — I AM BEGGING YOU — STOP TALKING — https://www.theverge.com/... [image] X: Heather Bragg / @heatherbragg : Considering @wordpress powers 40% of the Internet, this comment is concerning. Eva de Valk / @evadevalk : What a mess https://www.theverge.com/... Matt Beck / @mattbeck : One takeaway I have in all of this WordPress drama is that it's amazing it hasn't blown up in Matt's face this way until now. https://www.theverge.com/... @alchemyunited : Well, that's one way to silence any dissenting plugin and theme owners on .org. Why wasn't this “business structure” made more transparent sooner? “ https://wordpress.org/ just belongs to me personally,” Mullenweg said during an interview with The Verge. https://www.theverge.com/... [image] See also Mediagazer
Context & Ripple Effects
The dispute had already moved from commercial negotiations to platform access: Automattic said it had sought a licensing agreement with WP Engine, then ended WP Engine's free access to WordPress.org. Mullenweg's ownership claim makes the governance question explicit because WordPress.org, the WordPress Foundation and Automattic occupy distinct stated roles in the project ecosystem.
The immediate issue is not simply a disagreement between vendors. Reporting describes a growing overlap between the open-source project's public infrastructure, its nonprofit backer and Automattic's commercial interests; later coverage characterized the conflict as raising conflict-of-interest and legal concerns.
First-order effects
- WordPress contributors, users and commercial participants now have a clearer reason to question which entity controls WordPress.org decisions and on what basis.
- WP Engine faces a dispute in which access to project infrastructure has already become a point of leverage, while Automattic and Mullenweg face intensified scrutiny over their separation from project governance.
Second-order effects
- Hosting and plugin businesses that depend on WordPress.org may reassess the operational risk of relying on infrastructure controlled outside the Foundation's stated nonprofit role.
- The public disagreement over licensing and access can make commercial partners seek clearer terms for trademarks, services and project resources before committing further.
Third-order effects
- If control of widely used open-source infrastructure remains closely tied to a commercial participant or an individual, governance clarity becomes a competitive and trust differentiator for open-source ecosystems.
- The episode could accelerate pressure for more explicit separation between nonprofit stewardship, project infrastructure and commercial enforcement, though the corpus does not establish that any governance change is underway.
The trend: This is one data point in the broader push to test whether open-source projects can preserve community legitimacy when their infrastructure and commercial interests are closely intertwined.