Hi,
> Thanks for sharing your notes after the conference and sprint. Certainly > some of the points you mention are an accurate description of the current > state of GetPaid (ie there is no product manager now), but I think your > characterization of GetPaid's viable underestimates both the product and the > people in the community and I wanted to respond and provide some of the > information that was shared in the conference presentation as well. > Thanks for very good response Chris. I hope I was not over-critical with some of my points, I must some I love getpaid very much though feeling the frustration now and then, like many of us do. It's almost there that you could use it for Plone commercing needs, but it gives some problems which would be solved if you used external shopping system. I was hoping that my email would inspire some discussion so people, even ones who didn't go to conference, could see that the train is still going :) > > There are several sites that have been launched with GetPaid already. About > two dozen are listed at > http://www.plonegetpaid.com/why/sites-using-getpaid . Some are just "out > of the box" GetPaid and work well for the client as is, some are customized > (and many of the docs about how to achieve the customizations shown are > linked to in the presentation I gave at the ploneconf2009: > http://snurl.com/getpaid-slides ). I think the barrier comes when you need to have some "deeper" customizations. Like having a new field on Order. You basically need to go to hand-edit getpaid.core or override various, various, adapters and templates. Which makes it difficult as it is not very clear how things are connected. Getpaid architecture, nice as it is, tries very hard to keep "architecture" (getpaid.core) and "implementation" (Products.PloneGetPaid) separate from each other. For example, payment processor contain both architectural and UI drop ins. The problem comes with latter when people create plug-ins which need to use overrides.zcml to get things done. However these problems are just technical, and they can be solved when community knows what they are aiming at and have time do the work. This issue has been already discussed partially with's Brandon's work on payment processors. > Regarding people who are playing roles to maintain the product, GetPaid has > gone through a period of activity and evolution, several releases. > Unfortunately, I left some of this story out of the presentation in > Budapest. Perrito (Horacio Duran) has managed a release (0.6.2, I believe) > and Lucie at SIx Feet Up has managed releases over the 0.7 series of > PloneGetPaid, and David Glick from Groundwire has been involved since ~0.8. > These are all people in the Plone community who are/were involved over a > period when they were using GetPaid and were working to make it better for > their needs. I'm hoping that is what we are starting again as a community. > Great :) The problem is that no one really knows when to commit trunk. Lots of patches end up being in the bug reports and email attachment (like the late issues with inter-database references), when there is no a single point of contact who would help to maintain the trunk. As already discussed, some nice ideas come up. >The project is now in a period where we need new people with interest in ecommerce in Plone to step up and lead in various aspects of the project. That's an invitation I extended during the presentation at the conference. There are >several people interested in getting the remaining needed functionalities (downloadable files, premium content, others), and the model we took in organizing this project originally (see Social Sourcing presentation, >www.ifpeople.net/solutions/social-sourcing ) was about getting people involved upfront in a round of changes. So yes, as you point out, there was an original architect who is no longer active in the project. But, of the other sponsors, >supporters and contributors at the very outset of the project, about 3/4 are still involved in the project in one way or another, which gives us a solid basis of community around GetPaid. Now it's time to get the community involved in >actively shaping the future again. Here we are! Cheers, Mikko -- GetPaid for Plone: http://www.plonegetpaid.com (overview info) | http://code.google.com/p/getpaid (code and issue tracker) You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en?hl=en
