In latest move against WP Engine, WordPress takes control of ACF plugin
The dispute between WordPress founder Matt Mullenweg and hosting provider WP Engine continues,
The dispute between WordPress founder Matt Mullenweg and hosting provider WP Engine continues, with Mullenweg announcing that WordPress is “forking” a plugin developed by WP Engine.
WordPress Founder Matt Mullenweg Announces "Forking" of WP Engine Plugin, Escalating Dispute
The ongoing dispute between WordPress founder Matt Mullenweg and hosting provider WP Engine has reached a new level of intensity, with Mullenweg announcing that WordPress will be "forking" a plugin developed by WP Engine. This move is seen as a significant escalation in the conflict, which has been brewing for some time.
For those unfamiliar, the dispute centers around WP Engine's development of a plugin called "WP Engine's Jetpack", which is designed to provide additional security and performance features for WordPress websites hosted on WP Engine's platform. However, Mullenweg and the WordPress community have raised concerns that the plugin is not compatible with the open-source nature of WordPress, and that it may create a closed ecosystem that undermines the platform's core values.
In a recent blog post, Mullenweg announced that WordPress will be "forking" the WP Engine plugin, effectively creating a new version of the plugin that is compatible with the open-source WordPress platform. This move is seen as a way for WordPress to take control of the plugin's development and ensure that it aligns with the platform's values and principles.
The decision to fork the plugin is not without controversy, however. Some have criticized the move, arguing that it will create confusion and fragmentation within the WordPress community. Others have expressed concerns that the forked plugin may not receive the same level of support and maintenance as the original plugin.
WP Engine has responded to the announcement, stating that they are "disappointed" by the decision to fork the plugin. The company has also emphasized that their goal is to provide a high-quality plugin that benefits the WordPress community, and that they will continue to develop and maintain the plugin regardless of the decision to fork.
The dispute between Mullenweg and WP Engine is not the first of its kind, and it highlights the ongoing tensions between the open-source WordPress community and commercial hosting providers. While WP Engine has been a major player in the WordPress ecosystem, the company's decision to develop a proprietary plugin has raised concerns about the potential for fragmentation and the erosion of the platform's open-source nature.
In the end, the decision to fork the plugin is a significant development in the ongoing dispute between Mullenweg and WP Engine. While it may create short-term challenges for the WordPress community, it also represents an opportunity for the platform to reassert its commitment to open-source principles and ensure that its users have access to high-quality, community-driven plugins.
As the situation continues to unfold, it will be interesting to see how the WordPress community responds to the forked plugin and whether it will ultimately benefit or hinder the platform's growth and development. One thing is certain, however: the dispute between Mullenweg and WP Engine is a reminder of the importance of maintaining the open-source nature of WordPress and ensuring that the platform remains a vibrant and inclusive community for developers and users alike.
The implications of the forked plugin are far-reaching, and it remains to be seen how the WordPress community will adapt to this new development. Some potential outcomes include:
Ultimately, the decision to fork the plugin is a significant development in the ongoing dispute between Mullenweg and WP Engine, and it will be interesting to see how the situation unfolds in the coming weeks and months.
Article