How it works

1. Project maintainers submit links to TODO tests to the Management System for TODO Test Bounties. TODO tests should either test for a known bug, or for a yet unimplemented feature. The submission includes a link to some discussion of the issue, an estimate on the time needed to implement it, and a 'price tag' (which will be paid by Vienna.pm to whoever fixes the bug / implements the feature).
2. We prefer small and cheap things over big and expensive things. Something that can be done in a few hours / a weekend (or ~€250) would be ideal.
3. Vienna.pm reviews submitted TODO tests. We will prefer big projects (like Perl 5, Perl 6, etc) and widely used CPAN modules over something that's only used by few. Vienna.pm might change the price tag (up or down...).
4. Vienna.pm publishes a list of accepted TODO tests
5. People willing to implement the features / fix the bugs say that they want to do so
6. If the project maintainers agree, the implementor gets some time to do his/her work
7. As soon as the implementor is done, the project maintainers review his/her work
8. If the project maintainers are happy, Vienna.pm pays the specified amount into the implementor's bank account.

Budget

Our total budget for this project is €4,000.

Any money left will probably be donated to TPF for their grants.

Prototype

http://todo.useperl.at

Timeframe

We first need the Management System for TODO Test Bounties which should be ready by Jan 2008.

As we're doing the Winter of Code, the first run of this project will last until 31st March 2008. Depending on the success (and our funding), we might extend it, or stop earlier.

Trivia

Thanks to Nicholas Clark for suggesting this.

Maybe some of this bounties could go to how Todo's are handled (not eliminating Todo's from known modules). There has been a discussion on perl-qa which stated with "shouldn't "UNEXPECTEDLY SUCCEEDED" mean failure?" and continued with "TODO -> MAYBE tests?".

I have informed the perl-qa people about this bounties.

Cheers, Nadim.

contributed by guest@hidden on Dec 8 2:16am

To me that would seem like something that should be part of a separate grant application, rather than one of the specific TODO test bounties. My opinion isn't "no", just "not right here" - it sounds like something worth suggesting via the main Winter of Code page.

contributed by guest@hidden on Dec 23 3:40am

Well, its not always possible to make code that does incredibly complex stuff with good efficiency to be very simple but it is always possible to make the API to USE YOUR CODE simpler.
“The simpler your code is, the fewer bugs you will have. ” ;) http://www.superiorpapers.com/ -essay writer

contributed by Luke Sam on Oct 20 8:13pm