Maybe it's time to fork WooCommerce

#1

Looks like Matt & Co. continue with their aggressive takeover of the WordPress universe for their own commercial benefit.

First they forced Gutenberg down our collective throats.
Then, Jetpack dropped support for anything below WP 5.0 and started promoting paid upgrades to anyone who installed it
Now, news emerges that WooCommerce will add suggestions for extensions but only if they are in the official Woocommerce marketplace. Other extensions (even if they are in the official repo) will not be mentioned.

I think it is pretty obvious where this is going and unfortunately WP is quickly turning to the ‘dark side’.

Luckily, WP and repo plugins like Woocommerce are all GPL which means they can be forked.

Forking Woocommerce by the ClassicPress community is a very smart move IMO. Not only it will further raise the profile of the ClassicPress project as a whole but it will actually be beneficial in the sense that it will ensure Woocommerce will remain compatible with ClassicPress.

The Jetpack example proves definitively that Woocommerce will eventually stop working on websites that don’t have Gutenberg (which obviously includes anyone using ClassicPress) and it will probably won’t take that long as its owner is clearly on an ‘evangelical’ mission to convert (figuratively and literally!) everyone to Gutenberg.

Thoughts?

6 Likes
#2

Hi @ginmi and welcome. It’s a great idea and one that has already occurred to the CP community. We have a product name, a domain name reserved (classiccommerce.cc), a logo designed and some of our members are working on the code now.

Here are some links…

naming discussion: WooCommerce
logo discussions: ClassicCommerce Logo
latest progress with coding: Woocommerce fork

If you can help at all it would be very much appreciated.

6 Likes
#3

By the way, I hadn’t seen the latest development with WooCommerce pushing ads for their related products…

“Marketplace Suggestions Require Dismissal Every Day for 5 Days, Only to Return 1 Month Later”

Wow!

1 Like
#4

As an addition to @ozfiddler’s answers. @parkerj is currently leading the effort of the CP fork of WooCommerce, if you have questions of status and details, you should probably contact him.

2 Likes
#5

Thanks @ozfiddler & @klein.

Any ETA for the first public release of a Woo Fork @parkerj?

2 Likes
#6

Here is a list of places @parkerj seems to need some help in:

3 Likes
#7

Version 1.0.0 is currently set for June 3rd: https://github.com/ClassicPress-research/classic-commerce/milestones

5 Likes
#8

if you create another version of Woocomerce, please include an invoicing, vat ID and reminder system :smiley:
Just something that every ecommerce must have

1 Like
#9

@ced1870 - Hi Cedric and welcome! There is a GitHub page for this but I have also created a post here and added in your suggestions: Necessary plugins/extensions for ClassicCommerce

1 Like
#10

thanks, I’m going there :slight_smile:

1 Like
#11

I guess it will be an heck of job, but ecommerce is very important to show the power of the platform.
it could also be a good reason to improve the little thing that still bug me.

Speaking of ecommerce. I m using EDD - and i love it - small,fast, easy to use. Pippin is super proactive. I d ask him if he would support CP, too

4 Likes
#12

Rotello if you’ve talked with Pippin before, please feel free to reach out to him to ask if he’d be willing to support CP. I don’t remember if others here have done that yet but it can’t hurt – and we sure would love to have the support!

1 Like
#13

He is very active. i think that writing a ticket may be enough to get an official reply.
I wonder if someone whose first language is english (and has good communication skill) can write a 3-4 line pitch for CP, so we all can use and spread :slight_smile:

1 Like
#14

Actually, everyone using the same pitch could be dismissed as spam. Would be better if everyone makes their request in their own words.

3 Likes
#15

We’ve had an email template for this for some time now. https://www.classicpress.net/faqs/#is-there-a-sample-email-we-can-send-to-plugin-developers-to-ask-for-classicpress-compatibility

Feel free to use this as inspiration for your own message, but as Ray says, it’s better to write in your own words about why you want this.

1 Like
#16

I see they were added

cc: https://github.com/ClassicPress-research/classic-commerce/issues/8