Hi all I've been following getpaid for a while, but I have not had a project involving e-commerce until now. I'm currently fixing some bugs in getpaid related to internationalization, creating a new danish payment processor, and have a translation to danish ready. I would really like to get some of the current issues in getpaid fixed soon, and are willing to put in some time.
I might just commit some of the insignificant fixes to trunk, and post for feedback on this list for the larger ones. I'm freelancing for Headnet (Copenhagen, Denmark), and we have quite a few plone 4 projects involving getpaid starting up, so its good news with the beginning of the getpaid on plone 4 efforts. I'm willing to put in a lot of effort to get this going. I contributed a while back to PloneMall. And its good to see that some of the PloneMall architectural problems are fixed in getpaid. My plone experience goes back to 2.0.5. A) What are the thoughts about ditching at least plone 2.5 compatibility in this process? The code could be cleaned up and streamlined a bit while making getpaid plone 4 compatible. B) David Glick wrote in another thread: "Okay, I think I've sorted out the issues with the refactored getpaid development buildout now -- bin/buildout -c 334.cfg should now work. My solution was to make it check out all of the eggs that getpaid requires forks of (zc.resourcelibrary, zc.table, yoma.batching, and hurry.workflow) -- otherwise the original (and now incompatible) versions get grabbed from PyPI. Incidentally, this is kind of a mess. I'd love to see us take the eggs that we've forked and rename them to getpaid.* so that we can release them to PyPI without colliding with the original packages." I would like to see no forks of other (non-getpaid specific) eggs. Lets use the standard releases from pypi or we have chaos. Additional features needed should be incorporated into those packages - or we should make our own packages, building on top of (and still using) those third party packages. Like plone.app.z3cform building on top of z3c.form, and so on. C) What's the status of merging Brandons and Mikkos branches? I'll look into the plone4 work already committed during this week. Do we have some sort of roadmap with version numbers for the next releases of getpaid? How do the (if any) GetPaid version correspond to getpaid.core / Products.PloneGetPaid? For instance, plone 4 support from version xx, and plone 2.5 compatibility until yy. Regards, Sune B. Woeller -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en?hl=en
