http://www.perlmonks.org?node_id=682368

Google has just announced their accepted projects for the 2008 Summer of Code.

This year's Perl projects are:

Apologies to any monks I didn't recognise (and thus didn't link to)

If you still have an itch to scratch, and some time to develop (unfortunately, without Google's $4,500), have a look at the full list of ideas submitted for GSoC 2008.

Replies are listed 'Best First'.
Re: Google Summer of Code projects for Perl
by elmex (Friar) on Apr 23, 2008 at 17:30 UTC

    Nice projects have been taken! The Math::GSL projects looks like it could become really useful. And lets hope the 3 Perl 6/parrot related projects are fruitful.

    I wonder about the test suite, will the student be able to actually run all his tests? Or is he writing without testing his test scripts? I mean: Is all the stuff from those 15 synopsises implemented? Where? In PUGS? Rakudo?

    (I thought about participating in GSOC this year too, but for GNU Smalltalk. But in the end I decided I want to concentrate on my studies, and the $4,500 are just ~2835 Euros these days (I'm living in the EU))

      Well, obviously, under a test-first methodology, if you want to test your test files, you'll have to write some tests for your test files first. And then if you want to test those tests... :)

      Seriously, we have ways of marking tests as "todo" for various implementations, and it's just a degenerate case if you have to mark the test as "todo" for all implementations.

      I'm the student that's writing the test suite. I addressed those issues in my proposal, but that part isn't public, so I'll explain how I plan to get it correct.

      TimToady addressed the TODO issue rather well. I'm going to try as many implementations as feasible, but some will fail. For those, I'll refer to the spec as much as possible. If the spec is unclear, I'll ask on #perl6 and perl6-language. Peer review is another source of ensuring that the tests are correct.