All the Perl that's Practical to Extract and Report

Hackathon

gnat on 2003-03-30T22:45:44

So we're going to have a hackathon at OSCON. Basically, if you can think of a project that you, possibly with others, want to work on, then you follow these simple steps:

  • Rally your troops--find out who else wants to hack with you on this project.
  • Tell us by mailing oscon03hackathon AT oreilly.com saying what your project is and who will be working on it. (This is so we know how big a room to have--just turning up on the day without warning us would be bad)
  • Hack!
The Hackathon runs from 9 A.M. Sunday July 6 to 9 P.M. Monday July 7--36 hours of open hacking. We'll have chairs, tables, a whiteboard, wireless, and a hub. You should bring laptops and something to hack on.

What's to hack on? Add a feature to your favourite module. Work through the TODO list in the Perl core. Clean up the Perl bug database. Tidy up the Perl docs. Add a feature to parrot. Pick a module on CPAN with a lot of bug reports in the CPAN RT database, and fix those bugs ...

--Nat

how about...

jhi on 2003-03-31T10:42:35

...Perl 5.8.1 bug-fix-athon? Oh, dang, I was supposed to be ready by then.

Re:how about...

gnat on 2003-03-31T12:23:34

If you're not ready by then, maybe we should pound on whatever bugs remain ...

--Nat

Re:how about...

ziggy on 2003-03-31T13:49:40

Even if Jarkko is ready by then, maybe we should pound on whatever bugs remain... (There's still the development tree ya know...)