Mullenweg Shuts Down WordPress Sustainability Team, Igniting Backlash
WordPress co-founder Matt Mullenweg’s decision to shut down the project’s volunteer-run sustainability team — after previously championing it — has intensified concerns about his leadership style and the concentration of power around WordPress.org and Automattic. Commenters argue over whether the team’s work (such as event guidelines and a carbon-footprint plugin) justified its existence, but many see the abrupt, confrontational way it was disbanded as damaging to community trust and long-term ecosystem stability. Some agencies and developers are now openly weighing alternatives like Drupal, Wagtail, or Craft CMS, raising questions about WordPress’s future governance and resilience.
Perceived behavior of WordPress leadership
- Many see the shutdown of the sustainability team, the “drama” Reddit post, Slack taunts, and recent bans/deactivations as unprofessional, petty, and authoritarian.
- Some argue this is part of a broader pattern: aggressive responses to criticism, legal threats, alleged bullying at events, and ecosystem decisions made “in a fit of pique.”
- A minority think the outrage is overblown relative to the actual stakes and see the reaction as “manufactured drama.”
Sustainability team: role and shutdown
- The team appears to have focused on things like a Sustainable Events Handbook and a plugin to estimate site carbon footprint.
- Several commenters note the work was volunteer-based and cost the project “nothing,” so shutting it down is seen as symbolic and hostile.
- Others are skeptical of the value, seeing it as performative, niche, or ideologically driven; some would have cut it on principle.
- There is specific anger that leadership publicly claimed not to know the team existed despite evidence that it was created at leadership’s own request.
Governance, control & forks
- Commenters emphasize that effective control over the foundation, infrastructure, brand, and a dominant share of company stock is concentrated in one person.
- This centralization makes replacing leadership nearly impossible without a fork, which many see as risky due to trademarks, potential lawsuits, and personal retaliation.
- Ideas raised: a fork stewarded by a major nonprofit or large ecosystem player, but most consider this unlikely or difficult.
Impact on ecosystem & user sentiment
- Some agencies and long-time developers report reconsidering WordPress due to governance instability and unilateral moves (e.g., plugin repo actions).
- Alternatives discussed include Drupal, Wagtail, Craft CMS, and proprietary builders; migration costs for large deployments are acknowledged as very high.
- Others believe typical end users will barely notice, and the platform will remain commercially viable, at least short- to mid-term.
Debate over sustainability & priorities
- One camp views sustainability work as low-impact “greenwashing” or distraction; another argues efficiency at WordPress scale has real environmental and cost benefits.
- A recurring theme: frustration that time is spent on public fights instead of making the core editor and platform better and more efficient.