Whose WordPress is it anyway? – Jason Tucker and Sé Reed

Keep this handy—bookmark it for later!

On June 14, 2024, Jason Tucker and Sé Reed talk about who “owns” the WordPress open-source project and who controls it. They point out the conflict between open-source ideals and real centralized control. The episode ends with a call for more transparency and accountability in the WordPress community, especially about project leadership.

Here are the main points from this video, made with Harpa AI:

  • 00:01:15 🎤 Se Reed shares her experience troubleshooting issues with the Astra theme while assisting a friend, highlighting frustrations with hybrid themes.
  • 00:06:47 🛠️ The hosts discuss the complexity of WordPress themes, emphasizing how theme choices can lead to being locked into specific options and settings.
  • 00:07:16 ❓ Se Reed questions who truly “owns” WordPress, noting a discrepancy between user needs and decision-making influences within the community.
  • 00:08:22 📊 Discussion reveals that Matt Mullenweg plays a pivotal role in controlling the WordPress ecosystem, affecting many users and developers.
  • 00:10:00 🏢 Five main entities—WordPress Community Services, WordPress Foundation, Automattic, Audrey Capital, and Matt Mullenweg—are identified as key players in WordPress governance.
  • 00:12:41 🏰 Matt Mullenweg owns the WordPress.org domain, giving him significant control over the project’s direction and decisions.
  • 00:19:16 ⚖️ The hosts discuss the implications of Mullenweg’s control, suggesting it creates instability for businesses relying on WordPress.
  • 00:21:35 📉 The disbanding of the WordPress marketing team is linked to conflicts over SEO practices and Mullenweg’s control over project direction.
  • 00:25:07 ⚖️ Volunteer contributors for WordPress.org also serve the marketing interests of WordPress.com, leading to a conflict of interest.
  • 00:26:52 🤔 Contributors feel divided between WordPress.org and WordPress.com teams, questioning the unity of their efforts.
  • 00:29:32 🚫 Attempts to implement gamification features for contributor engagement were rejected by higher-ups, indicating a lack of support for innovation.
  • 00:32:07 🔒 The founding principles of WordPress as open-source software are under threat due to centralized control by key individuals, notably Matt Mullenweg.
  • 00:37:11 🏛️ The separation between WordPress.com and WordPress.org has become increasingly blurred, raising concerns about conflicts of interest.
  • 00:42:32 📉 The marketing team’s efforts have diminished, leading to a narrower focus for WordPress.org and less community involvement.
  • 00:46:15 ⚠️ An independent investigation confirmed bullying and harassment by Matt Mullenweg, with no public apology offered to the complainant.
  • 00:49:44 📝 A warning was retroactively issued to the complainant for behavior linked to a previous incident, raising concerns about potential community bans.
  • 00:50:53 ⚖️ Se Reed expresses the need to protect individuals causing harm while balancing personal involvement in the community.
  • 00:52:29 🌍 The WordPress Community Collective launched a new program to incentivize DEIB advocacy within the WordPress community.
  • 00:53:59 🎤 Reed emphasizes the importance of public advocacy for DEIB initiatives to raise awareness in the WordPress community.
  • 00:55:33 🔍 Discussion around Matt Mullenweg’s control over WordPress and its implications on community governance.
  • 00:56:36 👥 Reed highlights that WordPress was meant to be a collective project, not controlled by a single individual.
  • 00:57:41 💼 Reed warns about the shift from volunteer contributors to paid positions under Matt’s influence in the WordPress ecosystem.
  • 00:58:14 🏛️ The need for the community to openly discuss leadership and accountability within WordPress is stressed.
  • 01:00:29 ✋ Reed calls for community members to stop ignoring the realities of WordPress’s leadership structure.
  • 01:01:44 🚫 Reed challenges the notion that Matt’s control is unchallengeable and urges accountability from the community.
Know someone who needs to see this? Share it now!

Leave the first comment

Explore More

  • WP Engine vs WordPress WordPress Drama

    Check out the timeline of tensions and controversies within the WordPress ecosystem, highlighting key events between Automattic and WP Engine. Discover how these conflicts have…
  • Affected Plugins From Wordpress Drama

    Check how the WordPress and WP Engine dispute affects the plugin ecosystem. Explore the list of themes and plugins that have been impacted by this…
  • Who Wants What With Wordpress Drama

    Let's find out who owns what in this WP Drama. Here’s a breakdown of the key stakeholders and their ownership in the ongoing WP Drama…
  • Who Got What From Wordpress Drama

    So, what’s the outcome of this ongoing conflict? The situation remains unresolved, but it appears that no party involved is reaping the benefits of this…
  • Who Said What in WordPress Drama Image

    This article looks at what important people and groups are saying about the WordPress drama, providing insight into the different opinions that have come up…