Wiki - Hackathon
Hackathon
diff v10 - v11
v10: 10/24/08 08:45 AM - Seth Viebrockv11: 10/25/08 10:49 PM - Seth Viebrock
--- Hackathon v10
+++ Hackathon v11
@@ -20,7 +20,7 @@
== Project Descriptions ==
- * '''Introductory Hackathon''' - I noticed last year that several people showed up to the hackathon with no clear project to work on, and several more who signed up but didn't show. Maybe these people didn't have (or feared they didn't have) the experience to work on the projects that folks were hacking on. Details are still in the works, but this project will be for those people who want to hack on something but aren't quite sure what. For this project I'd quickly cover the basics of version control, look at SVN and Git, talk about PAUSE and developer-related aspects of CPAN, introduce screen sharing and distributed pair programming, and then we'd hack together something like a little web service or whatnot, wherein everyone could contribute something regardless of their skill level. The end product wouldn't necessarily serve as a final product to directly benefit the Perl community but would rather introduce folks to the concepts and attitude of contributing to the Perl community.
+ * '''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 rather indirectly benefit from the introduction to 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.