I’d suggest asking the WooCommerce team (via a GitHub issue) if they are going to keep support for WordPress 4.9.x in new versions, as many people will not be upgrading. If they can do that, then that makes our part much easier.
1 Like
Thanks, I will ask them via a ticket, I don’t know what a GitHub issue is.
However whatever they say may not actually be what happens of course.
2 Likes
If someone (cough) was crazy enough to fork WooCommerce, what would this kind of support look like?
2 Likes
I think that would be something we (the committee) would need to clearly define and chat about.
Are you thinking of becoming that crazy person? 
I’ve been thinking of becoming that crazy person for a while now, even before these conversations started.
6 Likes
@parkerj Just to say that you are not alone in this, already heard that from a few persons(myself included) 
I think it will happen at some point but it could be soon now. At the moment there aren’t any issues in running Woocommerce in ClassicPress.
1 Like
@parkerj the good news is that you have a lot of freedom to undertake this effort as you see fit. The bad news is that we wouldn’t be able to provide much official help or support right now, beyond giving you a place to put the code if you want, and maybe some commiseration mutual learning about all the things that need to be done to successfully fork large projects.
Are you thinking of forking WooCommerce yourself, or under the ClassicPress name?
If the former, well, you don’t need anything from us to get started 
If the latter, we could use the ClassicPress Research · GitHub organization and create a repository there. This is a semi-official place for experimental plugins that may one day be official recommendations from within the ClassicPress dashboard, or even integrated into the core software (not as likely in this case).
Either way, if you’re able to create and stay on top of a fork of WooCommerce, then kudos to you. And either way, what will ultimately determine the success of the project is whether members of the community choose to use it on their sites.
1 Like
Definitely under the ClassicPress name.
3 Likes
Ok, so I just need your GitHub username (feel free to send me a direct message here, or on Slack or Discord if you don’t want to share it publicly) and the repository name.
Repository name: ClassicCommerce? Something else?
My Github username is parkerj. But before we proceed, should we vote on what the name should be?
At this point the vote would be between “ClassicCommerce” and “something else”.
We can wait a day or two and see if other suggestions and a consensus emerge. It’s also not a big deal to change the repository name, so I wouldn’t worry about this too much until you’re ready to start actually changing the name in the code.
That was the name that immediately came to mind for me.
( “something else” just doesn’t grab me 
)
4 Likes
You should consider names that have an available .com domain, it’ll be needed later down the road for sure.
- Open Commerce Kit
- Commerce Kite
1 Like
.org is available though
Definitely Aussie humour.
These are what we have so far:
ClassicPress Commerce (.com available)
Commerce Kite (.com available)
Commerce CP (.com available)
Commerce Classic (.com available)
Open Commerce Kite (.com available)
1 Like
CP Selling (.com available)
Classic Sold (.com available)
Cart CP (.com available)
Cart Classic (.com available)
Logical Commerce (.com available)
Cobra Commerce (.com available)
2 Likes
Personally I still like ClassicCommerce better than any of these other names.
I don’t think it should be a requirement to have the .com name available. After all, we run ClassicPress off of ClassicPress.net because ClassicPress.com was unavailable.
3 Likes
Since it will be the first commerce plugin to support ClassicPress, you could probably use idhsbdusvz.com and people would find it. But, yeah, Classic Commerce has a nice ring to it.