[109 total ]
GetPaid featured by Zea Partners

Thanks to Zea Partners for featuring the GetPaid project on its site!

Check out the article, GetPaid, e-commerce and donations with Plone.

The power of GetPaid: An example job board

GetPaid is a very flexible framework, capable of complex and custom implementations. Building on the generic order management and payment system, lots of things are possible :)

Kapil documented one interesting implementation he did for a ... [More] GetPaid sponsor, Contextual Corp, that shows examples of integrating GetPaid with workflow and custom pricing. The use cases include:

Users pay to submit job board postings. Once it is paid for, it becomes visible to others.
Price of the job depends on (a) the job board where it is being created and (b) the role of the user.

The work is in the GetPaid svn repository as GetPaidJob. Read more about it here: Readme.

Thanks to Kapil for writing this up and thanks to Ken and Contextual for sharing! [Less]

Download tarballs fixed

Sorry for messing up code (nightly script). It seems to be working again thanks to some help from Josh Kidd.

You can find the latest tarball for GetPaid download at http://code.google.com/p/getpaid/downloads/list  . Should work for both ... [More] Plone 2.5 and 3.0.

If you notice any problems, please report them in the issue tracker or to getpaid-dev mailing list.

Thanks! [Less]

Revision 1000!

Not being a developer, I am continuously amazed at the activity that goes into GetPaid, as it is all of you that make the project tick! Since registering the project at Ohloh, I have been even more entertained to watch the stats associated with us. ... [More] For example, I have made a paltry 14 commits to the code base...In total we have 29 contributors to the project. The recent release-related super-star is Maurits van Rees, who has made 45 commits in the last month and give GetPaid its Plone 3.0 compatibility, along with some testing rigor. THANK YOU!!!

Rev 1000 also brings us steps closer to our Red Ochre Release. Kapil hit the 1,000 mark today with the fix to a Five initid bug, which provides us greater database stability. Now we are polishing, and closing issues leading up to the release. Got a second to test? Try the buildout or download the latest tarball.

We are still in the process of reviewing, evaluating, and issue tracking, so if you are poised on your seat, jump in now and get involved! Our mailing list is a great way to reach us, and spark a conversation, learn from others, or just say hello :)

Thanks also to the sponsors of the project's development! You all have made possible establishing the framework for GetPaid and our "social sourcing" model! Thank you!! [Less]

Thank you, Gerry!!!

And our apologies to the planet readers for sending such ugly html :(

But now, it's fixed!

For the information of other quills users...the problem was pointing to the atom
feed, as opposed to the rss feed. Why that matters, I still don't know :)

GetPaid now on Ohloh

Ohloh was created to provide more visibility into the open source development process and to help connect those involved in open source projects. By registering our project on the site, the site downloads and studies the software, determining the ... [More] lines of code and metrics about committers, comments, and more.

And now we know...
Well, the first thing Ohloh tells us, we already know: "Large, active development team" and that it is mostly written in Python. Ok, maybe not too insightful for us yet...but hopefully soon we can see committers on the little Google world map!

At the moment, it has online analyzed getpaid.core, so still waiting for two other elements to get sucked into the process...

Help build awareness
Please check out the listing for GetPaid: http://www.ohloh.net/projects/9356?p=GetPaid

Also, please rate the project! Your comments will help others learn about how cool the project is :)

Also check out
Plone's listing

Plone Collective's listing

Zope 3's listing

Zope's listing [Less]

GetPaid - Now with 3.0 compatibility!

Building on the strong basis of near-Release Candidate code for GetPaid on Plone 2.5, Maurits made some changes to ensure Plone 3.0 compatibility. Now GetPaid is running on 3.0 and 2.5 without a branch!

