{"id":5350,"date":"2024-10-09T14:00:38","date_gmt":"2024-10-09T12:00:38","guid":{"rendered":"https:\/\/www.lrob.fr\/?p=5350"},"modified":"2024-10-09T14:02:56","modified_gmt":"2024-10-09T12:02:56","slug":"wordpress-vs-wp-engine-conflict-drama-analysis","status":"publish","type":"post","link":"https:\/\/www.lrob.fr\/en\/blog\/internet\/wordpress\/conflit-wordpress-vs-wp-engine-analyse-drama\/","title":{"rendered":"WordPress vs WP Engine conflict: analysis of the drama"},"content":{"rendered":"<p>The world of <strong>WordPress<\/strong>which powers more than 40 % of the world's websites, is in turmoil. At the center of the conflict are two major players in the ecosystem: <strong>Matt Mullenweg<\/strong>founder of WordPress and CEO of Automattic, and <strong>WP Engine<\/strong>one of the leading hosting companies for WordPress.<\/p>\n\n\n\n<p>This confrontation, which has taken on legal proportions, raises crucial questions about control of the WordPress brand, open source, and the governance of one of the web's most influential projects. Here's a detailed analysis of the case and what's at stake.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Background: WordPress and WP Engine<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">WordPress and Automattic: a complex relationship<\/h3>\n\n\n\n<p><strong>WordPress<\/strong>launched in 2003 by Matt Mullenweg and Mike Little, is open source software for creating and managing websites. It's free to use, and enjoys the support of a large community of developers who contribute to its continuous improvement. However, the project's governance relies heavily on <strong>Automattic<\/strong>the company founded by Mullenweg. Automattic manages <strong>WordPress.com<\/strong> and other popular products such as <strong>WooCommerce<\/strong> and <strong>Jetpack<\/strong>.<\/p>\n\n\n\n<p>Although WordPress is open source, Automattic owns a <strong>exclusive license<\/strong> for the use of the <strong>WordPress<\/strong>This gives the company a central role in the ecosystem. This includes protecting the brand against perceived misuse or deception.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WP Engine: a major player in WordPress hosting<\/h3>\n\n\n\n<p>On his side, <strong>WP Engine<\/strong> is one of the largest hosting services specializing in WordPress. The company offers hosting solutions optimized for WordPress, making it easy for millions of users to manage their websites. It has experienced rapid growth, attracting leading investors such as <strong>Silver Lake<\/strong>.<\/p>\n\n\n\n<p>However, WP Engine is not directly affiliated with <strong>Automattic<\/strong> nor to the <strong>WordPress Foundation<\/strong>even though its name and business model are closely linked to WordPress.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Beginning of the Conflict: Mullenweg vs WP Engine<\/h2>\n\n\n\n<p>In September 2024, Matt Mullenweg published a blog post in which he openly criticized WP Engine, calling the company a <strong>\"cancer for WordPress<\/strong>. It criticized WP Engine for disabling the article revision history feature by default, a practice which, in its view, compromised the <strong>user data protection<\/strong>.<\/p>\n\n\n\n<p>Mullenweg also denounced WP Engine's use of the \"<strong>WP<\/strong>\"We felt that this was confusing users, leading them to believe that WP Engine was part of WordPress or had an official link with the WordPress Foundation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WP Engine's reaction<\/h3>\n\n\n\n<p>In response to these accusations, WP Engine sent out a <strong>cease and desist letter<\/strong> to Mullenweg and Automattic, demanding that they withdraw their statements. WP Engine defended its use of the \"WP\" trademark, claiming that it was a matter of <strong>fair use<\/strong> of the name, in accordance with trademark law. The company also accused Mullenweg of threatening to adopt a <strong>\"nuclear approach<\/strong> against WP Engine unless it agrees to pay a substantial royalty for the use of the WordPress trademark.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Legal escalation: cease-fires and counter-attacks<\/h2>\n\n\n\n<p>In response to WP Engine's letter, Automattic issued its own cease and desist letter, claiming that WP Engine violated the rules for use of the WordPress and WooCommerce trademarks.<\/p>\n\n\n\n<p>The conflict reached a new climax when <strong>Mullenweg has taken the radical decision to ban WP Engine from WordPress.org resources<\/strong>. This ban blocked WP Engine-hosted sites from accessing plugin and theme updates, exposing many sites to security risks. This measure has been widely criticized within the WordPress community, as it has left small businesses and independent sites without a viable solution.<\/p>\n\n\n\n<p>WP Engine denounced this decision, accusing Mullenweg of<strong>abuse of power<\/strong> and endanger the entire WordPress ecosystem.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\"><p lang=\"en\" dir=\"ltr\">Matt Mullenweg, CEO of Automattic, has misused his control of WordPress to interfere with WP Engine customers' access to\u00a0<a href=\"https:\/\/t.co\/ZpKb9q4jPh\">https:\/\/t.co\/ZpKb9q4jPh<\/a>asserting that he did so because WP Engine filed litigation against <a href=\"https:\/\/t.co\/erlNmkIol2\">https:\/\/t.co\/erlNmkIol2<\/a>. This simply is not true. Our Cease &amp;...<\/p>- WP Engine (@wpengine) <a href=\"https:\/\/twitter.com\/wpengine\/status\/1839246341660119287?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener\">September 26, 2024<\/a><\/blockquote><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Repercussions for the WordPress community<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Users taken hostage<\/h3>\n\n\n\n<p>The interruption of WP Engine services has had a major impact on many users. Although WordPress plugins and themes are licensed open source, hosting providers like WP Engine have to manage infrastructures so that their customers can use them. The temporary ban revealed the fragility of certain technical dependencies and highlighted the importance of a <strong>balanced management of open source resources<\/strong>.<\/p>\n\n\n\n<p>However, Mullenweg asserted that <strong>conflict was strictly linked to trademark issues<\/strong> and not to the overall management of WordPress. The ban was temporarily lifted at the end of September, but the incident sowed doubts in the community.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Automattic too dominant?<\/h3>\n\n\n\n<p>More and more voices are being raised to question Automattic's dominant position in WordPress management. <strong>John O'Nolan<\/strong>founder of the open source CMS <strong>Ghost<\/strong>criticized the <strong>excessive centralization<\/strong> around Matt Mullenweg, asserting that \"40 % of the web should not be controlled by one person\".<\/p>\n\n\n\n<p>On his side, <strong>David Heinemeier Hansson<\/strong>creator of <strong>Ruby on Rails<\/strong>has accused Automattic of betraying the principles of open source by requiring WP Engine to return 8 % of its revenues. For him, this practice could have repercussions far beyond WordPress, threatening the entire open source community.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Legal and commercial implications<\/h2>\n\n\n\n<p>On October 3, 2024, WP Engine decided to go on the offensive by <strong>filing a complaint against Automattic and Mullenweg<\/strong> for abuse of power and anti-competitive practices. WP Engine accuses Automattic of failing to respect its commitments to open source and of harming the interests of developers and users.<\/p>\n\n\n\n<p>This case is still ongoing, but it could have far-reaching <strong>far-reaching consequences<\/strong> on how open source brands and projects like WordPress will be managed in the future.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A special message when you log on to WordPress.org<\/h2>\n\n\n\n<p>When logging in to the WordPress.org forums, a new checkbox appears:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"has-medium-font-size\">\u2705 I am not affiliated with WP Engine in any way, financially or otherwise.<\/p>\n<\/blockquote>\n\n\n\n<p>Unusual message that prompted me to look this up and discover this case.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Questions raised for WordPress<\/h2>\n\n\n\n<p>This mainly affects two large American companies that are exploiting WordPress commercially (in models that are, in my opinion, too modified from the original version of WordPress). The original version of WP is truly free, and you can host it wherever you like (and hopefully, you'll choose a host that's as free as possible). <a href=\"\/en\/web-hosting\/\">LRob hosting<\/a>).<\/p>\n\n\n\n<p>For the time being, independent web hosts such as LRob are totally unaffected by this conflict. There are no alarm bells ringing for us, even if we remain vigilant.<\/p>\n\n\n\n<p>In any case, this conflict underlines <strong>tensions <\/strong>possible when managing a large-scale open source project. While WordPress remains an essential technology for millions of sites, the debate surrounding the <strong>brand ownership<\/strong>the <strong>governance<\/strong> and the<strong>open source ethics<\/strong>raises a number of questions.<\/p>\n\n\n\n<p>In particular: how far can open source remain free when it is closely linked to massive commercial interests?<\/p>\n\n\n\n<p><em>Source: <a href=\"https:\/\/techcrunch.com\/2024\/10\/08\/wordpress-vs-wp-engine-drama-explained\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">techcrunch.com<\/a><\/em><\/p>","protected":false},"excerpt":{"rendered":"<p>Le monde de WordPress, qui alimente plus de 40 % des sites web dans le monde, est en pleine \u00e9bullition. Au centre du conflit se trouvent deux acteurs majeurs de l&rsquo;\u00e9cosyst\u00e8me : Matt Mullenweg, fondateur de WordPress et CEO d\u2019Automattic, et WP Engine, une des principales entreprises d\u2019h\u00e9bergement pour WordPress. Cet affrontement, qui a pris [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3207,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,5,22,4],"tags":[],"class_list":["post-5350","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","category-blog","category-internet","category-news"],"_links":{"self":[{"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/posts\/5350","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/comments?post=5350"}],"version-history":[{"count":3,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/posts\/5350\/revisions"}],"predecessor-version":[{"id":5361,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/posts\/5350\/revisions\/5361"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/media\/3207"}],"wp:attachment":[{"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/media?parent=5350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/categories?post=5350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lrob.fr\/en\/wp-json\/wp\/v2\/tags?post=5350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}