-
Notifications
You must be signed in to change notification settings - Fork 544
Removing UPS integration #544
Comments
Why do you plan to remove UPS integration? |
Why this change? I mean, obviously UPS is a terrible organization, but I don't see any reason why including a wrapper around their API — that you already have to sign up for — would pose problems. Certainly you're still using these codepaths at Shopify; going back and wiping the entire project of any trace of UPS is pretty ridiculous. |
what is the motivation for this change? Was there some kind of legal issue in having it remain? |
Does anyone have a fork/clone with the original history? |
Yes. Email me at [email protected] i can send you a zip tomorrow
… On Nov 22, 2017, at 20:54, Jason Tokoph ***@***.***> wrote:
Does anyone have a fork/clone with the original history?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Super annoying, why was this done? |
I would also like to know the reason UPS requested the removal, and why the git history was rewritten to remove all trace of the code |
This is absurd. I sent an email to my rep this morning. I will share anything I learn. |
@maartenvg What is the status of 2.2.0 gem version? Are you going to release it? |
There's still gems with the old code, so a fork or extension of active_shipping that isn't associated with Shopify would probably need to be created where this code can live. |
WIP
The text was updated successfully, but these errors were encountered: