Re: Bounty for Bugs in Open Source Projects?

   From: Robin Millette <[email protected]>

   There's also the concept of reverse bounties, where a developper write 
   down a specification, an estimate of the work needed to implement the 
   feature, and finally puts a price tag on it. That gets posted somewhere, 
   and when enough money is accumulated, the coder finishes the job and 
   releases his code.

Don't get hung up about such distinctions.  "bug bounty" ultimately
means little more than "I'm willing to pay on the post market for
labor directed in a certain direction.  It doesn't matter, after that,
where the *spec* for the work to be done comes from --- it can come
from developers, sure.

It's the hang-up about a central site rather than ad hoc semi-private
negotiation that caused past efforts in this area to fail.  There are
some secondary hang-ups (e.g., trying (deliberately or accidentally)
to use the licensing of free software as an excuse to skimp on
taxes....  just because source is freely licensed doesn't mean that
the payment for the labor to create is automatically charity....)

-t