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.
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!),
http://plonegetpaid.com/updates/files/getpaid-presentation-ploneconf-2008.pdf
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:
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.
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
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 Sites Using GetPaid page had become a nightmare to maintain with kupu and I simply couldn't edit it without things blowing up. So, I am really excited to announce that the page is now something organized, lovely, and scalable :D.
I went for my inclination to use structured data and some nice features to clean that mess up and used the ATSuccessStory product (what is also used for sponsors on the site...this is a version slightly customized by the product author, frapell).
Soo.....check out the all new, improved and attractive http://plonegetpaid.com/why/sites-using-getpaid/
I added 4 new sites that hadn't been there previously:
You will also notice that there is a portlet with rotating site features on plonegetpaid.com to highlight the sites as you navigate around.
We have some really great example sites out there, so please have a look!
If you have a site to add - please let me know - I am now all caught up with all the sites I know of. Also, if you want to send changes to any info there, please let me know.
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:
(12:04:11 AM) dixond: effectively what I've built is a way to turn a Plone site with GetPaid into an advertising channel, where people can pay to publish their content for a fixed time. The basic framework and concept can be extended then to other things also.
Stepping down from dixond's elloquent marketing-speak, the use case is something like this: A user needs some credit to make their content public in some way (ie "for a week" or by virtue of a group membership).
OK, the nuts and bolts:
1) ICreditRegistry for storing the credits (can obviously be in RDBMS but my trivial implementation uses ZODB and BTrees)
2) TickingMachine subscriber that knows about ICreditPublishedContent and applies some rules around send reminder emails, depublish, etc
3) Archetypes schema extender profile for ICreditPublishedContent to track stuff like 'weeks remaining published'
4) Various portlets to allow purchasing credit and using that credit to publish ICreditPublishedContent
5) A few basic content types to represent the credit being purchased
Basically, what I've been building is a way to buy 'non-things' much like the notion of the 'donatable' type and to keep track of them and then use them for controlling access to arbitrary actions later. At present it works great, I'm spending most of my time 'generic-ifying' it so that it can be re-used elsewhere and isn't tied too closely to my specific use-case. Also on the list are other credit types like 'group membership' etc. Once I've generic-ified it enough this should be 'easy'.
Currently, three packages: getpaid.creditpublish, getpaid.creditregistry, getpaid.purchasablecredit
Future extensions could also allow content to be accessed by using credits, if a payment processor is implemented which consumes credits.
What are others saying: "that's a really needed usecase of getpaid - lots of people will be hopping happy :)" -duffyd on #getpaid
So, it did land in the repo - in sandbox: https://getpaid.googlecode.com/svn/sandbox/dixond/
Here is the full post dixond made (can be found in mailing list archive also):
I have been busy implementing a slightly different sort of use-case on
top of GetPaid for the last couple of weeks. The scenario is based
around a site where the site owner would like to charge the general
public to run, eg, user-submitted advertisements for a fixed period of
time. Think 'classified ads' or similar. The user is put in complete
control of publishing their content according to a policy (eg, the
first one implemented is for week-by-week publishing). The user pays
for a 'week' of credit, and can then consume those in publishing their
own content for that period of time. Also on the cards is
month-by-month group membership, which could then give them access to
special roles etc for 'all you can eat publishing'.
The overall framework is a relatively big, semi-independent
component/app in its own right, but the payment portion of it is tied
quite closely to GetPaid, and the rest seems to me to tie in nicely to
GetPaid as a whole, so I've attached it in name and spirit to GetPaid
for the moment ;)
There are three pieces that I have uploaded code for currently, all
of them relatively divorced from the nitty-gritty implementation
details and specifics of the use-case that birthed them:
Last week, we peered into the top secret skunkworks of dixond and well,
let the cat out of the bag about an exciting new extension coming to
GetPaid any day now :) Ok, so maybe skunkworks is a bit of
exageration...but I deal with developers who are hard to get to talk!
It is often classified (in heads) until checked in...thanks to a
shocking burst of verbosity, we got this insight:
(12:04:11 AM) dixond:
effectively what I've built is a way to turn a Plone site with GetPaid
into an advertising channel, where people can pay to publish their
content for a fixed time. The basic framework and concept can be
extended then to other things also.
Stepping down from dixond's elloquent marketing-speak, the use
case is something like this: A user needs some credit to make their
content public in some way (ie "for a week" or by virtue of a group
membership).
OK, the nuts and bolts:
1) ICreditRegistry for storing the credits (can obviously be in RDBMS but my trivial implementation uses ZODB and BTrees)
2)
TickingMachine subscriber that knows about ICreditPublishedContent and
applies some rules around send reminder emails, depublish, etc
3) Archetypes schema extender profile for ICreditPublishedContent to track stuff like 'weeks remaining published'
4) Various portlets to allow purchasing credit and using that credit to publish ICreditPublishedContent
5) A few basic content types to represent the credit being purchased
Basically,
what I've been building is a way to buy 'non-things' much like the
notion of the 'donatable' type and to keep track of them and then use
them for controlling access to arbitrary actions later. At present it
works great, I'm spending most of my time 'generic-ifying' it so that
it can be re-used elsewhere and isn't tied too closely to my specific
use-case. Also on the list are other credit types like 'group
membership' etc. Once I've generic-ified it enough this should be
'easy'.
Currently, three packages: getpaid.creditpublish, getpaid.creditregistry, getpaid.purchasablecredit
Future
extensions could also allow content to be accessed by using credits, if
a payment processor is implemented which consumes credits.
What
are others saying: "that's a really needed usecase of getpaid - lots of
people will be hopping happy :)" -duffyd on #getpaid
At last the Ohloh report is updated! So here is the update:
We are building on the momentum of last week's 2 day sprint and the
previous Friday sprints in getting GetPaid super-charged. An amazing
amount of cleanup, organizing and catchup is going on in the community
right now - it is great to see (and Fridays are regular GetPaid sprint
days now!).
We want to continue this momentum and engage new folks - while
taking advantage of a great change to work together in person - at the
Plone Conference in DC in October. We hope you will join us! If you are
interested, please sing up at http://www.openplans.org/projects/plone-conference-2008-dc/getpaid
we are down to 62 issues open in tracker, about half of which have hte new metadata applied...and up to 738 downloads of getpaid tarball
WARNING: PloneGetPaid code has MOVED. It was eggified...
As a reminder, GetPaid is ZPL license and we hope that contributors will keep consistency in their packages.
Here is a partial list of updates from our standup meeting just now...includes people who were there and what we could remember :)
Dennis: credits for store (ie user can buy credits and then shop with those)
Lucie: I will continue uploading the eggs to pypi to have the recipe done.This morning is getting humming in #getpaid with activity as our 2-day
remote sprint starts. Here's a checklist so you can find out how to
pitch in:
[ ] Morning stimulant (plenty of yerba mate here...CHECK!)
[ ] Fresh checkout of GetPaid: https://getpaid.googlecode.com/svn/getpaid.buildout/trunk getpaid.buildout
[ ] Clothing (optional...it's a remote sprint afterall ;)
[ ] You in #getpaid - needed!
So far this morning, we have:
- Fairwinds and Lucie: working on pypi uploads
- Dennis: working on Paypal IPN
- Me: updated ohloh, now updating Spanish translation
Later today I will be working with Gabrielle on the issue tracker.
Come on by and help out! Plenty to do.
Horacio Francisco Sebastián Durán Barrionuevo (aka perrito666) will give a talk on the quality and simplicity of GetPaid as a complete e-commerce solution at the 8th Jornadas Regionales de Software Libre (Regional Free Software Conference) in Buenos Aires, Argentina on August 21, 2008.
Just wanted to remind you that we are sprinting in #getpaid tomorrow (Thurs) and Friday!
As
opposed to the little Friday-afternoon-with-GetPaid-and-a-beer kinda
sprints ;), this is time to get down and dirty and get some serious
stuff done! (/me has even managed to keep the calendar almost free!)
Lucie
is our awesome Sprint Goddess for the sprint and can help folks looking
to get involved. We have some great work already in motion from the
last sprints (see updates in this blog). We are headed towards the 0.7
release, so there is a good bit of work to go, so we hope you will help
us in making the buildout easier, squashing bugs, adding/editing
documentation, adding some polish and features, and getting ready for
the next version of GetPaid! More info at http://code.google.com/p/getpaid/wiki/AugustSprint
Please join us on #getpaid . If you aren't there, you can always use this email list to figure out how to help!
Go
sprinters go!Given that it is already Thursday in New Zealand (where we
have some awesome GetPaid community members!), feel free to go ahead
and start early :D