Update call summary

For your planning:

• Next week we will be ready for alpha testers! (and you should be able to
  complete a checkout)
  
• In two weeks (June 6), we will have a followup call to talk about the
  testing, new development, and planning for Google sprint (same time as
  today's call).
  

Also, don't forget that we are in the process of our Red Ochre release
fundraising! Please check out www.plonegetpaid.com/sponsor to make a
contribution!

Check out the updates below. If you have any questions, please ask!

Cheers,
Chris
--
GetPaid Dev Update Call
May 23, 2007

Attendees: Alex (aclark), Kapil (hazmat), Richard (fifer), Scott (spaleyAE),
Jon (jonstahl), Chris (cjj)

Update:

Develoment is in a rapid pace of change now

Infrastructure over last week

• marking content as "payable" and being able to edit amount
• shopping cart that you can add things to (all viewlet based)
• integration of ore.member for adding fields to member

Next:

• Order management facility (in process), track orders and payment process info
• Pay processor integration (troubles getting authorize.net dev account; Scott and Kapil to connect about that)
• zope 3 workflow engine being used for checkout

By next week should have ability to complete checkout process.
Next week we will need alpha testers!

Then: Support for users to look at orders

Goals:

• Will be able to store all ecommerce data in relational db (to make it

easier for reporting systems tie in). Because of this, the bundle includes
some things for testing that won't be part of the first release.

Q/A:

• Scott asks about donation management (forms to make donation in predetermined amounts for a given program/sub-organization). Would need to set dropdown of prices, ideally, and possibly have open field for price also.
• Other use cases: workflow change on payment will be deferred till Google sprint.
• Delivery through the web use case has several complexities around changing
  security settings on an object and has been deferred for now. 
• SSL use in commerce systems is ubiquitous. Though we can't necessarily
  enforce it in the product, we should explain (or link to doc on plone.org)
  it in master README; perhaps we need to configure SSL in admin screens.
  
• Trust Commerce (payment processor) product published by Tres (link from
  the payment processors page in the wiki).