>>>>> "Asko" == Asko Soukka <asko.sou...@jyu.fi> writes:
Asko> - As far as I've understood, there was some progress for
Asko> Brandon's branches during the PyCon sprint, but eventually,
Asko> they were not merged into the trunk? Is that correct?
yes
Asko> - I've read that Mikko's multipaymentprocessor-branches have
Asko> been upgraded to Plone4. It also seems that they are kept
Asko> up-to-date with the current trunk. Is that correct?
yes, i've also committed a buildout config to setup a plone4 environment
to use them.
Asko> - Yesterday, David merged and released
Asko> GetPaidForPlone4-branches (Great thanks for you all, who did
Asko> the hard work!), but the releases didn't seem to include any
Asko> features from either Brandon's or Mikko's branches? Is that
Asko> correct?
Yes, I think i was a "conservative" choice made by David to publish the
work already done while we come to a decision on the subject. I will
continue to backport new features from trunk to
"GetPaidForPlone4-multipaymentprocessors" branches until then.
Asko> Since both Brandon's and Mikko's branches affect how custom
Asko> paymentprocessors (and/or their wizard support) should be
Asko> implemented/upgraded, decisions regarding the future
Asko> directions would be appreciated.
Thanks fro opening (or re-opening) the discussion on this.
I agree, personally i've updated Mikko's branches beacuse i seemed the
"simplest" and more clean solution. The differences between the trunk
and multiplepaymentprocessors branches are some "insertion points" into
checkout and configuration and a registry of the payments methods.
What i failed to grasp of Brandon's branches is the reason for the
differentiation between onsite and offsite payment processors and why
there can be only one of the former active per site. If someone with
more experience of the two different solution can point out what's on
Brandon's code that is missing on Mikko's, i will volunteer on merging
the two.
Also i would like to see some bugreports cleanup. Many seems obsolete,
many are so vague that it's impossible to verify if the trunk is still
affected. Sometimes they are used to discuss stuff that goes far beyond
the subject of the bug but it's nearly impossible to track bugs recently
changed as the addition of comments doesn't seem to update the
"changed" field on bug. Can anyone with more knowledge about the project
or that is in charge of any of them update their status?
Asko> And after that there's a nice awaiting Sales Tax
Asko> implementation (for us Europeans) in Mikko's
Asko> "miohtama-taxes"-branches, but those again are based on
Asko> Brandon's branches... :)
never looked at it, my shop will sell stuff with clients that that don't
need to know anything about vat and other taxes.
Asko> Finally, I'd be personally interested to enhance the current
Asko> Currency Options with "currency_formatting" option (should the
Asko> currency symbol be rendered before or after the currency
Asko> value) from hannesc's branch (see:
Asko>
http://groups.google.com/group/getpaid-dev/browse_thread/thread/1956c8017245532a).
Or
Asko> does someone oppose it?
not me
--
GetPaid for Plone: http://www.plonegetpaid.com (overview info) |
http://code.google.com/p/getpaid (code and issue tracker)
You received this message because you are subscribed to the Google Groups
"getpaid-dev" group.
To post to this group, send email to getpaid-dev@googlegroups.com
To unsubscribe from this group, send email to
getpaid-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/getpaid-dev?hl=en?hl=en
To unsubscribe, reply using "remove me" as the subject.
