Each year, [Google Summer of Code](http://code.google.com/soc/) puts hundreds of students to work on open source projects, and pays them for it. The Perl Foundation is proud to announce that it has been accepted as a sponsoring organization this year. Students propose projects that they'd like to have funded, and are assigned a mentor who will help guide the student and project to completion. For students, this is a great way to contribute to open source, get experience working on real projects that you can put on a resume, and get paid for it. You'll be helping open source while helping yourself. For mentors, you'll also be helping open source, and helping a new programmer get his or her start. Jonathan Leto's blog has [links to find out more](http://leto.net/dukeleto.pl/2009/03/tpf-accepted-to-google-summer-of-code-2009.html).
At the nudging of some users, I've gone back and fixed up some bugs in long-untouched modules, and at the same time moved their repositories over to [github](http://github.com), which I am enjoying more every day. Template::Timer fixes a bug that's been around since 2005 during installs. Perl::Critic::Bangs was doing invalid testing that meant breakage with the new 1.098 release of [Perl::Critic](http://search.cpan.org/dist/Perl-Critic).
Rakudo Perl, the implementation of Perl 6 on the Parrot virtual machine, has made [a milestone release](http://use.perl.org/~pmichaud/journal/38562). For years now, Rakudo has been tucked into the Parrot project, but no longer. Rakudo is now its own project, with its [own source repository](http://github.com/rakudo/rakudo) and its own release schedule, following the Parrot release schedule closely. This 14th development release of Rakudo is codenamed Vienna, after Vienna.pm, the Perl Mongers group that has been sponsoring Jonathan Worthington's development work since April 2008. Future releases will be named after other Perl-related cities. This is a fantastic time to take a look at Rakudo and see what's happening. We're reaching the top of the hill, and I couldn't be more excited.
I got errors on my Mac today complaining about IO.pm. I had just installed Parrot on the way to building up a Rakudo to work on, so I figured something in the still-not-ironed-out Parrot install had caused the problem. It looked like this:
% perl -MIO IO object version 1.22 does not match bootstrap parameter 1.23 at /System/Library/Perl/5.8.8/....
I just figured I'd reinstall the module.I tried to update IO.pm, but the CPAN shell uses IO, and so barfed. Had to install it manually by downloading a tarball (gasp!) and doing it manually. And then everything was fine.
And then my old colleague Ed Silva IMs me asking if I knew anything about it. I had to confess I was surprised to see he had the same problem.
And now Miyagawa, bless his heart, lays it all out for you in this blog post about the Mac OS X security update. Ooopsie!
Thanks to Miyagawa for explaining the problem.
I just gave [my keynote at Frozen Perl](http://www.slideshare.net/petdance/frozen-perl-2009-keynote), and one of the big points I made was that we don't know what Perl 6 is going to look like. It's totally a green field. There's no toolchain, no LWP, no DBI, etc. My big question: Should Perl 6 use the CPAN? Does an 11 year-old distribution system make sense in 2009? In 1998, when we didn't have everything living in a cloud, and hosting websites took a lot of money, and if you wanted massive bandwidth, you were at a big company or a university. In 2009, those are no longer true. Of course, I'm not suggesting that we don't distributing thousands of excellently awesome modules to the world. If we didn't, we wouldn't be Perl. But does it need to be through a centralized distribution channel like PAUSE + CPAN? I don't have an answer. Discuss.