The poll is closed now. Path 1 has 20 votes while Path 2 has 18 votes.
Although path 1 has more votes than path 2, the difference is negligible and highlights how divided the ClassicPress community is. What’s more important is that every participant wants ClassicPress to exist and grow.
With the WPTavern article about our “crossroads”, many outsiders across social media channels said they don’t understand why ClassicPress was created to begin with, how it survived for over 4 years, that it’s a stupid idea, and that it will die.
Comments like that are not new. We’ve heard them since day one, we’ve heard them when ClassicPress turned 1 year, 2 years, 3 years, and 4 years and they will continue… so will ClassicPress.
ClassicPress continues to exist and slowly grow because it’s not WordPress without Gutenberg. It is WordPress. It stayed true to WordPress philosophy, something WordPress leadership failed to do in order to advance their commercial interests. There’s a reason why Matt killed WordPress Governance project, then pushed a half-baked, bug-ridden Gutenberg into the core a few months before securing $300 mil and $80 mil from investors to compete with website builders. Why some controversial features are forced into the core by Google-sponsored contributors. WordPress might be open source, but it’s not a community-driven project anymore.
Gutenberg was the breaking point for the community when WordPress failed its own philosophy:
The core of WordPress will always provide a solid array of basic features. It’s designed to be lean and fast and will always stay that way. We are constantly asked “when will X feature be built” or “why isn’t X plugin integrated into the core”. The rule of thumb is that the core should provide features that 80% or more of end users will actually appreciate and use. If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. If we stick to the 80% principle then this should never happen.
We are able to do this because we have a very capable theme and plugin system and a fantastic developer community. Different people have different needs, and having the sheer number of quality WordPress plugins and themes allows users to customize their installations to their taste. That should allow all users to find the remaining 20% and make all WordPress features those they appreciate and use.
The Gutenberg plugin is still 2 stars. Classic Editor is still 5 stars.
ClassicPress users don’t hate WordPress, they love it. That’s why they chose to use ClassicPress instead of Joomla, Drupal, etc. WordPress right now is basically MySQL when Oracle acquired it, so now we have a community-driven MariaDB (or ClassicPress in our case). No wonder WordPress lost market share for the first time recently.
Forking is a natural part of an open-source project’s lifecycle. Even WordPress was a fork of b2/cafelog. Look at all the Linux-based operating systems and their forks, and forks of those forks. When the project doesn’t meet the specific needs of a group of users and these users are willing to dedicate time and money to make something to fill their needs you get a fork.
WordPress didn’t (and still doesn’t) meet the needs of a group of users. The fork lives on:
After listening to part of the #WordPress #StateOfTheWord I am so glad I have stopped using WordPress and moved to @classicpress (source)
Frankly, many developers in the ClassicPress community use both. I use WordPress for many projects and when I need something lighter, leaner, and easier to use I choose ClassicPress. Use the right tool for the right job, not everything is a nail that needs to be hammered in. Sometimes you need a screwdriver, sometimes an Allen wrench. Pick the right tool for the right job.
ClassicPress won’t beat WordPress. It doesn’t have to. It will help fill the needs of users that WordPress can’t fill anymore. This is why forks are important.
ClassicPress community has made mistakes, no open-source community is perfect. We’ve learned from our mistakes and are trying to implement changes to build a better foundation for the project to grow.
That’s my personal 2 cents.
This topic will be closed.
The core contributors will discuss the results of the poll, the feedback given by the users, and what we can realistically accomplish. All active contributors will be contacted. Since it’s the holiday season this may take a few weeks. We’ll try to draft a plan/roadmap to leave this crossroads behind us, and give WPTavern something to write about again.
Anyone willing to start contributing to the core should PM me, but all non-coders are encouraged to step up and help the project grow - writing documentation, translations, testing, marketing, blogging, etc. Whatever your skills are, they can help ClassicPress grow. PM me, join Slack, stop by GitHub, pick your channel. Donating to support ClassicPress is also a great way to show you care!
And remember, use WordPress, use ClassicPress, use Joomla, use Drupal, use Django, use Laravel, use Backdrop, use the right tool for the job.