i18n

As typical, a slightly slow start to the sprint post-very-fun-last-night-of-conference. But by midday, we had momentum (yeah...it took us 2 hours to get buildouts running due to either connectivity issues or everyone crushing the distribution points for the plone code). We had a strong showing from the Abstract guys, who dove in to fixing stuff right away! We also had Adam, a long-time irc channel companion and local and Ken Wasetis, one of the sponsors of the first release of GetPaid.

Here's a quick update of what we did on Day 1:

We all got buildouts set up (except me) - 3 ways were tried (2 worked): trunk, recipe, and meteoroid branch (later didn't work yet).
Fixed the 1 failing test in Plone 3.1
Test and verify GetPaid recipe works in Plone 3.1(.6) site
getpaid.core i18n files updated; Italian translation finished; Dutch done

Testing bugs/issues in tracker: started with 73 issues, we will probably be several less by the end of the sprint!
  A critcal bug ended up not being reproducable: 209
  Testing processor gets default value (improves usability)
  Strategized and dove into a high priority issue to provide more order info: 116 
  Started issue 214
  Starting creating Checkout Options as part of issue 184

Sunday (tomorrow):

- Update pay processor order.py to get order id back from processor ==> authnet
- pay processor integration sprint (work on 2 or 3 potential processors)
- documentation update

Surveying the State of the Art in Plone Ecommerce

I intended my talk for the conference to be a good learning experience that pushed my own understanding of GetPaid. As I am not a developer, I certainly don't know how to do a lot of things that people do with GetPaid. But, as GetPaid was my motive for actually learning how to use svn and making my first checkin, I figure I should be able to figure some of this stuff out using the available documentation and my knowledge of GetPaid. So as part of my talk, which will be walking through what you can do with GetPaid: out of the box, with community addons and with basic customziations, I have been asking a lot of questions! This has motivated some new documentation being produced that will continue to support new community members who are finding GetPaid. Also, I found a few bugs that are now in our tracker.

Some of the things I will show:

• Managing inventory with GetPaid
• One-page checkout (with PloneFormGen integration)
• Making a store

• Pay-to-publish content (working that integrates a payment step for job listings, ads, applications, etc)
• Making your own content type buyable (programmatically)
• Showing GetPaid information on your templates

Sprint Preparation and Plans

Distribution

• Eggify components and get to pypi (everything in externals already there)
• getpaid.warehouse
• getpaid.report
• Finish GetPaid? recipe; Document usage
• Buildouts:
• Test and finish reorganization (base, 30, 25, currently on meteoroid-branch) and document buildouts (how to add getpaid)
• Document and use in DevGettingStarted
• Merge branch or copy files on existing buildout
• update anonymous buildout (diff svn externals and cfg file). Fairly easy, as it was last updated in August.

Bugs & Issues

• fix issues
• Issue #209
•  Issue #202 
• Issue #117
• Improve paypal processor: make multi-item checkout possible, make/fix admin screen for processor

i18n

• update translations
• Spanish: in progress (FranGM, Wu, cjj)
• French (very close to done)
• German
• Italian
• Chinese
• Dutch

Testing

• add greater test coverage:
• getpaid.report

Documentation

• gather/improve/update/add documentation (list specific here)
• Review and improve content type integration for devs doc
• How to show price (or other GetPaid? properties) on a template in your site
• How to wire payment process to a workflow state change (ie create a piece of content, but pay before it is published)
• How to get and use getpaid.formgen
• How to customize the checkout process (including using available slots, ie for comments)
• Enabling components in buildouts
• Using the new buildouts
• Using the recipe
• Review mailing list and document errors messages (on plone.org doc collection) and how to fix them
• How to get and use getpaid.salesforce
• ReorganizeIssueTracker (in progress; cjj, gabrielle)

Release prep

• 0.7.0 release (would support 2.5 and 3 together)
• update changelog on plone.org/products/getpaid
• branch code
• make a branch to separate future 2.5 and 3 support (dennis)

Just recently we have had two translations added to the product - French (from Lucie and Maurits) and now Chinese (from Adam Tang)!

That makes our list for languages shipping with the project: Spanish, Italian, Portuguese, Dutch, German, French, Chinese (and English)

Thanks for making things even better! We are inching towards the release here and minor issues getting wrapped up!!  

<cheerleader>Whadda we need? Deployments! Whendaweneed 'em? Now! </cheerleader>

The great thing about GetPaid reaching a stable state is that it is getting used! And that is creating lots of great effects:

• Bugs are getting found and fixed (thanks to Javimansilla, Lucielejard!)
• Extensions of the product are being created to give GetPaid new functionality
• Improvements are being integrated that make the core better.

This week we had great news about some of this additions, including:

• News of a French translation in the works by Lucie Lejard!
• The creation of a discounts extension by Lucie at Six Feet Up. Six Feet Up announced the project this week and the code is already in the public repository, though still in the works. Eventually it will be packaged as an extension for GetPaid.
  
• The email notifications system got improved once folks started finding out about using (and overriding it). Now it is easier to use your own templates for email notifications.
  
• New payment processor: in the works is integration with Paymentech, the Chase bank processor. Look out for getpaid.paymentech soon too...
  
• Additions of new documentation to the GetPaid documentation on plone.org

GetPaid has a number of outstanding issues at the moment in the leadup to our Red Ochre release (0.3, see issues here).

A few updates (from Argentina):

• Issues are being added and eliminated. Please grab a bug or issue and help us hit the release!
• The product README now contains information on getting started with the project (and was completely updated)
• The dev site has been updated with the latest code as of today, which includes a fix of the payment processor (authorize.net)
• A new tarball of products is available (from Aug 15)
• Internationalization of the product is very advanced, and now includes a Spanish and Italian translation. Work pending on the zope-specific product (getpaid.core). Thanks to i18n Sprint participants at the Jornadas de Software Libre in Cordoba, Argentina!
• Kapil is currently in Argentina working with a group of FairSource developers to work towards the release. 
• ore.member (a simple product for customizing membership properties) is being removed from the product before release
• Documentation development is underway - if you can contribute, please see the outline here .
  

Call for testing reminder!

ThePlone sprint will happen on i18n of GetPaid for Plone on August 9, 2007. It will include training on internationlization and then a day of collaborative work on GetPaid internationalization. Other interesting during the conference Plone training (a site admin/content management one AND an intermediary developer training!) and many Zope/Plone/Python talks.

Call for testing reminder!