• Commerce Report

  last modified May 22, 2007 by cjj

Note: This project has a new home

Please see www.plonegetpaid.com for general information and http://code.google.com/p/getpaid/ . The links within the document have NOT been updated to reflect that (except for the ones at the end).

Goals for Sprint

We started the sprint with the following goals:
  • Understand the overall goals of the project
  • Review and refine the user stories, choosing a set for the sprint
  • Find and share available assets for the project (code and otherwise)
  • Document implementation strategies
  • Build a scarecrow of the system
  • Create a plan for continuing progress

What Happened

A group of people[1] sprinted on GetPaid at the BBQ-Sprint to create a way to make payment processing easy in Plone. We came with ideas and enthusiasm and started experimenting to create a new commerce platform for Plone. Kapil led the charge with a late night effort to bust out a framework and leadership for the development team. Nate brought code for the particular case of "premium content" and integration with payflowpro processor. Veda and Chris worked to refactor the user stories many times to have a complete set that described the interface and features of the system. Initial tests were developed and a basic interface created in Plone.

Specifically in regards to the stated goals:
  • We got the group collaborating within the vision of the project.
  • User stories received major work (the main page itself had 40 new versions during the sprint, plus creation of dozens of stories, with details added to provide functionality and user interface specifics). We worked on the case of being able to make any site content "payable", the case of a "donation" form, and "premium membership" (ie a level of site membership that grants access to additional content), as well as the management interface.
  • We benefitted greatly from being around so many people during the sprint. Other sprinters (Calvin, Tres) contributed code assets, and Nate brought a huge piece of code and experience around the case of premium content/membership subscriptions. We also found and began using pay processors from the zwarehouse (zope commerce) tool (see payment processors documentation).
  • The coding of the infrastructure led to some changes in the implementation strategy (for example, dropping ContentFlavors). Instead of ContentFlavors, we will be using the strategy that Plone4Artists used for the calendar view and audio files folder: using a marker interface to add properties to a folder. More on the implementation strategy and "to do" lists can be found on our project page.
  • Scarecrows in the making...see the code for Nate's PremiumMembership, which he was able to get set up enough so others can download and run (with PayFloPro integrated). The basis of GetPaid and PloneGetPaid products are in the collective, though we weren't able to get to the point of actually processing a payment yet.
  • The final day we spent figuring out how to continue our work. We have the following:
The code is available in the Plone Collective: GetPaid and PloneGetPaid

[1] Sprinters included: Kapil, Chris, Nate, Veda, Richard, Edmund, Rob, Carol, and (when not fixing things for BBQSprint) DaveP. Thanks to everyone for their contributions!!!

What's Next

Events: Commerce and Documentation Sprint, June 25-29, 2007 at GooglePlex
Meetings: Followup Skype Meeting, week of Mar 21
Development Tasks: Lots! Please check out the To Do List
Fundraising: We are seeking funds to support the next sprint effort

Where to Find Us

Chat channel: #getpaid (irc.freenode.net)

Public web site: www.plonegetpaid.com

Plone Product Page

Google Code Project area

Contact the project organizer about getting involved

Marketing Site (in development)