All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

And yes, eight weeks of full time hacking. Given that Google are
(generously) paying at a rate equivalent to $27,000 per year, my non-humble
opinion is that any student not giving their full time attention is slacking.
How many other student summer jobs pay $14/hour?

Actually, turns out I'm about a year out of date. SoC runs for
3 months [google.com] this year,
so that's more like twelve weeks

I really don't feel that the suggestions are sufficiently epic in
scale. I believe we need to think bigger, such as:

Integrate PPI into Eclipse to provide full Perl refactoring support

(I've never used or needed to use Eclipse, but I assume that this is
plausible and useful from perusing their documentation. See also
Perl Needs Better
Tools [perl.com])

Check and when possible close every open Perl bug

There are 1500 open core perl bugs in RT. It would be good to check
every bug to see whether it's been responded to, whether it's still a
bug, and if so write a test case. Three months means 20 minutes on
average per bug, so completing this task is feasible. So it's of the
correct scale of epicness for SoC, although in fairness I don't think that
this is a good proposal, as there's not enough coding in it, and any one
person trying to do this would go insane

Migrate core perl from perforce to subversion

This isn't a trivial task to get right. Tools exist, but they aren't good
enough to migrate the nearly 30000 changes racked up in the past 9 years. In
particular, they fail to preserve the existing complex branching history,
which we need to preserve for code auditing purposes. So this task would involve
improving the existing migration tools, or writing more powerful new ones,
rather than a simple sysadmin fire-it-off task.

What could existing Perl projects such as DateTime, Module::Build or
bioperl achieve with a 3 months of full time work?