A Dangerous Power Play: Matt Mullenweg's Latest Move Threatens To Totally Fork Him Over
A collaborative interpretation of Matt's effect on WP between myself and Leonardo.ai
A Call for Accountability in Open Source
Open source thrives on trust, transparency, and community collaboration. But recently, Matt Mullenweg, the CEO of Automattic who acquired WordPress, has taken actions that threaten to undermine these core values. By seizing control of the Advanced Custom Fields (ACF) plugin and attempting to stifle WP Engine under the guise of security concerns, Mullenweg has shifted from championing open source to centralizing power. This move doesn’t just endanger the WordPress ecosystem—it endangers the entire open source philosophy of collaboration and innovation. The WordPress community, like any other open source ecosystem, depends on shared values: transparency, freedom, and collective progress. These principles have been at the heart of WordPress since Automattic's involvement. However, Mullenweg’s recent power play with the ACF plugin—a community-developed tool trusted by thousands—signals a disturbing deviation from these ideals. By prioritizing control over collaboration, he risks damaging not just WordPress but also the open source community as a whole.
The Unique Power of Open Source
Open source is built on freedom, transparency, and collaboration. Unlike proprietary software, where control rests in the hands of a single entity, open source invites anyone to contribute, review, and modify code. This openness drives innovation and growth, and it’s what has allowed projects like WordPress to become dominant forces on the web, powering over 40% of websites globally. Mullenweg's recent actions go against these fundamental values. Instead of fostering a space where the community can thrive together, his attempts to centralize control threaten to reverse years of progress. Trust is the backbone of open source, and when that trust is broken, it discourages the very contributions that have made WordPress successful.
Lessons from the Past: Power Struggles in Open Source
The battle over control isn’t unique to WordPress. History offers valuable lessons on the dangers of centralized authority in open source. In 2010, Oracle's acquisition of Sun Microsystems brought control of OpenOffice under a corporate agenda. The community, fearing a loss of transparency and collaboration, responded by forking OpenOffice to create LibreOffice. Today, LibreOffice thrives as a community-led project, demonstrating the strength of collective action in preserving open ideals.Another example is the Node.js/io.js split in 2014. When developers felt restricted by Joyent's control of Node.js, they forked it to create io.js, a version driven by community ideals. Eventually, the projects reunited under a more open and collaborative governance model, showing that decentralization can ultimately lead to a stronger ecosystem. The WordPress community should heed these lessons: when authoritarian control threatens open source values, the answer is to act decisively in favor of community-driven solutions.
Centralized Power vs. Community Governance
Mullenweg’s appropriation of the ACF plugin marks a clear shift away from community-driven governance. By forcibly taking over a tool that was developed by and for the community, he sets a dangerous precedent—one that disregards the contributions of independent developers in favor of centralized authority. Open source software is supposed to be collaborative. If developers fear their contributions might be taken over without their consent, enthusiasm and participation will inevitably wane. Without community involvement, the project’s energy dries up, and what remains is a stagnant shell of its former self.
The Social Backlash and Erosion of Trust
The backlash against Mullenweg's actions has been swift and loud. Developers and WordPress users across the web have voiced their frustration over this authoritarian approach, which stands in stark contrast to the community-first origins of WordPress. Social media has become the battleground, with some defending Mullenweg's actions as necessary for security, while many others decry them as an overreach of power. This division has deepened the rift within the WordPress community, eroding the trust that is vital to open source projects. Without trust, open source cannot thrive; it cannot grow. The fracture caused by Mullenweg's power grab will take more than words to heal—it will take actions that re-establish community trust.
A Moral Issue, Not Just a Legal One
The controversy surrounding WP Engine and the ACF plugin should have been a moral debate about preserving the integrity of open source. Instead, it has devolved into a battle over control and licensing fees. By asserting trademark power and demanding licensing fees, Mullenweg has pushed WordPress towards monopolistic practices—the very kind of behavior open source was built to resist. If the community remains passive, we risk allowing open source to become a mere facade—controlled by those whose primary goal is profit, not community enrichment. It is critical that the WordPress community reclaims the narrative and ensures WordPress remains a free and open project.
Charting a New Course: Forking WordPress to Protect Its Future
The community now faces a choice: Allow Mullenweg to continue his unchecked control, or take decisive action to preserve the freedom that open source stands for. One of the most powerful responses available to an open source community is to fork the project. A hard fork of WordPress—perhaps called OpenPress—could help protect the core values that made WordPress successful while establishing a governance model that is truly decentralized. Forking isn’t an easy decision, nor should it be taken lightly, but it may be the only way to safeguard the project’s future. By creating a new, community-led version of WordPress, developers can ensure that the software remains open, free, and driven by collaboration.
A Call to Action: Fork for the Future
Matt Mullenweg’s actions have demonstrated the urgent need for the WordPress community to act. If the largest open source project on the internet can be controlled by one individual without accountability, then the entire model of open source is at risk. A fork is the best way to protect WordPress from monopolistic power plays. The time has come for the community to take a stand, to act, and to uphold the promise of open source. The future of WordPress—and the integrity of open source software—depends on our willingness to step up and take action now.
