The WordPress community is currently embroiled in a heated controversy between the platform’s founder, Matt Mullenweg, and WP Engine, a popular hosting service for WordPress websites. The drama began when Mullenweg publicly criticized WP Engine for disabling the ability for users to see and track the revision history for every post. This feature, according to Mullenweg, is essential for protecting user data, and he accused WP Engine of turning it off to save money.
Mullenweg also took issue with WP Engine’s investor, Silver Lake, alleging that they do not contribute enough to the open source project. Additionally, he claimed that WP Engine’s use of the “WP” brand has confused customers into believing it is a part of WordPress. In response to Mullenweg’s criticisms, WP Engine sent a cease-and-desist letter demanding that he retract his statements. They argued that their use of the WordPress trademark was covered under fair use.
The legal battle escalated when Automattic, the company founded by Mullenweg, also sent a cease-and-desist letter to WP Engine, accusing them of breaching WordPress and WooCommerce trademark usage rules. The WordPress Foundation chimed in, updating its Trademark Policy page to address the confusion caused by WP Engine’s branding. They emphasized that while the abbreviation “WP” is not covered by the WordPress trademarks, it should not be used in a way that confuses users.
Following the back-and-forth of cease-and-desist letters, Mullenweg decided to ban WP Engine from accessing the resources of WordPress.org. This move had significant repercussions as it disrupted the normal operation of websites hosted by WP Engine, leaving them vulnerable to security attacks. The community was divided, with some supporting Mullenweg’s actions while others criticized him for leaving small websites helpless.
In response to the ban, WP Engine accused Mullenweg of misusing his control of WordPress to interfere with their customers’ access to WordPress.org. They argued that his actions were detrimental to the entire WordPress ecosystem, impacting not just WP Engine but also all WordPress plugin developers and open source users who rely on their tools.
Amidst the turmoil, Mullenweg clarified that the fight was solely over trademarks and that Automattic had been trying to negotiate a licensing deal with WP Engine to no avail. The WordPress community and other projects expressed concerns about the potential implications of this dispute, fearing that similar actions could be taken against them in the future. They called for clear guidance from Automattic regarding the use of the WordPress trademark.
As the debate continues, developers and providers are anxious about the potential trademarking of phrases like “Managed WordPress” and “Hosted WordPress” by the WordPress Foundation. They worry that these trademarks could be used against them in the future, raising questions about the stability of relying on commercial open source products related to WordPress.
In conclusion, the ongoing drama between WordPress and WP Engine underscores the complexities of navigating the open source landscape. As the community grapples with trademark disputes and legal battles, it is essential for all parties involved to prioritize transparency, communication, and collaboration to ensure the sustainability and growth of the WordPress platform.
