develooper Front page | perl.perl5.porters | Postings from May 2009

Re: spending other people's money

Thread Previous | Thread Next
From:
Elizabeth Mattijsen
Date:
May 31, 2009 12:12
Subject:
Re: spending other people's money
Message ID:
p0624081fc64886088a1c@[10.0.1.191]
At 10:39 PM +0100 5/30/09, Nicholas Clark wrote:
>It's almost 6 months since booking.com kindly donated $50,000 to TPF
>
>     to aid in the further development and maintenance of the Perl programming
>     language in general, and Perl 5.10 in particular.
>
>  http://www.hsyndicate.org/news/4039070.html
>  http://news.perlfoundation.org/2008/12/bookingcom_makes_a_major_contr.html
>
>
>So far there is no published plan to spend it, as best I can tell from out
>here the entire amount remains safely in the bank, and at it stands there
>will be no change in the next 6 months either. This aids neither development
>nor maintenance.
>
>Also, vienna.pm still has around $35,000 surplus from YAPC::EU 2007 to spend
>on "advancements of Perl": http://use.perl.org/~domm/journal/39013
>
>
>So, without consulting either group, or anyone with commit rights, here's an
>impertinent suggestion on how to try to spend other people's money. It has 3
>virtues:
>
>Laziness:   It requires nearly no up front effort to organise
>Impatience: It tries to spend as much money as rapidly as possible
>Hubris:     It ties to both get bugs fixed, and draw new people in.
>
>
>And the crazy scheme is: Offer bug bounties on every open Perl 5 bug*
>
>http://rt.perl.org/rt3/Search/Results.html?Query=Queue%3D%27perl5%27AND(Status%3D%27open%27ORStatus%3D%27new%27)
>
>
>Anyone can claim:
>
>    $25 for correctly identifying* the change that introduced a bug
>            or demonstrating that the bug has been present since 5.000
>            or explaining why it is not a bug, and should be closed
>
>    $25 for a committed TODO test*
>            or for identifying the existing TODO test
>              [may well be cheaper to write a new test.
>               I don't have a problem with this]
>            or for identifying which bug this is a duplicate of, and merging it
>
>[bugs in dual life modules can't earn any more, at this point*]
>
>    $50 for Perl code that is committed to blead that fixes the bug
>   $100 for Bourn shell, Makefile or other code that is committed to blead that
>              fixes the bug
>   $150 for XS or C code that is committed to blead that fixes the bug
>
>   $200 bonus for fixing bugs present in perl 5.000
>   $400 bonus for fixing bugs present in perl 1.000
>
>
>Hence $100 for completely resolving a Pure perl bug, or $200 for completely
>resolving a bug in C code.
>
>However, the minimum payout is $500, equivalent to
>
>   20 git bisect runs
>   or 10 bisect + TODO test
>   or 10 bisect and de-duplicate
>   or 5 bisect + fix pure perl bugs
>   or 2.5 bisect + fix C bugs

FWIW, I like it!


At 1:17 PM +0100 5/31/09, Nicholas Clark wrote:
>It's actually "How can I spend the money as quickly as possible, with the
>least effort, and then be given more money to repeat the trick?"
>So the revised scale of virtues is
>
>Laziness:   It requires nearly no up front effort to organise
>Impatience: It tries to spend as much money as rapidly as possible
>Hubris:     People will actually give *more* money to keep it going

Count Dijkmat in!



Liz

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About