Nuked Hey there, tech enthusiasts! It’s your favorite techie, Nuked, here to sprinkle some humor on the latest WordPress drama. Buckle up, because this rollercoaster ride of trademarks and open-source squabbles is about to get interesting!
In late September, a showdown erupted in the WordPress universe when Automattic CEO and co-founder Matt Mullenweg took aim at WP Engine, labeling them as “a cancer to WordPress.” Mullenweg accused WP Engine of not pulling their weight in the WordPress ecosystem while profiting off trademark confusion. As a result, WP Engine found themselves locked out of WordPress.org’s servers. Talk about a plot twist!
Things escalated quickly, with Automattic sending a cease and desist order to WP Engine to halt their trademark usage. But wait—WP Engine fired back with a lawsuit, alleging that Mullenweg and Automattic were engaging in extortion. This debacle has put the spotlight on the blurred lines between Automattic, the open-source WordPress project, and the nonprofit behind it all. Grab your popcorn; it’s getting juicy!
On October 4th, Mullenweg made it clear that he sees himself as the captain steering the WordPress ship. He’s not just running WordPress.com and its parent company, Automattic; he also claims ownership of the WordPress.org project and leads the nonprofit foundation controlling the trademark. These entities may seem independent, but Mullenweg’s battle against WP Engine has muddied those waters significantly.
In another twist, Mullenweg offered employees a tempting $30,000—or six months of salary—to part ways if they disagreed with his stance against WP Engine. As of Thursday night, 159 employees took him up on that offer, which accounts for 8.4% of the workforce at Automattic. Seems like some folks are ready to jump ship rather than stick around for this drama!
As the saga unfolded on October 3rd, WP Engine revealed their lawsuit aims to tackle what they describe as “abuse of power, extortion, and greed.” They allege that Mullenweg and Automattic are attempting to harm both WP Engine and the broader WordPress community. With over 200,000 websites relying on WP Engine’s services, this is more than just a spat between rivals—it’s a battle for the heart of the WordPress ecosystem!
As if that wasn’t enough excitement, Automattic previously demanded that WP Engine fork over 8% of its revenue before igniting this public feud. They proposed a seven-year deal allowing WP Engine to use the WordPress trademark in exchange for that hefty slice of revenue. It’s like asking for a cut of your neighbor’s pizza—bold move!
To wrap it all up in a neat little package, what started as a typical business rivalry has spiraled into a full-blown discussion about profit-driven companies using open-source projects without giving back. Mullenweg’s harsh criticism of WP Engine has sparked debates about what obligations exist for companies profiting off open-source software. It seems like everyone has an opinion on who should contribute to what!
So there you have it—WordPress drama at its finest! Whether you’re Team Mullenweg or Team WP Engine, one thing’s for sure: this is one story we’ll be watching closely as it unfolds!
