Automattic Dramatically Cuts WordPress Contributions, Escalates Feud with WP Engine
Automattic, the company behind WordPress.com, has drastically reduced its weekly contributions to the open-source WordPress project from a staggering 3,988 hours to a mere 45 hours. This move, announced on Thursday, marks a significant escalation in the ongoing feud between Automattic and its rival hosting provider, WP Engine.
The drastic reduction in contributions is attributed to two primary factors:
- Legal Battle with WP Engine: The ongoing legal dispute between Automattic and WP Engine has diverted significant resources and attention. Automattic argues that the legal action initiated by WP Engine consumes valuable time and energy that could otherwise be channeled towards supporting the growth and health of the WordPress ecosystem.
- Community Pressure and Criticism: Automattic has faced intense criticism from within the WordPress community, with some members demanding that CEO Matt Mullenweg and other key figures distance themselves from the project. This pressure, coupled with the legal battle, has influenced Automattic's decision to significantly scale back its contributions.
Automattic's Contribution Model:
Automattic will now contribute 45 hours per week to the WordPress project through the "Five for the Future" program, which encourages companies to contribute 5% of their resources back to WordPress.org. These contributions will primarily focus on critical updates and security enhancements.
The Roots of the Conflict:
The conflict between Automattic and WP Engine stems from a series of events, including:
- Mullenweg's Public Campaign Against WP Engine: Mullenweg publicly criticized WP Engine, labeling it a "cancer" to the community. He also took over WP Engine's popular ACF plugin, further escalating tensions.
- WP Engine's Lawsuit: In response, WP Engine filed a lawsuit against Automattic and Mullenweg, alleging that Mullenweg's actions were designed to induce breach or disruption. A judge subsequently granted WP Engine a preliminary injunction.
- Internal Turmoil at Automattic: The conflict has led to internal turmoil within Automattic, with some employees leaving the company after being offered buyouts due to their disagreement with the company's stance against WP Engine.
Impact on the WordPress Ecosystem:
Automattic's decision to drastically reduce its contributions has significant implications for the WordPress ecosystem:
- Slower Development: The reduced development effort may lead to slower development of new features, bug fixes, and security updates.
- Increased Vulnerability: Slower security updates could increase the vulnerability of WordPress websites to cyberattacks.
- Erosion of Community Trust: The conflict between Automattic and WP Engine, coupled with Automattic's reduced contributions, could erode trust within the WordPress community.
- Potential for Forking: The reduced involvement of Automattic could increase the likelihood of forking within the WordPress community, where developers create their own versions of the software.
Conclusion:
The dramatic reduction in Automattic's contributions to WordPress marks a significant turning point in the history of the open-source platform. The ongoing feud with WP Engine, coupled with internal pressures, has forced Automattic to make a difficult decision that could have far-reaching consequences for the future of WordPress.
