WordPress vs. WP Engine drama, explained

Overview of WordPress and its importance:

WordPress powers 40% of websites and is open-source. Users can self-host or use providers like Automattic or WP Engine for managed hosting solutions.

The current controversy:

A conflict between Matt Mullenweg, founder of WordPress and CEO of Automattic, and WP Engine, a WordPress hosting provider, has erupted over trademark usage, service policies, and open-source principles.

Background

• WordPress’s open-source nature:
  • A key feature is its open-source software and a wide ecosystem of themes and plugins. Automattic and WP Engine are major players in offering managed hosting solutions.

Conflict Unfolds

1. Mullenweg’s Criticism of WP Engine

• In mid-September, Mullenweg labeled WP Engine a “cancer to WordPress” in a blog post. He criticized WP Engine for:
  • Disabling post revision history, which he called a violation of user data protection.
  • Using the “WP” brand, confusing customers into believing WP Engine is affiliated with WordPress.

2. WP Engine’s Response

• Legal actions: WP Engine issued a cease-and-desist letter to Mullenweg, accusing him of trying to enforce trademark usage unfairly and claiming Mullenweg demanded payment for a license to use the WordPress name.
• WP Engine’s defense: Claimed its use of the “WP” brand falls under fair use and clarified it was not officially part of WordPress.

Escalation

3. WordPress.org Ban on WP Engine

• In response to the trademark dispute, Mullenweg banned WP Engine from accessing WordPress.org resources.
• Impact on websites: This broke many WP Engine-hosted websites, preventing updates to plugins and themes, leading to potential security vulnerabilities.

4. Temporary Resolution

• Temporary lift: On September 27, the ban was lifted temporarily until October 1. WP Engine made changes to its branding to avoid trademark violations, updating its website and product names.

Ongoing Legal Battle

• WP Engine’s lawsuit: Filed against Automattic and Mullenweg in October, claiming abuse of power and betrayal of WordPress’s open-source principles.
• Automattic’s defense: They maintain that WordPress.org is not controlled by Automattic or the WordPress Foundation, but is run by Mullenweg for the benefit of the community.

Community Reactions

• Community concerns: The WordPress community is divided, with developers worried about Automattic’s control over WordPress and the implications for other service providers.
• Criticism from notable figures: Leaders like Ghost founder John O’Nolan and Ruby on Rails creator David Heinemeier Hansson condemned the actions as threats to open-source integrity.

Impact on Automattic

• Internal strife: Over 150 employees left Automattic following Mullenweg’s decisions.
• Leadership changes: Mary Hubbard was appointed as executive director of WordPress, following the departure of key figures like Josepha Haden Chomphosy.

Conclusion

• Future of WordPress: The controversy has far-reaching implications for WordPress’s open-source nature, trademark rules, and community governance, with the legal battle and community discontent far from resolved. The first hearing on the injunction is set for November 26.