My late night project for openmage v21

[fballiano]

So, you all know I want to remove a lot of code from OM's repo and delegate responsability to the original authors, I a forked OM v20 on my repo and started the work:
https://github.com/fballiano/openmage/tree/mcommerce

I called it mcommerce at the moment, I don't really know why but that's beside the point.

Notes:

• based on OM 20
• bumped requirement to >=php7.4
• moved to zf1-future installed via composer
• moved net_idna2, linuxlibertine-fonts, phpseclib, mcrypt_compat to composer requirements
• moved colinmollenhour/cache-backend-redis and colinmollenhour/magento-redis-session to composer suggest
• added some other modules to composer suggest (like image cleaner and full page cache)
• updated emogrifier to 6.0 (installed via composer)
• removed web based installation system (you can install via command line or magerun)

Preliminary tests are ok and I'm really liking it. I'd obviously a little "edgy" but I think that is the direction to go.

I'd like it to be the next OM and I hope it will not take years to bring some more news into OM.

Let me know what you think!

[kiatng]

Next OM, modernize the js framework for use in both front and backend.

[fballiano]

all of the current changes are compatible with the past but what scares me about the javascript part is that most of the frontend modules (and payment methods) won't work anymore

[addison74]

It is difficult to express an opinion at this moment, but I have gone through such situations when certain projects fell apart due to contrary ideas, non-involvement, delay in achieving the objectives.

If you have made your own repository I presume that your work will focus there abandoning what exists here in OM. I don't consider it a timely decision because there are still issues and PR that need to be analyzed and integrated. We had barely managed to achieve the impossible by decreasing the number of issues and PR's and we are talking about projects whose finality is not known. For better or worse OM offers us an umbrella for everyone at this moment.

I would have preferred to discuss first any important changes you intend to make than to be made to choose whether to follow you or not. Honestly speaking, you have created some PR's lately that I would have liked to discuss before publishing. I also feel a certain upset in your message, a personal disappointment. You are an excellent programmer and organizer and for sure I would miss you.

[fballiano]

I don't know where you read all of this disappointment cause there's none.
I just don't like sitting and waiting when I have time to experiment, that's why I experiment and I hope somebody says "ah nice idea let's take it from there".

The PRs I opened and not written in stone so now it's the time to discuss them, in the PR itself. In some of them I specifically wrote "feedback and suggestions are welcome".

[addison74]

Nowadays it becomes more and more difficult to express a personal opinion because someone will come to tell you that it is wrong. I'm sorry if my previous message upset you in any way. I am not in the category of those who are waiting or sitting down, but I think that teamwork involves other more subtle things. I will think seriously about what is happening here and I will make a decision.

[fballiano]

I'm not upset in any way. This branch that I created is a test to show what's my vision. What I hope? That it will become OM v21, I dislike fragmentation and FLOSS should be about getting together.
But again, I've a bit of time lately and I'll try to produce stuff, I hope I'll be able to open more PRs soon since I've some ideas. And all my PRs (when I think they're something that should be integrated in the core) will be in OM, not anywhere else.

[fballiano]

Apologise if perhaps I write in a "too assertive" way and that seems I'm upset but I'm really not.

[elidrissidev]

I'd like to see a complete implementation of the REST API.

[fballiano]

I've never used the REST API so... what's missing in your opinion?

[elidrissidev]

A bunch of stuff, adding comments to orders, CRU* operations for invoices, shipments, coupons, etc...

[kiatng]

I do not know how to use the Rest API, I tried but it didn't get anywhere. I used the old SOAP. Then I learned JSON-RPC from Colin, now it's the API that I use for projects. JSON-RPC is very lightweight and easy to implement. It is a direct replacement to SOAP in OM. The same endpoints for SOAP/XML-RPC work right of the box for JSON-RPC.

[elidrissidev]

Indeed the default authentication method for the REST API: OAuth 1, is very difficult to use and it's not possible to use for authenticating standalone scripts. I made my own extension to add support for HTTP Basic authentication which greatly simplified that.

My biggest concern with the SOAP API is its slow performance.

[fballiano]

#2273 :-)