Summary of work (taken from Maurits's ... [More] notes):

There is a buildout for getpaid on Plone 3.0 https://getpaid.googlecode.com/svn/trunk/getpaid-30.buildout
The getpaid product (PloneGetPaid) and packages (getpaid.core and hurry.workflow) have gotten compatibility fixes on trunk.  So no branches needed for now.
All unit tests pass on 2.5 and 3.0.
There are test failures for Products.PloneGetPaid on both 2.5 and 3.0.
Compared with one week ago, Five was moved from develop-products/Five to parts/five/Five and all keeps working fine.
For a more complete discussion and details on this change, please see the getpaid-dev mailing list thread.

Thanks, Maurits!!! And thanks to all the sprinters that added a lot more tests (especially in PloneGetPaid) to help this happen! [Less]

Naples sprint conclusions

We have been plugging away in Naples and now at the end of our sprint.

We got good progress today, but the list kept growing even as we got things done. We mostly focused on tests, and also got some minor improvements in the system. Today ... [More] included UI, issues, translations, and functional and unit tests. More tests needed, as we didn't know how all the pieces were supposed to function (ie not tested).

Would be great to have people start testing and file issues if you find anything (http://code.google.com/p/getpaid/issues/list ). I suspect a RC tarball will be available late this week or early next week.

Status:

Content catalog work nearly done. One test still failing, so Jean is branching getpaid.core to continue working on it (with Kapil).Functional tests from yesterday and the checkout ones made today are now failing in one place. So we had to do someCart and cart portlet tweaked to show number of total items (as opposed to number of types of items, ie 2 shoes and 4 hats = 6 items vs 2).plonegetpaid.com updated with information about Red Ochre releaseIssue 124 is fixed, though ideally it still needs to write the error to the exception log for referenceA German translation got committed.You can see the two earlier updates here: http://plonegetpaid.com/updates/archive/2007/10/

Things on the list not yet done:

testing the new features manually (duplicate processing protection, mail notification fix)documentation on making a payment processor and development practices/conventionsmigrating more documentation from the wiki to plone.orgdocument dev conventions: update and run tests before commit. capitalizations.

Thanks for your support and following the project. Thanks especially to Jean, John, Ricardo, Florino, Reed, Andreas, Davide, and Guissepe. And especially thanks to Kapil, whose engineering has been a great way to interest and involve more developers, and who has done so much of the product we have today. [Less]

Another update from Naples

Overall, sprinter numbers are way down today as many people head home, but GetPaid sprint is still with seven people. At this point in the day, we are the largest sprinting group...

We are now over 900 commits in the repository (912, at this ... [More] moment)!

Today we discovered some important features that were running without tests, so more testing has been added to the getpaid.core in the order and buyable catalog thanks to Jean Francois. Additionally, we finished off two important issues, thanks to Florian and Ricardo. We also got a new means of protecting the user from duplicate transactions working (we are requesting review and testing of this) thanks to John. Additionally I updated information on plone.org about the product and started updating the home page with release info, including the list of features. We also got a German translation thanks to Andreas. As you can see on the side, we also got a release icon! Thanks to Luke Aune for help on that one.

The order manager is currently being refactored to handle cataloging the products (for use in backups). The checkout wizard is in the process of having functional browser tests implemented. The UI is getting cleaned up some (titles on admin pages, including making additional skinning possible (so elements of PloneGetPaid inherit your site's styles).

ploneconf2007 [Less]

Naples sprint update

Naples Sprint
There's over a hundred people in the Naples Sprint, post Plone Conference. There are lots of topics and projects going on here. GetPaid's goal for this sprint is to get out a release candidate of the Red Ochre release. ... [More]

GetPaid: Day 1

On the first day, we recruited a group of 8 to work on the project. We reviewed our task list and refined it some. Before delving into refactoring, we discovered that our product tests were in need of serious attention. Though work has gone on recently in building in tests in the getpaid.core (Zope 3 library) - in part to make to easier to upgrade to Plone 3.0 - the PloneGetPaid (Plone wrapper product) was desperately needing improvement. Some tests created during the Google sprint were completely outdated and needed removal, and large sections of the product needed tests. This quickly became a priority for considering a release. Reed also cleaned up some of the naming in the product to make it more consistent.

In this process, Jean Francois introduced a product into the buildout for making functional tests called Test Recorder. It allowed me (read "not a developer") to make functional doctests for the product! That was exciting, as I had no idea it could be so easy (ie literally just clicking through the site and adding some comments).

We also updating the Plone version to the latest release in the series (2.5.4) and updated the Five version to 1.4 to allow for browsertesting.

Davide also worked on getting us onto GenericSetup best practices. Things were removed from the install.py and cleaned up for GenericSetup.

Davide also made an example customization policy to ship with the product to demonstrate how to change settings. This complements the Zope 3 approach to customization discussed in documentation and in Martin's talk from the conference.

A small bug in the policy display was fixed.

Liam, sprinting remotely, also checked in several UPS integration files to the branch he is working on, which included tests.

On the internationalization front, Ricardo added a Portuguese (Portugal) translation, Giuseppe updated the Italian translation.

That's about it for day one! Looks better when I actually write it all down :)

Day 2
We are already under way for the day. Unit tests in PloneGetPaid are getting advanced, and the GenericSetup work is completed already!

More later...

ploneconf2007 [Less]