The ongoing conflict between WordPress co-creator Matthew Mullenweg and WP Engine has intensified, raising concerns about the future of open-source collaboration. It all began when Mullenweg announced that WordPress.org would fork the “Advanced Custom Fields” (ACF) plugin, rebranding it as “Secure Custom Fields” (SCF) due to alleged security vulnerabilities.

This move automatically transitioned users of ACF, managed by WP Engine, to the new SCF plugin. However, critics argue that WP Engine had already patched the security flaw, making the fork appear more as a retaliatory action amidst a broader legal dispute between the two parties.

Mullenweg’s frustrations with WP Engine stem from the hosting provider’s use of WordPress without, in his view, contributing sufficiently to its development.

Tensions escalated when Mullenweg blocked WP Engine users from accessing WordPress.org resources, prompting WP Engine to create its own plugin delivery system. The dispute has not only fractured the community but also impacted events like WordCamp Sydney, where WP Engine was suddenly removed as a sponsor without explanation.

FOSS advocate David Heinemeier Hansson has called for reconciliation, warning that using open-source platforms as leverage in commercial disputes could set a dangerous precedent. He urged Mullenweg to resolve the issue and preserve the spirit of collaboration that underpins the open-source world.

As the feud continues, it threatens to upend the neutrality and cooperation that have long defined WordPress and other open-source projects.