Entries For: June 2008
2008-06-12
Tax infrastructure implemented
We had some motivated folks at the Plone Symposium in New Orleans, and ended up doing a one-day sprint. And they got basic tax infrastructure implemented!!
Special thanks to CalvinHP, Claytron, and ChrisW for enthusiasm for taking on the taxes in GetPaid.
At the Plone Symposium in New Orleans, we did some collaborative design of the needs and requirements for tax infrastructure. Then, on last Friday, Calvin, Clayton, and Chris busted out the infrastructure!
Calvin's update reports:
During the NOLA sprint we put in place a few notable changes to the checkout/cart/order totaling so we can support the diverse ecosphere of taxing models around the world.
The old API used to just return a float for the call to the Tax Utility. Now the same call will return a list of dictionaries with one dict per each tax that is potentially applied to the order or configured in the system.
The next step from here would be to finish a default implementation of a ITax policy that can be registered in the site. I would suggest we just do a simple flat tax one so people get the idea of how to develop and register their own.
That is pretty much our current status for now. Let me if there are any other ideas floating around that we haven't thought of.
Please join the mailing list to connect around tax use cases.
You can check out the code in the repository or via buildout. This work will be part of GetPaid's next release.
PloneFormGen + GetPaid integration galloping along
Thanks to a lot of work by GetPaid and Plone community members, this integration work is rapidly evolving! Here's a quick update.
The Symposium in New Orleans was a hotbed of GetPaid collaboration. We jump started a collaborative design process for integration PloneFormGen with GetPaid based on the nifty Salesforce.com adapter for PFG. Now, a week after we left New Orleans, already work is rapidly evolving:
- SteveM added a new feature to PFG (so action adapters can fail) and the code is tested and ready to release - thanks SteveM!!
- DanielHolth and perrito666 have been furiously hacking away and sharing code in a mercurial repository.
- Daniel's update today:
perrito666 and I have been developing this at a rapid pace. So far we
have something that's addable to the form and does a little bit of
work. My end adds 0 of all the products in a given folder into the
cart, and then the user might update their cart to select how many of
each they want. - Last I saw, perrito666 was working on pre-populating the PFG folder with the required GetPaid forms.
2008-06-11
14,937 Lines of Code
Almost in time for our second major release, Ohloh updated our stats. Here's a quick summary...
GetPaid's report at Ohloh has been updated to give stats on the project. We are now up to 14,937 lines of code. Other interesting factoids:
- 3 person-years worth of code (in about a year's time)
- 44 contributors
- 112 people following the mailing list
- 750+ downloads of the first release (plus many users with buildout)
- Over 170 downloads of the second release (only out for 2 weeks so far)
- 4 sprints
Check out more stats at Ohloh. Browse the code, download and report issues here.
2008-06-09
New payment processor available: DPS PXPay
Thanks to some friends in New Zealand, a new payment processor is available for use with GetPaid!
Payment Express is a Visa and MasterCard certified solution, developed by DPS, which facilitates electronic payments seamlessly from multiple access points i.e. Web, EFTPOS, Billing, Interactive Voice Responce, CRM, Vending, MOTO (Mail Order / Telephone Order) and Wireless.
DPS are certified with banks in Australia, New Zealand, Pacific Islands, Singapore, South Africa, USA and United Kingdom.
The payment processor is distributed as an egg getpaid.pxpay and is available on http://pypi.python.org/pypi.
This processor plugs in to the final step of the checkout. It provides the mechanism to securely authorize payment offsite.
See: http://code.google.com/p/getpaid/source/browse/trunk/getpaid.pxpay/src/getpaid/pxpay/README.txt for more help/discussion.
Thanks to Matt Halstead for integrating this and Darryl Dixon for kicking off the development!
2008-06-05
Taxes sprint!
We are going to do a small sprint to get tax handling in GetPaid underway here at the Plone Symposium New Orleans. Join us if you are interested!
Oh, and we are going to sprint on tax handling in GetPaid tomorrow (Friday) during the sprint day of the Plone Symposium in New Orleans. If you are interested in this, please see our evolving notes/design info and join us in #getpaid (or share your views/experience on the getpaid-dev mailing list).
2008-06-03
Social Sourcing talk at Plone Symposium NOLA
I will be giving another talk on social sourcing in New Orleans at the Plone Symposium.
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).
2008-06-02
GetPaid 0.6 release made
A long awaited release that improves the store functionality of GetPaid.
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
