conference

Well, just in time production (thanks to perrito and dunny), I had the various "howto's" I needed to explain how to use GetPaid for the talk.

In the talk, I introduce GetPaid and its core features, and then show how it can be used to satisfy various use cases, both with the out-of-the-box components as well as with some customization.

The audience was a decent size (especially considering I was up against Joel Burton at same time slot!),

Download slides here.

http://plonegetpaid.com/updates/files/getpaid-presentation-ploneconf-2008.pdf

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)

GetPaid Presentation at Plone Conf 2008

GetPaid will be present at the upcoming Plone Conference session "Ecommerce in Plone: Surveying the state of the art". If you are interested in learning what you can do with GetPaid, how the Sites Using GetPaid were made, and what you can do with GetPaid, please join us on Wednesday, October 8, 2008 (Day 1) at 2:30pm in the Polaris room for this presentation!

Also, don't forget that GetPaid will be present at the Plone Conference Sprint! Sign up to participate here. A schedule of tasks is coming in a week.

PloneFormGen Integration Gets Refactoring

You may have read about the integration between GetPaid and PloneFormGen that happened a couple months ago. Recently, it got some refactoring to make it clearer, thanks to perrito666 (aka Horacio Duran). He also implemented the ability for it to accept multiple "adapters" (in the PFG sense, not the Zope 3 sense). What does that mean? Now you can seamlessly use PloneFormGen with GetPaid and add in your Salesforce.com integration adapters (or whatever other PFG adapters you may have)!

The latest updates are available at the mercurial repo available here: http://code.except.com.ar/hg/hgwebdir.cgi/getpaid.formgen

Remote Sprints Continue to Further GetPaid

Lucie Lejard of Six Feet Up is the Goddess of Remote Sprints in GetPaid throughout the summer. After a vacation in France, she returned to wrap up work on improving ease of integrating GetPaid. She has been on a quest for the holy grail of GetPaid deployments - the recipe.

And behold! With the guidance of Clayton (claytron) she is unleashing the power of the recipe! The recipe grabs the eggs, grabs the vendor products, and makes GetPaid a part of your buildout! It is so close to finished.

The CIA bot dumped a long list of checkin updates into #getpaid yesterday afternoon, and remarkably we passed our 2000th revision! In that swirl of code, paypal workings got fixed thanks to duffyd, some error controls and bug fixes to the getpaid.report component were added (and perrito666 hit the 2000 milestone!), googlecheckout got updated by dunny, and more. See changelog.

Thanks to all who have been working on the project!

Other noteables from GetPaid:

• GetPaid 0.6.1 tarball now has 895 downloads and has surpassed the 0.3 downloads total!

For those joining the Plone Symposium in New Orleans this week, I will be giving a talk on "Social Sourcing" tomorrow (Wed) at 3pm.

Social sourcing is the participative organizing model with an entrepreneurial backbone, an established role for non-developers, and an ongoing process to make open source software projects sustainable that we used to organize the GetPaid project. Check out the notes and video from the social sourcing talk in Naples. This talk should include some updates (including from the questions in Naples and taking into account the Plone Strategic Planning Summit).

Thanks to Maurits for summarizing the talk on his blog here.

To download the presentation by John Lenton, please click here.

Social Sourcing Talk

The GetPaid project was organized differently than your average free software project. For one, we raised money for it. Additionally, we had an integrated design process that involved non-developers from the beginning. In the talk, I introduce the social sourcing model we used and why this was an important process for making the best product possible. I explained the process by telling the GetPaid story.  *New* Watch the video at plone.tv

Basic outline of the process:

Definition: An organizing approach that gets diverse stakeholders to participate to the software making process.

Outline of Social Sourcing, v1.0 Alpha ;)

• Study the market (benchmark)
• Put together a compelling plan
• Recruit the right people
• Engage a wide base in refining requirements
• Ask for money
• Celebrate successes
• Sustain it: fun, organization, motivation
• Regroup, review, and restart...

It's exciting to be moving towards the end of this process in GetPaid. After the conference, we go into a Release Candidate sprint...but we are definitely eyeing the review, regroup, and restart step!

You can get the full presentation here

The presentation was recorded and should be available at plone.org within about a month. Note also though that some sessions are being streamed live at http://ploneconf.comlounge.tv/
Technorati Profile

Questions for Plone

Part of my presentation was to ask questions about the processes for organizing and desiging Plone, in light of the social sourcing model. In particular, how can Plone be more inclusive to non-developers in defining it's directions and features? Perhaps Plone could benefit from process improvements that would:

• Clarify direction and identity
• Provide more inclusive design process
• Improve the overall product
• Strengthen Plone community
  

In particular: how is the vision for the future defined? Is that a transparent and open process? Where is it documented? Also, why is there nothing between the vision and a PLIP that would enable non-developers to participate? (This last one came out of my frustration at not being able to create a PLIP to introduce some search UI improvements we had made to Plone core, since, as per policy on plone.org, only core developers can make PLIPs).

Just as I was getting into this, "someone who knows" informed us of imminent announcements that will address this issue. I suppose that means that at the Plone Foundation meeting tonight! So look for some more news :)

Questions for GetPaid

Jon Stahl, our NGO liason and ongoing project supporter, made a great question: what does GetPaid need to keep the process going? Not something I had prepared for, so I made a few notes here in addition to what I responded:

• Deployments! We need more deployments, and in particular, practical applications of GetPaid that lead to more options being available in the product (ie for payment processors, workflows, configurations, interfaces, etc).
• More organizers! The project is likely to have teams oriented around specific extensions to the product (membership, event registration, advanced store functionality). The organizers would basically focus on new rounds of social sourced development.
• More committed developers! Though for the first release, we relied on Kapil's work establishing GetPaid as a framework. Going forward, we need more people involved as developers to architecture as well as features.
• UI love! Usability on the system can be greatly improved and we welcome contributions to this.
• Screencasts!...for documentation and marketing.
• Organizing new round of features: questions from the audience helped get my brain off the narrow focus on getting a release to see the next round of features that need to be considered. I will be writing up some notes on this work.

Well, that's a good first start, I think, but will definitely continue to consider what we need (especially after we get to reflect on a release).

Kapil Thangavelu, lead architect of GetPaid and cofounder of ObjectRealms, will give a talk entitled "GetPaid - Making Money with Plone". The talk will provide developers a glimpse of how Zope 3 was used to create the GetPaid product and how it can be used and extended to create custom commerce solutions in Plone.

Chris Johnson, organizer of GetPaid and cofounder of ifPeople, will give a talk entitled "The story of GetPaid and a 'social source' process to create new opportunities with Plone". This talk builds on a talk delivered at the Regional Free Software Conference in Cordoba, Argentina that outlines how the project was organized using an entrepreneurial, participative model.

We are glad that the conference organizers chose GetPaid as a product to spread within the Plone community at the upcoming conference!

Find more on the conference

See the complete list of talks.