Google Checkout Module for 68 Classifieds

Just my 2 cents:

I don't think this should be something done by 68C itself. This could easily be done by a 3rd party developer. Sure you might have to pay more for this, but would you rather the cost of creation, maintenance, security auditing, and support be added into the cost of the 68C script for everyone? These kinds of custom requests are better suited to 3rd party development. The less core changes you have the less the system needs to be updated saving everyone time/money.

My thoughts are, the system is fine the way it is. However, I think the custom payment provider should be expanded to deal with 3rd party provider requests, if it doesn't already (haven't given this bit of code much of a look).

The payment system should be able to support modules that take payment for other kinds of services at least to a minimum level. I think opening up the payment system for module access would increase the likelihood that modules for other payment systems will be developed.

I think Maffo has the right idea, site owners (see a handful of them voted yes) could pool their money and hire someone to develop this and all share in the benefit. Heck they could even stipulate that they can resell the module and earn back all of their investment.

I also would like 68C to concentrate more o features that appeal to the majority.

As for pooling money, thats a great way to "buy" code if you can all organize it. Keep in mind though that you all have to agree on the implementation of the feature request.

As far as stipulating that you then become owners of the code, that gets a bit tricky.

For starters, if you own the code and sell it you better be prepared to support it. Also, code is intellectual property and in the US is copyrighted at time of creation. By stipulating that you as the buyer now own it you are asking for someone to sign over their copyright to the code and in turn give up future profits from it. This is something I wont do unless paid a very high premium for the code itself since I legally lose the right to reuse and resell it myself.

Eric - I meant the ability to inject the payment amount, then intercept the payment return and do something else other than create an order for a listing or approve a listing.

Larry - you are very right. I tend to always think of something as if I were to do it, so supporting it comes second nature to me. Thanks for reminding anyone else not to forget that aspect.

The last post in this thread before yours was a year old, you really dont need to search for and bring every post on this topic back to the front, I think we have all seen you many posts on this subject already!

Please read Larry's reply. It is clear that this payment gateway does not exist and nobody is working on it. You only need to submit it as a feature request rather than dragging multiple old threads back to put them at the top and then trying to redirect other threads back to your thread. It is not going to get your concern or desire for this payment provider to be supported any more attention.

Demand drives development. If no one is working on it then demand simply isnt high enough or at least not high enough to warrant the effort.

Look at this from a developer standpoint. This poll shows 14 people interested.

If the mod for example sells for $50 and you sell 15 copies thats $750. And this of course doesnt take into account future sales but it also doesnt acount for potential support issues along the way that eat up time.

What if the module takes you 40 hours to create and your normal hourly rate is $50 an hour in the same amount of time you spent making the module you could have made $2000.

At the end of the day asking a developer to undertake this project you are asking them to take a 63% pay cut. Are you willing to work for 63% less than you are now?

People have car payments, heating bills and mortgages to pay.