The Wordpress drama keeps getting worse

What sparked the WordPress drama with WP Engine?

The WordPress drama with WP Engine was ignited by a conflict involving Matt Mullenweg, the CEO of WordPress.com. He raised concerns over WP Engine's contributions to the WordPress platform.

Dissatisfaction arose when he believed that WP Engine, which hosts WordPress sites, was not giving back enough to the community.

Matters worsened when Matt felt entitled to an 8% royalty on WP Engine's revenue—a point of contention that many considered absurd. This led to increased tensions as Matt accused WP Engine of ignoring essential contributions, such as event sponsorships like WordCamp.

Explore more on what sparked the conflict to understand the depths of this drama.

How did Matt Mullenweg's actions escalate the situation?

Matt Mullenweg's actions significantly escalated tensions with WP Engine and within the broader WordPress community.

• He restricted WP Engine user access to WordPress.org, impacting the ability to do crucial updates and plugin management.

• Publicly threatened WP Engine, aiming to make it an undesirable platform, and expressed intentions to harm its customers.

• Imposed a contentious checkbox on the WordPress.org login, obstructing access for those affiliated with WP Engine, leading to severe backlash.

These actions were compounded by misleading communications and extortion-like threats against WP Engine, as detailed in the WordPress lawsuit documents.

Steps like these have drawn significant criticism against Matt, raising concerns about the impact on WordPress' reputation and the ethical implications within open source communities.

What are the implications of the Advanced Custom Fields plugin takeover?

The WordPress plugin takeover of the Advanced Custom Fields (ACF) plugin marks an unprecedented move in open source history. WordPress.org's decision to forcibly take control of an actively managed plugin from its creators at WP Engine has sparked widespread concern. This takeover violates the principles of open source collaboration and has set a dangerous precedent.

"A plugin under active development has never been unilaterally and forcibly taken away from its creator without consent in the 21-year history of WordPress."

Such actions could lead to mistrust within the open source community. The implications for trust and collaboration are profound, with fears this might inspire similar moves elsewhere. The situation threatens to undermine confidence in the open source ecosystem and its core values. Exploring the potential implications for the WordPress community is crucial to understanding the broader impact.

How has the WordPress community reacted to these events?

The WordPress community has reacted with a mix of outrage and disappointment to the Matt Mullenweg controversy. Former employees, like an ex-Automattic worker, expressed shame over having been affiliated with a company now marred by such contentious actions. One remarked, "I'm ashamed I ever worked there," emphasizing the emotional impact of the situation.

Notable figures in open source, including DHH, have also voiced their concerns. He urged, "Matt, don't turn into a mad king," highlighting the potential damage to WordPress's reputation. Additionally, he pointed out the risks this sets for the open source community impact.

Community sentiment echoes worries over the WordPress plugin takeover of Advanced Custom Fields, with many commenting it's a step too far. These tensions have led to fears about longevity and trust in WordPress, impacting long-time contributors and everyday users alike. For detailed insights, explore the potential implications for the WordPress community.

What are the potential consequences for WordPress and open source?

The escalating Matt Mullenweg controversy and the actions surrounding the WP Engine lawsuit could have significant repercussions.

1. Reputation Damage: WordPress's long-standing reputation may suffer due to public controversies, as detailed in the recent WP Engine lawsuit. Community trust is at risk.

2. Reduced Contributions: Unilateral actions like the WordPress plugin takeover could deter developers from contributing to open-source projects. This impacts WordPress's ability to innovate and evolve collaboratively.

3. Legal Precedents: The legal disputes might set a precedent impacting open source governance, potentially leading to increased trademark disputes and stricter controls over community contributions.

4. Community Fragmentation: There's potential for fragmentation within the community as stakeholders argue over decisions. This could undermine the collaborative spirit that WordPress has thrived on, leading to a future of reduced cooperation.

Ultimately, these events highlight the necessity for resolution and transparency to maintain confidence and collaboration in the open source ecosystem.