Introduction

In a dramatic escalation of the ongoing feud between WordPress co-creator Matthew Mullenweg and hosting provider WP Engine, tensions boiled over this past weekend. The chaos has left WP Engine seemingly unwelcome in the WordPress landscape, particularly within Mullenweg's faction, as an unprecedented move to fork a popular plugin unfolded.

The Forking of ACF

The conflict ignited when Mullenweg, representing the WordPress security team, announced on Saturday that a plugin known as “Advanced Custom Fields” (ACF) would be forked, and the new version would be branded as “Secure Custom Fields” (SCF). This action was allegedly taken to address certain security vulnerabilities and eliminate commercial upselling practices that were present in ACF.

Debate Over Necessity

However, the tone quickly shifted as questions about the necessity of the fork arose. Tim Nash, a well-known WordPress security consultant, pointed out that WP Engine's team had already patched a critical vulnerability in ACF prior to the fork announcement and shared it with the WordPress Security Team. This revelation raises a critical question: if ACF had already undergone necessary security updates, was the fork truly warranted?

Background of the Conflict

Mullenweg’s scorn for WP Engine stems from a belief that the company, which is backed by private equity, has profited from the open-source WordPress platform without adequately contributing to its development. Despite efforts from Mullenweg and his organization Automattic to engage WP Engine constructively, their calls for deeper collaboration fell on deaf ears.

WP Engine's Response

In retaliation to Mullenweg's restrictive measures, which effectively barred WP Engine users from accessing resources at WordPress.org, WP Engine took action by developing its own plugin delivery and update service. The situation intensified further, as WP Engine and ACF started to provide independent updates to their plugin.

Mullenweg's Defense

Mullenweg cited security concerns as the impetus for the fork, but he acknowledged the unusual nature of this situation by stating, "This is a rare and unusual situation brought on by WP Engine's legal attacks. We do not anticipate this happening for other plugins.”

Criticism from ACF

Responding sharply, ACF’s product manager Iain Poulson criticized Mullenweg’s actions, warning that they could irreparably damage the entire WordPress ecosystem. He accused Mullenweg of attempting to monopolize control over the open platform that countless developers rely on, portraying it as a breach of trust.

Impact on WordCamp Sydney

The ramifications of this feud have also impacted the upcoming WordCamp Sydney, set for early November. The event's organizers announced via their social media account that they had removed WP Engine as a sponsor due to the growing tensions, although it was noted this decision was not made solely by the organizing team. Confusion remains, as the organizers await a clearer directive from WordPress regarding WP Engine’s sponsorship status.

Legal Battle Looming

Moreover, a looming legal battle appears to be on the horizon. A company called Very Good Plugins has filed a lawsuit against Automattic and WordPress.com, alleging trademark infringements regarding "WP Fusion."

Community Reactions

As the WordPress fracas drags on, prominent figures in the open-source community are weighing in. Ruby on Rails creator David Heinemeier Hansson has voiced concerns over what he describes as alarming abuses within the open-source sphere. He warns against the use of open-source code registries as leverage in commercial disputes, calling for a return to neutrality to maintain peace among developers.

A Call for Reconciliation

In a passionate plea, Hansson urged Mullenweg to resolve this conflict amicably, emphasizing the importance of collaboration and mutual respect within the developer community. “It’s not too late,” he stated. “Look at those as sunk costs. Even in isolation, the additional expense from here on out to continue this conquest is not going to be worth it either. There's still time to turn around. To strike a modest deal where all parties save some face. I implore you to pursue it.”

Conclusion

As the WordPress community watches this drama unfold, the apocalyptic tone of the conflict raises concerns about the future of open-source collaboration. Will the parties involved reach a reconciliation, or will further escalation redefine the landscape of WordPress and its thriving ecosystem? Only time will tell.