I’m bringing some points from another conversation that’s relevant for this discussion.
There are two groups of ClassicPress users. Those that want ClassicPress to move faster away from WordPress and ignore (largely) backward compatibility and those that want to maintain backward compatibility for as long as possible to ensure ClassicPress is stable and doesn’t cause problems for users like Gutenberg did when it was introduced.
Both have valid points. Both are necessary for ClassicPress to be stable, yet continue to move forward. The reality is, the core development team doesn’t have enough developers to move forward faster. Moving forward faster means more testing, more troubleshooting, and more bugs to deal with. If we had more core developers, we could do more work and move faster. We don’t, that’s the reality.
It’s a catch-22. ClassicPress needs more developers to move faster, but because it’s moving slower some developers are not willing to contribute their time. So we’re back to moving slower. Unless developers commit to helping develop the core, working on changes they want to see in ClassicPress, nothing will change. So you have to be the change. I wanted to see improvements to the login form, so I’m working on them myself after the community showed support in the changes I wanted to make.
You’re right, many items on that list are part of the roadmap, but as I said before ClassicPress needs more developers to help bring these changes to fruition.
TinyMCE v5 is already in the works. The next main thing that ClassicPress needs to begin work on is the core plugins. @MattyRob did an excellent job creating the initial research fork where he pulled out several features into core plugins. He can’t do everything himself. We need people to test and help develop these core plugins into stable, functional core plugins that can be included in v2.
https://github.com/mattyrob/ClassicPress/tree/experimental/core-plugins
So that would be a good place to start and bring the change that you desire to ClassicPress.
If core development isn’t your thing, Classic Commerce could use a lead developer.
@ozfiddler brings up a good point. Other than the roadmap, we don’t have much strategy in place. It’s a side effect of not having enough core contributors to work on a concrete plan. But also, we haven’t had a core meeting in months, if not years. I think the last meeting we had was prior to starting the work on 1.3.0 this past spring. Not sure if that’s something @james and @wadestriebel will bring back.
The core development did pick up, with weekly PR scrub meetings. So ClassicPress is moving forward, albeit slowly. But forward nevertheless.
Everyone wants version 2, but what will it actually have? TinyMCE v5 might be the feature to deliver us version 2, but that’s still in the research stage and months away because there’s only one developer working on it right now if I’m not mistaken @joyously
We were supposed to have core plugins in version 2, but other than the initial work by Matt, nothing else has been done. Unless someone helps with it, it’s not going to be in version 2.
The point is, roll up your sleeves and do what you can to help ClassicPress move forward. Talking about it won’t change anything.