Google

It's great to see we are almost at 300 downloads for the GetPaid RC1! So far just one small bug in that file so far so expect a final shortly. Already, new work has started on the trunk and in some of the branches, so I wanted to give a quick update about two exciting pieces.

Google Checkout Integration

Thanks to Michael Dunstan, a simple integration of Google Checkout now exists for GetPaid! That gets your order straight into Google Checkout so you can use their infrastructure for fulfillment and order management. See screenshot of order management interface.

This is good news for US non-profit organizations, as Google is offering GoogleCheckout for free (at least through end of this year). That means no processing fees, monthly fees etc to accept donations online!

Still pending is a smooth buildout experience to get the feature, but if you are interested, check here to check out the product (especially README!).

More sophisticated integration (ie getting messages back to GetPaid from Google Checkout) requires an SSL certificate and secure communications with the Plone site.

UPS Shipping Integration

Liam started off UPS integration and Kapil has refactored it, including unit tests and more. Now shipping costs can be looked up in real time from your GetPaid site. The work is currently happening in the UPS branch of the code, but will be rolled into the trunk and available tomorrow.

Some other goodies in the work include persistent shopping cart, ability to print order, and more!

Interface with GetPaid-development mailing list at http://www.nabble.com/GetPaid-for-Plone---Dev-f27137.html

DocComm sprint got underway at Google's headquarters in Mountain View, CA yesterday. We had a great start with a solid team of a dozen people.

To catch up on progress, check out:

• Sprint objectives, including tasks
  
• Sprint updates (who is doing what, daily progress notes)
• Get the source latest version!
• If you already have it, please update your code ("svn up") and reinstall the product.

First, if you are planning to attend, make sure your name is here:
http://www.openplans.org/projects/doc-and-e-commerce-sprint/interested-attendees
and that you have made your lodging plans clear here:
http://www.openplans.org/projects/doc-and-e-commerce-sprint/roommate

Second, make sure you get there! If you are traveling to the Bay area, act fast for tickets (AirTran has a sale through Tuesday; I just picked up tickets on Delta for good price). You can check out the sprint logistics page here: http://www.openplans.org/projects/doc-and-e-commerce-sprint/logistics

We have 10 rooms in a hotel for the entire sprint and are arranging for vans to transport us to Google. The organizers' fundraising
efforts have helped to cover hotel (shared room) and local transport costs, but you are responsible for getting there and for daily meals,
incidentals, etc.

If you know of any other potential sponsors, PLEASE let us know ASAP! We would love more support for this great opportunity to advance both commerce and documentation for Plone!

Send potential sponsors or contributors to http://plone.org/events/sprints/doc-ecommerce/

There is an important Plone sprint coming up and the community is seeking sponsors (great perks! [1]) and sprinters (in person and remote) for the "doccom" sprint, June 25-29. The site will be at Google's headquarters in California. There are two topics:

• Documentation (to ensure that Plone 3.0 is released with full documentation), and
  
• Commerce, to achieve a new version of the product GetPaid that makes payment processing and commerce simple and flexible in Plone. [2]
  

Regarding documentation, this is something that benefits everyone! As you know, Plone has been changing very fast, and the pending release of Plone 3.0 represents a radical shift in the technology and how people will develop for it. Documentation is needed now more than ever. Please consider supporting the sprint either financially [3] or with your participation.

For more on the sprint, please check out: http://plone.org/events/sprints/doc-ecommerce

You can see a list of interested attendees (and sign up!) at http://www.openplans.org/projects/doc-and-e-commerce-sprint/interested-attendees

Hope to see you online or at Googleplex!

[1] Sponsor levels include free training! PloneBootCamps and the intro trainings from 7TechNorthwest. See
http://plone.org/events/sprints/doc-ecommerce for the full breakdown.
[2] Plone commerce has a long and painful history, which we are trying to change with a product called GetPaid (and PloneGetPaid), which leverages Zope3 technologies and will be useful in Plone 2.5. This product was begun at the BBQSprint and has its first release scheduled for June 1, and second release after the doccom sprint. 
[3] Financial support makes sure the great sprinters have food, shelter, and fun during the time they spend helping make the Plone community stronger (and btw, they are donating their time...).

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.