From: Richard Lyman <lymans@...>
Date: 2005-05-04T09:36:42+09:00
Subject: Re: "Bounty" approach for small pieces of code?

While all of these are 'nice' features - what you're really wanting is
only an advanced form of contract work. Why don't we just stick to
that model?

Steps:
1. Someone ("funder") wants to "develop ruby stuff"
2. "funder" starts really small - so small that losing the money won't
matter ("small project").
3. "funder" offers "small project" to a group preselected by resume -
resume defined the same way it always is: either a piece of paper, or
previous extablished work.
4. "small project", and associated terms, is accepted by "contractor".
5. "contractor" finishes "small project".
6. If "funder" is pleased then the two form a "relationship" that
moves on to bigger projects. If "funder" is not pleased, then no
bigger risk is taken either with the "contractor" or (worse yet) with
Ruby.

It's that simple.

(I know, I know - it sounds like I'm giving dating advice... lol...)

So. If someone wants something done - just start small and work your way up.

I imagine that if the "contractor"s "resume" was good enough the
"funder" could skip steps 1-5. Which would be ideal in my opinion...
and so very few have a "resume" that is _that_ good... but there are
some who do - and they _have_ skipped steps 1-5.

-Rich