The open-source software community is facing a challenging moment. Recently, I’ve come across numerous Reddit threads and blog posts discussing the ongoing situation with WordPress, it’s founder and WP Engine. For those who may not be aware, this controversy stems from a significant disagreement between a prominent figure and a major company in the ecosystem.
If you’re interested in understanding the details and implications of this conflict, I recommend reading a few articles that provide a comprehensive overview. These pieces not only summarize the events but also highlight the broader effects this disagreement could have on the future of open-source development.
- WP Engine Must Win
- The dispute between WordPress and WP Engine now only hurts the end users
- WordPress.org bans WP Engine, blocks it from accessing its resources
- Reddit.com
What’s truly disheartening about this situation is that the founder of WordPress is inadvertently harming end users, contributors, and WordPress consultants and developers due to his disagreement with a hosting company, WP Engine. Regardless of whether I share his concerns about WP Engine’s use of the WordPress trademark or their level of contribution to the core project, his approach is troubling. If he feels compelled to take a stand against them, that’s his prerogative. However, doing so at the expense of the very community that relies on WordPress is deeply concerning. The consequences of this conflict could have lasting negative effects on those who depend on the platform, and it’s disappointing to see personal disagreements overshadow the broader interests of the community.
So, what’s the way forward from here? To be honest, I believe it’s time for me to step away from WordPress. I plan to cancel all my WordPress subscriptions. As for whether I will migrate my blog content to a new platform, I’m still undecided.
Interestingly, I don’t feel particularly sad about this decision. A few years ago, I walked away from WordPress to focus on my own open source projects. Although I chose to return to the platform recently, I found myself questioning whether it was the right choice and whether I should stay. Ultimately, I believe this is the best move for me at this point in my journey.
I am currently deep into the development of a PHP web framework called CodefyPHP. This framework is specifically designed for complex applications that require domain-driven development (DDD), Command Query Responsibility Segregation (CQRS), and Event Sourcing.
In addition to this framework, I have also been working on a blogging platform. A few years ago, I developed a headless Content Management System (CMS) called QubusCMS, which I plan to revive and dedicate more time to. I believe it’s time for a fresh contender in the market.
Recently, I set QubusCMS to read-only mode. The reason for this decision is that I haven’t yet determined whether to upgrade the existing system or to start from scratch using my new DDD framework. My vision is to transform QubusCMS into a headless, domain-driven CMS, which I believe would be an excellent solution for enterprise-level applications.
If I choose to upgrade the CMS in its current form, I will also create a separate enterprise version built on top of the CodefyPHP framework. This dual approach will allow me to explore different possibilities and better serve the needs of users seeking a robust, enterprise-ready CMS.