On Sat, Jul 21, 2012 at 6:14 AM, renato wrote:
There's no simple way that this can work. The dev that works on a
particular problem has to be an expert with the software to be fixed.
Usually this means being the one who wrote it in the first place.
Also, you never know how long you'll spend working on a problem, until
you actually do it. Anyway, the notion has been surviving for
years--I'd say "search the archives", except I have no idea what terms
would actually work.
Suppose I write a potentially
useful software, and then leave several bugs until people start
funding it. Then, rake in the dough and fix the bugs (I already know)
in record time. It changes the incentive whether and how to create
But changing the incentive is the entire point, right? IMO--devs need
no particular incentive. Funding conferences is a more attractive
option--for those aspiring academics and those who are building a
resume, free software conferences provide another route to
Linux-audio-user mailing list