Entries For: April 2007

The next sprint for the GetPaid project will be at the GooglePlex, June 25-29. This sprint, called "doccom" for its combination of sprinting on (Plone 3.0) documentation and ecommerce, should be a lot of fun. We are hoping to have about 15 or so people, and are seeking those interested, committed, and ready to contribute. Please check out:
http://www.openplans.org/projects/doc-and-e-commerce-sprint for more info. If you are considering attending, please note that on the page of interested attendees.

A tentative agenda for GetPaid includes:

• New release of PloneGetPaid, that further builds out the framework that will be in place by then
• Payment processors: additional inclusion of payment processors (and taking advantage of the group to get everyone's favorite done!).
• Special use cases: probably the subscription/membership case, but others being considered (especially with the influence of sponsors;).

Comments on this are welcome!!

If you are interested in supporting this sprint, please contact us. We are seeking to provide at least some supporting funds to all sprinters, with amounts varying based on level of commitment/contribution to the project.

Hear Richard Amerman describe the recent surge of activity bringing payment processing to Plone.  PloneGetPaid is a new project with a lot of momentum that Richard has been involved with.  Hear what the project has accomplished so far and where it's headed.

On April 2, Kapil writes:

"I've been working on getting together a member framework that can be used for getpaid and others. its main purpose is just being able to easily add fields to users for registration, administration, and editing via attaching zope3 schemas to members with ui's being automatically generated by formlib, and a management ui for selecting which schemas are in use for a site. its pretty much complete, i'm about to start integrating it into the getpaid bundle. its very lightweight, no content types, skins (yet?), tools, or catalogs, etc. as compared to remember on a feature level, it doesn't do or want to do workflow, or cataloging of members. i've got a prototype for storing values back to a relational database efficiently, and will work on an ldap one over the next few days. in terms of getpaid integration, i'm going to add billing, shipping address...

"in terms of the integration with plone, the main things to be done on it are additional user testing, and management integration for editing a user with the additional properties present (already there for reads).

"its available from here, along with installation instructions
https://svn.objectrealms.net/svn/public/ore.member/trunk  "

Please find the full GetPaid sprint report from BBQSprint (put on by TriZPUG).