The WordPress vs. WP Engine drama, explained
The world of WordPress, one of the most popular technologies for creating and hosting websites, is going through a very heated controversy.
The world of WordPress, one of the most popular technologies for creating and hosting websites, is going through a very heated controversy. The core issue is the fight between WordPress founder and Automattic CEO Matt Mullenweg and WP Engine, which hosts websites built on WordPress.
The ongoing legal battle between Automattic, the company behind WordPress.com, and WP Engine, a hosting service that utilizes the WordPress brand, has sparked a heated debate within the open-source community. T
The dispute began when Automattic's CEO, Matt Mullenweg, published a blog post criticizing WP Engine for disabling the revision history feature for its users, which Mullenweg believes is essential for data protection. He also accused WP Engine of not contributing sufficiently to the open-source WordPress project and of confusing customers into believing it is part of WordPress.
In response, WP Engine sent a cease-and-desist letter to Mullenweg and Automattic, claiming that their use of the WordPress trademark was covered under fair use. Automattic then sent its own cease-and-desist letter to WP Engine, alleging that it had breached WordPress and WooCommerce trademark usage rules. The WordPress Foundation, which owns the trademark, subsequently updated its Trademark policy page to call out WP Engine for confusing users.
The dispute escalated when the WordPress Foundation banned WP Engine from accessing the resources of WordPress.org, which resulted in many websites being broken and left vulnerable to security attacks. The community was not pleased with this approach, and WP Engine accused Mullenweg of misusing his control of WordPress to interfere with its customers' access to WordPress.org.
The ban was temporarily lifted, but the dispute continues. Mullenweg has clarified that the fight is only against WP Engine over trademarks, and Automattic has been trying to broker a trademark licensing deal for a long time. The WordPress community is concerned about the potential for similar disputes with other projects and is asking for clear guidance on how they can and can't use the "WordPress" brand.
Developers are also worried about relying on commercial open-source products related to WordPress, especially when their access can be revoked quickly. Ghost's founder, John O'Nolan, has criticized the control WordPress has with one person, saying that the web needs more independent organizations and diversity.
In response to the controversy, WP Engine updated its site's footer to clarify that it is not directly affiliated with the WordPress Foundation or owns the WordPress trademark. The company also changed its plan names to remove references to "WordPress." The dispute highlights the complexities of trademark law and the importance of clear guidelines for using open-source brands. It also raises questions about the control and ownership of open-source projects and the potential for similar disputes in the future.
The controversy has sparked a wider discussion about the role of open-source projects and the need for clear guidelines on trademark usage. It has also raised concerns about the potential for similar disputes in the future, particularly in the context of commercial open-source products. As the debate continues, the WordPress community is left wondering what the future holds for the open-source project and how it will navigate the complexities of trademark law.
I better stay out of this one.