This story has been up to date all through with extra particulars because the story has developed. We’ll proceed to take action because the case and dispute are ongoing.
The world of WordPress, one of the vital well-liked applied sciences for creating and internet hosting web sites, goes by way of a really heated controversy. The core concern is the struggle between WordPress founder and Automattic CEO Matt Mullenweg and WP Engine, which hosts web sites constructed on WordPress.
WordPress know-how is open supply and free, and it powers an enormous chunk of the web — round 40% of internet sites. Web sites can host their very own WordPress occasion or use an answer supplier like Automattic or WP Engine for a plug-and-play answer.
In mid-September, Mullenweg wrote a weblog put up calling WP Engine a “cancer to WordPress.” He criticized the host for disabling the power for customers to see and observe the revision historical past for each put up. Mullenweg believes this function is on the “core of the user promise of protecting your data” and mentioned that WP Engine turns it off by default to economize.
He additionally known as out WP Engine investor Silver Lake and mentioned they don’t contribute sufficiently to the open supply undertaking and that WP Engine’s use of the “WP” model has confused prospects into believing it’s a part of WordPress.
The authorized battle
In reply, WP Engine despatched a cease-and-desist letter to Mullenweg and Automattic to withdraw their feedback. It additionally mentioned that its use of the WordPress trademark was lined beneath truthful use.
The corporate claimed that Mullenweg had mentioned he would take a “scorched earth nuclear approach” towards WP Engine except it agreed to pay “a significant percentage of its revenues for a license to the WordPress trademark.”
In response, Automattic despatched its personal cease-and-desist letter to WP Engine, saying that they’d breached WordPress and WooCommerce trademark utilization guidelines.
The WordPress Basis additionally modified its Trademark Coverage web page and known as out WP Engine, alleging the internet hosting service has confused customers.
“The abbreviation ‘WP’ is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is ‘WordPress Engine’ and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress,” the up to date web page reads.
WP Engine ban, and trademark battle
Mullenweg then banned WP Engine from accessing the assets of WordPress.org. Whereas parts like plug-ins and themes are beneath open supply license, suppliers like WP Engine need to run a service to fetch them, which isn’t lined beneath the open supply license.
This broke plenty of web sites and prevented them from updating plug-ins and themes. It additionally left a few of them open to safety assaults. The group was not happy with this strategy of leaving small web sites helpless.
In response to the incident, WP Engine mentioned in a put up that Mullenweg had misused his management of WordPress to intervene with WP Engine prospects’ entry to WordPress.org.
“Matt Mullenweg’s unprecedented and unwarranted action interferes with the normal operation of the entire WordPress ecosystem, impacting not just WP Engine and our customers, but all WordPress plugin developers and open source users who depend on WP Engine tools like ACF,” WP Engine mentioned.
On September 27, WordPress.org lifted the ban quickly, permitting WP Engine to entry assets till October 1.
Mullenweg wrote a weblog put up clarifying that the struggle is barely towards WP Engine over logos. He mentioned Automattic has been attempting to dealer a trademark licensing deal for a very long time, however WP Engine’s solely response has been to “string us along.”
On September 30, a day earlier than the WordPress.org deadline for the ban on WP Engine, the internet hosting firm up to date its website’s footer to make clear it’s not immediately affiliated with the WordPress Basis or owns the WordPress commerce.
“WP Engine is a proud member and supporter of the community of WordPress® users. The WordPress® trademark is the intellectual property of the WordPress Foundation, and the Woo® and WooCommerce® trademarks are the intellectual property of WooCommerce, Inc. Uses of the WordPress®, Woo®, and WooCommerce® names in this website are for identification purposes only and do not imply an endorsement by WordPress Foundation or WooCommerce, Inc. WP Engine is not endorsed or owned by, or affiliated with, the WordPress Foundation or WooCommerce, Inc,” the up to date description on the location learn.
The corporate additionally modified its plan names from “Essential WordPress,” “Core WordPress,” and “Enterprise WordPress” to “Essential,” “Core,” and “Enterprise.”
WP Engine mentioned in a press release that it modified these phrases to moot Automattic’s claims.
“We, like the rest of the WordPress community, use the WordPress mark to describe our business. Automattic’s suggestion that WPE needs a license to do that is simply wrong, and reflects a misunderstanding of trademark law. To moot its claimed concerns, we have eliminated the few examples Automattic gave in its September 23rd letter to us,” an organization spokesperson informed TechCrunch.
On October 1, the corporate posted on X that it has efficiently deployed its personal answer for updating plug-ins and themes.
The WordPress group and different initiatives really feel this might additionally occur to them and need clarification from Automattic, which has an unique license to the WordPress trademark. The group can be asking about clear steering round how they will and may’t use “WordPress.”
The WordPress Basis, which owns the trademark, has additionally filed to trademark “Managed WordPress” and “Hosted WordPress.” Builders and suppliers are fearful that if these logos are granted, they could possibly be used towards them.
Open-source content material administration system Ghost’s founder John O’Nolan additionally weighed in on the difficulty and criticized management of WordPress being with one individual.
“The web needs more independent organizations, and it needs more diversity. 40% of the web and 80% of the CMS market should not be controlled by any one individual,” he mentioned in an X put up.
On October 9, net app growth framework Ruby on rails creator David Heinemeier Hansson opined that Automattic is violating principals of open supply software program by asking WP Engine to pay 8% of its revenues.
“Automattic is completely out of line, and the potential damage to the open source world extends far beyond the WordPress. Don’t let the drama or its characters distract you from that threat,” he mentioned in a weblog put up.
On the identical day, Mullenweg added a brand new checkbox to WordPress.org contributor login, asking individuals to confirm that they don’t seem to be related to WP Engine in any manner. This transfer was criticized by the contributor group. Some contributors mentioned that they have been banned from the group Slack for opposing the transfer.
In response, WP Engine mentioned that its prospects, companies, customers, and the group as a complete will not be the corporate’s associates.
WP Engine lawsuit and Automattic exodus
On October 3, WP Engine sued Automattic and Mullenweg over abuse of energy in a courtroom in California. The internet hosting firm additionally alleged that Automattic and Mullenweg didn’t preserve their guarantees to run WordPress open-source initiatives with none constraints and giving builders the liberty to construct, run, modify and redistribute the software program.
“Matt Mullenweg’s conduct over the last ten days has exposed significant conflicts of interest and governance issues that, if left unchecked, threaten to destroy that trust. WP Engine has no choice but to pursue these claims to protect its people, agency partners, customers, and the broader WordPress community,” the corporate mentioned in a press release to TechCrunch.
The lawsuit additionally notes alleged texts from Mullenweg about probably hiring WP Engine CEO Heather Brunner. In a touch upon Hacker Information, Mullenweg mentioned that Brunner wished to be an government director of WordPress.org.
In response, Automattic known as this case meritless.
“I stayed up last night reading WP Engine’s Complaint, trying to find any merit anywhere to it. The whole thing is meritless, and we look forward to the federal court’s consideration of their lawsuit,” the corporate’s authorized consultant, Neal Katyal, mentioned in a weblog put up.
On the identical day, 159 Automattic workers who didn’t agree with Mullenweg’s route of the corporate and WordPress general took a severance bundle and left the corporate. Virtually 80% of people that left labored in Automattic’s Ecosystem / WordPress division.
On October 8, WordPress mentioned that Mary Hubbard, who was TikTok US’s head of governance and expertise, might be beginning as government director. This put up was beforehand held by Josepha Haden Chomphosy, who was one of many 159 individuals leaving Automattic. A day previous to this, one of many engineers from WP Engine introduced that he was becoming a member of Automattic.
You’ll be able to contact this reporter at im@ivanmehta.com or on Sign: @ivan.42
