Wiki - Hackathon
Hackathon
diff v11 - v12
v11: 10/25/08 10:49 PM - Seth Viebrockv12: 10/25/08 10:50 PM - Seth Viebrock
--- Hackathon v11
+++ Hackathon v12
@@ -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 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.
+ * '''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.