Where should I pay?

[Linas Vepstas]

On Fri, Apr 04, 2003 at 04:44:10PM -0800, Bill Wohler was heard to remark:
> Carl Parrish <cparrish at carlparrish.com> writes:
> 
> > Okay if I have a client willing to pay for gnucash where should I send
> > them?
> 
> One option is to set them up with a contractor they can pay to install
> gnucash for them, to show them how to use it, and--most important--to
> fix bugs and implement features for them, feeding the changes back into
> the repository. Assuming these changes are done in a way that are
> generally useful, this would be a tremendous help for the project.
> 
> Derek could facilitate this by adding a Consultants contact list on
> gnucash.org.

Thanks  for the thought, and if Derek wants to be listed as a
consultant, I'll let  him ask me.   Other than a chosen few, I would
not want to list any 'consultants' unless they can show some sort 
of track-record for running that kind of business, and some prior
experience developing for gnucash.  Given what I know, I'd venture
to say this list is very short.

My breif experience as a gnucash 'consultant' is that 
1) there are very very very few requests.
2) most casual requestors keel over & die when quoted a price.
   For the cost of paying a us/european based developer to add
   some feature to gnucash, you can buy a full-fledged, feature-rich
   prioreitary app.  Most business people will figure this out.
3) One casual requestor who *was* willing to pony up that kind of
   money seemed to want to farm out the work to developers in 
   India, because of the perceived cost savings, and use me as 
   an architect/patch maintainera. 

I guess I'm saying I don't want to condone some kind of activity
where some unknown person promises to add feature X to gnucash
for $500 and disappears with the money.  This benefits no one.

--linas


-- 
pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas at linas.org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933