Wiki - Hackathon

The Frozen Perl Hackathon will take place on Sunday, February 8th, the day after the conference. We will be reserving space for the hackathon soon, details to follow.

Last year we could accommodate approximately 25 people and expect similar accommodations this year. Please sign up below with your name and what you're interested in working on. If you're interested in leading a project work session please say so.

Where

TBD.

Food

We are still planning the event so food is not guaranteed just yet, but last year we did end up providing free coffee and tea all day, as well as pizza for lunch.

Projects and Project Leaders

Project leaders, please post below the project name you'd like to lead along with your name. Focused projects with delegable objectives are good, but we are open to anything. Some suggestions: Parrot, Moose, resume writing, Catalyst, Bricolage/Krang, Jifty.

Project Descriptions

  • Introductory Hackathon - I noticed last year that several people showed up to the hackathon with no clear project to work on, and some who signed up but didn't show. To these people: come to the hackathon this time, no matter your skill level. For this project we'll cover the basics of getting a module CPAN-ready. We'll look at Module::Build and/or Module::Starter, ensure POD coverage, write some simple tests, test Kwalitee, and cover developer-related aspects of CPAN. If there is time, interest, and a group of participants still remaining after the basics are covered, we could hack together a little feed aggregator or some simple modularized app wherein everyone could specialize in and contribute something regardless of their skill level. If we don't finish this year we could work on it at YAPC or save it for next year. The end product of our efforts may not directly and immediately benefit the Perl community, but this will certainly be indirectly beneficial by introducing the concepts and attitudes of contribution.
  • Test Your Module - Once you have the idea for a module, finding ways to test it effectively are not always easy. This would give people a chance to work through Perl Testing: A Developer's Notebook, deciding how to apply the material to their own modules -- or to a module they use that does not have adequate tests.

Attendees

Put your name and project(s) you're interested in working on ...


version 12 saved on 10/25/08 10:50 PM by Seth Viebrock

Home | Tags | Recent changes | History

Copyright © 2008-2009 Minneapolis Perl Mongers
The Perl logo is a trademark of the Perl Foundation.