Does anyone want to work on ClassicPress v2 (with breaking changes)?

[james]

@alvarofranz

Yo waddup! I like the idea. Count me in.

Great

You have expressed a lot of enthusiasm for this approach here and in other threads, for example:

@alvarofranz

So I will stay tuned and when/if the CP community part that wants to “move away from WP” as you call it gets bigger than the other one, then I will definitley roll my sleeves up, probably even tear them off the shirt.

Enthusiasm is a great first step. The next step is doing the work to make it happen. So, I invite you to try out this approach.

@alvarofranz

We would need an actual repository and someone who takes care of PRs there (@james what do you say?).

Sure, I created one: GitHub - ClassicPress-research/ClassicPress-next: The CMS for Creators. Stable. Secure. Instantly Familiar. Forked from WordPress.

It is under ClassicPress-research and named ClassicPress-next because it’s not currently clear to me whether this would be released as v2 or v3 etc, and on what timeline. I imagine that alpha and beta releases would be published here on the forums for people to try, and then the repository would be moved/renamed when it gets closer to an actual release.

Other than that, I think you should be the first person to “take care of PRs” there. If you are willing to help with this as you’ve stated, then send me your GitHub username (here or in a DM) and I’ll add you so you can get started.

Multiple people have expressed a desire for ClassicPress development to work this way, and I’d be happy to see this take off. In that case, I would take responsibility for the ClassicPress v1 branch and leave the work on future versions to others.

@ElisabettaCarrara

Here, I am developing a cool new feature that is very different. I will release it in V2 since it’s a breaking change and I am taking my time to release it to ensure that you can upgrade from your V1 to the new V2 safely.

When breaking changes are introduced, there is generally no way to guarantee safe upgrades. This is one of the biggest issues with breaking compatibility: how do you make sure that people can upgrade? For a high-profile example of this I suggest taking a look at the transition from Python 2 to Python 3.

In this case, what would the upgrade path from ClassicPress v1 to v2-with-breaking-changes look like? This isn’t something to be solved today but it needs to be kept in mind when planning a future version with breaking changes.