release

Just in time for the Plone Conference sprint, our Remote Sprint Goddess, Lucie, finished a release recipe for GetPaid, making it much easier for you to include GetPaid in your own recipe. Please give her your thanks and pat on the back!

More from Lucie:

The recipe is working and uploaded on pypi:
http://pypi.python.org/pypi/getpaid.recipe.release/1.0

You have all the detail on how to use it if you follow the link above. I will probably continue updating it today and make the documentation
prettier. I am currectly using it for one of our sites and seems to work correctly so far.

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)

If you haven't tried it already, check out the latest release from GetPaid and join 600 others!

Also, please note that we will have remote sprints this month! This Friday and the following one and then 2 days (Aug 21-22). Read more or see the sprint information wiki (includes svn refactoring proposal).

A while ago, we created the release branch for GetPaid's second major release, 0.6. However, we didn't officially release it (with packaged code etc), and in the meantime, several fixes and changes came in. So, we are now releasing 2 versions.

0.6.0: This is the originally branched code. Works well and preserves "backwards" compatibility for those using customized GetPaid code.

0.6.1: This is a final release. Includes API refactoring and unicode fixes. May break your customized GetPaid code but not too much :)

Both of these work on Plone 2.5 and 3.0, and apparently on Plone 3.1 also (though we currently aren't providing a buildout for 3.1).

To check out the changelogs, see http://groups.google.com/group/getpaid-changes 

As of earlier today, we had 258 tests passing on 2 versions of Plone (2.5 and 3.0) - yippeee!

So, with much joy, we are moving the trunk to the 0.6 branch for this release.

Next we will tag a 0.6.0 release candidate.

This release got a new directory of documentation as well as a lot of work on new features for shipping, fulfillment and reporting. Have a look at the latest buildout!

Ricardo has been helping us to clean up issues and we are down to 10 listed in the tracker, with several of those actually falling into the "continuous enhancement" category, as opposed to blockers or priority items for this release.

Here's a quick look at progress towards the 0.6 release and an update on the release.

• We are over 620 downloads of the 0.3 release tarball! (plus buildout usage)
• A bug got fixed in the 0.3 buildout branch this past week
• Several bugs got fixed in the trunk, including restored Plone 2.5 compatibility for the buildout, report-related bugs, template changes, and more.  Also, a tool got added to extract email addresses from customer records. Check out the change logs to see more.
  
• We are down to 14 issues tagged for M2 (actually less once we verify closure...). See the issues and grab one to fix or test!
  
• The 0.6 release branch will be made later this week. If you have goodies to include or bugs to fix, please do them asap!
  

Thanks for tuning in. Grab an issue, test the tools, and let us know how it looks so we can make way for 0.6 :)

GetPaid's second major release, this one provides complete fulfillment and shipping functionality as well as several enhancements to the base product, such as address book, warehouse and inventory management, reports, and UPS shipping calculator integration. This version supports Plone 2.5 and Plone 3.0. Hopefully it will also get the Discount product included as well.

Where are we today?

Lots of changes have been going on (see the older blog posts for a summary) and great new features, especially around fulfillment and shipping.  Basically, to the solid framework established in the Red Ochre release (0.3), we have built out fulfillment functionality quite extensively.

Ohloh reports us as having over 10,000 lines of code now!

What next?

Next week, probably, we will make our release branch of the code. There will be some complexity around making tarballs that work, so expect them a while later.

We still have several issues that are targeted at this release.

We also need a catchy code name for this release :)

One thing to note...this will be our last release supporting Plone 2.5, unless someone new steps up to do the maintenance on that part of the code. The future release (0.9) will probably be lots of cleaning and UI improvements, plus the new features people think up to include :)

Haven't checkout out the release candidate yet? Get it here. If you prefer buildout, start here.

A look at out code

Ohloh finally updated our code, given us a better idea where we are and how people have participated. By the numbers, we have:

• 7,627 Lines of Code (not counting the pesky white spaces) representing about 2 person years of work!

Ohloh likes to assign a value to that (and gives you a calculator to do it yourself), and claims that our product is worth about $92,000.

The ability to leverage investments in the code base to generate additional community participation is another awesome aspect of the social sourcing model. We kickstarted something that is becoming more self-organizing, self-sustaining. Read more on our report at Ohloh.

Taking a look at our top contributors (by number of checkins), our top 10 are:

• Kapil, with 205 commits!
  
• Maurits
• Eric Steele
• JPG
• Javier Mansilla
• John Lenton
• Brian Gershon
• Ricardo Alves
• Lucie Lejard
  
• Fabio Corneti

Release Code Prep

Code preparation continues and now we have a tagged release for the 0.3. Those wishing to point their buildouts to the stable tag, can now do so.

Still to do is: update the anonymous buildout, finalize the duplicate checkout protection work, update declined payment handling in authnet.

Latest Changes

Since the tag got made after some fixes went into the product, I figured I would make a quick update on the changelog:

• Dutch and French translations were updated
• Testing processor was improved to include the "LAST_FOUR" handling, as in the other processors, for better testing.
  
• Cart item handling was improved so that when a quantity becomes zero, the item is removed from the cart. Tests around this were also included.
  

At last we have reduced the issues in the tracker, given the code some polish, fixed typos and added some improvements. Red Ochre has gone a ways beyond what we originally set out to do...providing additional features like Plone 3.0 compatibility, optional anonymous checkout, 2 additional payment processors, lots of languages and i18n work, and some example implementations. Supporting all these extra features has taken extra effort to get the release polished, but also been a great way to involve a much broader community of developers and integrators.

We made it to the release candidate thanks to some dedicated effort from Maurits over this past week to squash some remaining bugs and clean up the product. Then, Lucie swooped in at the last minute to take care of the remainder of issues yesterday! Wow, great work you all!! Thanks for helping get this ready!

Update on status:

• All tests are passing!
  
• Release Candidate tarball uploaded: Download it now! (484kb)
  
• Issue tracker: main thing left to do is prepare the code base (tags etc) for the release
  
• Our Ohloh reports seem to be broken, so I can't get new updates from there (request for updating made today). 
• There are a great many things to work on going forward, which have been organized in a page of proposals here. 
• If you find any issues with the current Release Candidate, please report them in the issue tracker and share any ideas, news, etc on our mailing list.
  

Latest changes in product:

• Put back on the last checkout page a check to see if the person is anonymous, and if the person is, we don't give a link to the order
• Added a check on the order view page to allow only manager and owner of the order to see the order, refs #157
  

And that's a wrap for today!

Please use the product and let us know how it goes! If you launch a site with GetPaid, please contact us so we can advertise it on our Sites that Use GetPaid page.

Thanks so much to  all those who helped make this possible - all our developers and supporters. Special thanks to our sponsors, who have contributed so much support to helping this become a reality:

ObjectRealms | ifPeople | One/Northwest | Contextual Corporation | Trees for Life | Totsie.com