I came across this article an year ago about Spree commerce core team moving out after being acquired by a company called FirstData.
I have not seen any conversations happening w.r.t this in this forum, so wanted to initiate some discussion around it.
A quick flow of developments & state of affairs at Spree is here, which is a must-read to get a quick hang of things.
As per my understanding there are two active communities globally working on developing core Spree, which are as below.
Solidus team, which forked Spree at 2.4, and started working focusedly on various issues to make Spree more usable.
In this blogpost, which is a lil self promoting version of themselves, Solidus explains why we should fork to Solidus and start exploring all the work they are doing, and as they are also working with the same ethos of Opensource, I guess it would be fair to have a look at if any work they have done would be useful with what we are building.
I was trying to go a little deep and see some of the features and extensions these teams have been working on & I came across a few of features we have been discussing. For ex.
Multi Domain Store : As explained by Solidus team here, Though this doesn’t fit our exact need of whitelabelling, I think there is some work been done on using one backend connecting to multiple front-end’s.
Soliud Extensions : A list of extensions, from payment gateway(stripe), to printing invoices etc.
Backend Admin Interface : Solidus seems to have put some effort in de-cluttering the backend, documentation for same.
But Spree 3.x also seem to use Bootstrap in frontend and backend, so more food for thought.
I tried to quickly setup the solidus on heroku here (username : firstname.lastname@example.org, pwd : test123) and have a look, the backend looks balanced, but as we are discussing about a single interface for both frontend & backend off late with discussions from @paroga, surely more thought reqd.
I was wondering if we could put forward our vision with these teams too, & express how we are heavily investing in Spree as our Future choice, & discuss how we could collaborate with them w.r.t building these features/customizations, so that there are not multiple efforts/funds spent to build these features on Spree.
And this also might be a step forward in helping us contribute to the Spree Global Commons.
p.s : Both of these teams have slack channels too with some active discussions happening too, so random discussions w.r.t Spree & OFN can be put up there too.