Closed (works as designed)
Project:
Commerce Stripe
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Apr 2012 at 22:44 UTC
Updated:
9 Aug 2012 at 18:19 UTC
There's an API module at Stripe. I am vascillating (sorta: #1533478: Backport to Drupal 6) over whether or not to port it to Drupal 6 and make Ubercart Stripe use it. If I knew it'd be used in Commerce Stripe at some point, that'd tip the scale in favor of it, and that'd probably be good for everyone (less duplication).
Let me know your thoughts.
Comments
Comment #1
wizonesolutionsRealized the title of this issue looked a bit inane. Clarifying.
Comment #2
iler commentedAt the moment I don't see a reason why I should use it because that project seems to be more or less dead/inactive.
Comment #3
wizonesolutionsMind if I mark it postponed? If all goes well, I will apply for co-maintainership on that project.
An alternative could be for Commerce Stripe to split out some of its functionality into a library/API module. Or maybe to contribute something to a module like Pay and then implement that.
But this module already implements Stripe.js, which to me is the main thing. So, as you to say, keeping what you have makes sense in the current circumstances.
Comment #4
iler commentedIt seems that the Stripe API module development is quite dead so closing this one.