The latest on the WordPress fight over trademarks and open source

In late September, Automattic CEO and WordPress cofounder Matt Mullenweg started a public dispute with the hosting provider WP Engine, calling the company "a cancer to WordPress." He accused WP Engine of not contributing enough to the WordPress ecosystem and profiting off of trademark confusion. As a result, WP Engine was blocked from accessing WordPress.org's servers.

Automattic has since sent a cease and desist order to WP Engine to stop it from using its trademarks, while WP Engine has followed up with a lawsuit that accuses Automattic and Mullenweg of extortion.

The series of events set off a public battle that calls into question the boundaries between WordPress.com host Automattic, the WordPress open-source project, and the nonprofit that's behind it.

Here's all the latest news so far.

Over the past several weeks, WordPress cofounder Matt Mullenweg has made one thing exceedingly clear: he's in charge of WordPress' future.

Mullenweg heads up WordPress.com and its parent company, Automattic. He owns the WordPress.org project, and he even leads the nonprofit foundation that controls the WordPress trademark. To the outside observer, these might appear to be independent organizations, all separately designed around the WordPress open-source project. But as he wages a battle against WP Engine, a third-party WordPress hosting service, Mullenweg has muddied the boundaries between three essential entities that lead a sprawling ecosystem powering almost half of the web.

Automattic CEO Matt Mullenweg offered employees $30,000, or six months of salary (whichever is higher), to leave the company if they didn't agree with his battle against WP Engine. In an update on Thursday night, Mullenweg said 159 people, making up 8.4 percent of the company, took the offer.

Automattic, which is in charge of WordPress.com and its commercial services, has been involved in a public dispute with WP Engine after Mullenweg called the third-party hosting service a "cancer" to the WordPress community and banned it from accessing WordPress.org.

The WP Engine web hosting service is suing WordPress co-founder Matt Mullenweg and Automattic for alleged libel and attempted extortion, following a public spat over the WordPress trademark and open-source project. In the federal lawsuit filed on Wednesday, WP Engine accuses both Automattic and its CEO Mullenweg of "abuse of power, extortion, and greed," and said it seeks to prevent them from inflicting further harm against WP Engine and the WordPress community.

WP Engine is a major rival to WordPress.com, with more than 200,000 websites using the service. Mullenweg runs Automattic, which owns WordPress.com, a company that sells a hosted version of the open-source WordPress software - just like WP Engine.

Automattic, the parent company of WordPress.com, asked rival hosting service WP Engine to hand over 8 percent of its revenue each month before igniting a very public battle over what you can and can't do with an open-source project.

On Wednesday, Automattic published the proposed deal that it sent to WP Engine on September 20th. The proposal lays out a seven-year agreement that gives WP Engine the right to use the WordPress trademark in exchange for a hefty payment. The 8 percent cut could either be paid as a royalty fee to Automattic or as salaries for WP Engine employees who would contribute to the WordPress.org open-source project.

WordPress is essentially internet infrastructure. It's widely used, generally stable, and doesn't tend to generate many splashy headlines as a result.

But over the last week, the WordPress community has swept up into a battle over the ethos of the platform. Last week, WordPress cofounder Matt Mullenweg came out with a harsh attack on WP Engine, a major WordPress hosting provider, calling the company a "cancer" to the community. The statement has cracked open a public debate surrounding how profit-driven companies can and can't use open-source software - and if they're obligated to contribute something to the projects they use in return.