Mullenweg threatens corporate takeover of WP Engine

Original Article ↗ Hacker News Discussion ↗

Nature of the Conflict

  • Many commenters argue the dispute is fundamentally about business models and perceived lack of upstream contribution, not about trademarks per se.
  • Several point out that GPLv2 allows commercial use that original authors might dislike; trying to control that after the fact is seen as contrary to open‑source norms.

Trademarks, Licensing, and Governance

  • Distinction is made between “WordPress” and “WP”: official policy long said “WP” was allowed, then was recently revised with more restrictive language, which some see as weaponized after the fact.
  • Debate over whether describing services as “WordPress hosting/plugins/themes” is nominative fair use or confusing endorsement.
  • Discussion highlights that the WordPress trademark is held by a foundation that granted Automattic an exclusive commercial license, raising concerns about conflicts of interest.
  • WordPress.org is said to be personally owned and controlled, blurring lines between project, foundation, and company.

Demands, Negotiations, and “Shakedown” Debate

  • A term sheet reportedly asked WP Engine for ~8% of gross revenue or equivalent staff time directed by WordPress.org, plus audit rights by a direct competitor.
  • Some see this as a reasonable attempt to secure ecosystem investment; others call it a shake‑down that would never be “enough” and note the timing appears sudden despite claims of long‑running “negotiations.”

Plugin Repository, Widgets, and Site Impact

  • WP Engine removed the wp‑admin news widget; Mullenweg framed this as “breaking thousands of sites.” Multiple commenters say only the widget was removed and nothing actually broke.
  • Cutting WP Engine off from the central plugin/update infrastructure is widely seen as a serious escalation that endangers security and livelihoods.
  • WP Engine is reportedly mirroring the repository and serving its own compatible API.

WooCommerce/Stripe and GPL Ethics

  • Allegation: WP Engine diverted “tens of millions” in affiliate revenue by substituting its own Stripe integration.
  • Counterpoints: either they forked code under GPL or built a separate payments plugin, both legally allowed. Some call it sketchy but not fraud; others say intent and user expectations still matter.

Forking, Alternatives, and Platform Risk

  • Several suggest WP Engine or others could fork WordPress or WooCommerce; most doubt they will invest enough engineering effort, and many think a fork would struggle without the WordPress brand.
  • Some users say this drama makes WordPress feel like an unstable platform and are considering migrations (e.g., to static site generators or other CMSs); others note WordPress’s market share remains huge.

Open Source Economics and Leadership

  • Broad agreement that big businesses built on open source “should give back,” but no consensus on what is owed or how to enforce it.
  • Many criticize current leadership behavior and public communication as damaging to community trust, while still acknowledging past stewardship and the structural funding problem for large GPL projects.