Power, Politics, and WordPress

For over 12 years, I co-hosted a podcast called WPwatercooler with Sé Reed and Jason Cosper. We weren’t just discussing the latest plugins or updates—but as of late we were holding a critical mirror up to the WordPress ecosystem. We talked about its triumphs, its community, and, yes, its leadership. Our episodes often took a closer look at the actions and decisions of Matt Mullenweg, WordPress’s co-founder. We aimed to question what needed questioning, and our love for the community was always at the heart of those conversations.

But as of August 9th, 2024, I decided it was time to step away. The world of WordPress, its challenges, and its shifting dynamics had changed significantly over the years, and it felt right to close this chapter. Little did we know how intense those dynamics would become in just a few short weeks.

Since our last episode, a major dispute erupted between Matt Mullenweg and WP Engine, and it’s turned into a saga that’s raising serious concerns across the WordPress ecosystem—and even beyond. The conflict, as outlined in a recent Fast Company article titled "The WordPress drama could have major implications for the internet", centers on accusations from Mullenweg that WP Engine has built its success by extracting value from the open-source project of WordPress without giving back. It's one of many articles out there but the most recent I've read. It’s an accusation that, in itself, might resonate with those who’ve seen the commercialization of open-source projects before. But the way it’s been handled is another matter entirely.

Mullenweg's decision to cut off WP Engine’s access to crucial resources and the subsequent back-and-forth of cease-and-desist letters have left many in the community feeling unsettled. It’s not just about trademarks and IP anymore—it's about a shift in how power is wielded in a space that’s supposed to be community-driven. The fact that over 150 Automattic employees took buyouts rather than continue under the current leadership speaks volumes. It’s a clear indicator of internal tension and of a fundamental disagreement with how things are being handled. With the recent take over of the free ACF plugin in the repository it just shows the weird power dynamic at play here.

This whole situation is emblematic of why I’m relieved to no longer be producing WPwatercooler. I loved being a part of those in-depth conversations about WordPress, but it’s been exhausting to watch how what was once a passionate, open-source movement has been evolving—sometimes for better, but recently, for worse. Mullenweg’s recent actions remind me of the delicate balance between the ideals of open source and the realities of commercial interests. When WPwatercooler started, WordPress was this symbol of community empowerment, offering users the ability to own their digital presence. Heck, we even had a birthday cake and piñata on it's birthday made for it at my local meetup. Now, the ongoing dispute with WP Engine has made it feel like the vision has shifted more towards control and consolidation.

Looking back, it’s bittersweet. I miss the lively debates with Sé, Cosper, and the community. We always aimed to hold WordPress accountable because we believed in it. We saw the potential it had to be more than just software—to be a movement. And perhaps, that’s why it’s so tough to see this current chapter unfold. It’s not that criticism didn’t have its place, but that it was always done with a sense of hope for what WordPress could become.

Now, as October rolls around and this saga continues, I’m watching from the sidelines, in my jammies in our "slack", and I can’t help but feel relieved that I don’t have to dissect every twist and turn of this drama anymore. WordPress will always be an important part in that part of my life, but I’m ready for new conversations, new projects, and a little less turbulence.

It’s hard to say what’s next for WordPress or for Matt Mullenweg. There’s a lot at stake for the community and for the internet itself, as WordPress powers over "43.5%" of all websites. But one thing is clear: this is a turning point. Whether it’s a turning point towards a healthier future or a fracturing of the community remains to be seen. For now, I’ll hold onto the good memories of WPwatercooler and remain hopeful that the community spirit that made WordPress what it was can endure.

And maybe, just maybe, someone else will be there to hold up that critical mirror when it’s most needed. For now I'll just write my blog posts in Ghost while sipping coffee from a Yeti travel cup with WPwatercooler stickers on it.