Updated Nov 17, 2007 by cjj.ifpeople
Labels:	sprint

NaplesSprint

Main page for GetPaid Sprint in Naples, Italy

Introduction

The GetPaid project has developed over the last six months and is now approaching its first major release, Red Ochre! The sprint is designed to get us through the last important tasks to get out the door with a stable release candidate. The target Plone version for this release is Plone 2.5.

Read on for more details on NaplesSprintTasks and GetPaid.

Details

About GetPaid

GetPaid is a flexible framework for commerce in Plone. Built entirely on Zope 3 (no content types!), the system provides out-of-the-box useful features while be extensible and flexible for adaptation to your ploning needs!

GetPaid public web site : www.plonegetpaid.com with general info about the project, features, news
GetPaid Developer/Collaboration area: code.google.com/p/getpaid
GetPaid Product area: plone.org/products/getpaid
GetPaid mailing list: groups.google.com/group/getpaid-dev

Scope of Sprint

The sprint details are defined here: NaplesSprintTasks

Preparation

To participate, you should:

Set up a buildout locally, see DevGettingStarted
Get commit rights to the project by sending your google account user info to cjj(at)ifpeople.net or hazmat(at)objectrealms.net (you can also list it on page http://www.openplans.org/projects/plone-conference-2007/getpaid, which will have all users added in batch for the sprint.
Check out the NaplesSprintTasks

Comment by cjj.ifpeople, Oct 14, 2007

Use case:

A common use case which would be nice for the product is the ability to add a "drop down" price selector to a payable form. ie the "price" on a donation may be variable (ie donate: 10, 20, 50, 100...). the field should be able to be activated from the "payable" screen and the site admin should be able to set the values (ie enter in values, separated by a coma)

Observation: do we associate this with some kind of more general variance capability in the system? ie each level could optionally correspond to a different type of donation, as a different price could correspond to different product criteria (ie small, medium, large).

GTD: But basically, I would like a selectable amount for the release. That should be integrated; I mention the flexible part for consideration in architecting, as it is surely to be a priority use case soon.