Wiki - Hackathon
Hackathon
diff v23 - v24
v23: 01/21/09 11:24 PM - Leonard Miller (olegm)v24: 01/27/09 04:14 PM - Patrick Michaud (Pm)
--- Hackathon v23
+++ Hackathon v24
@@ -39,7 +39,7 @@
== Project Descriptions ==
- * '''Rakudo & Parrot''' - Patrick Michaud will lead a hackathon focusing on Rakudo and Parrot. More details TBA.
+ * '''Rakudo & Parrot''' - Patrick Michaud will lead a hackathon focusing on Rakudo and Parrot. Our objective is to enable people to contribute directly to Rakudo and Perl 6. The first part of the hackathon will be done as a presentation covering several key areas: (1) building Rakudo, (2) reviewing and updating the Perl 6 official test suite, including getting all participants a commit bit to the suite, (3) submitting bug reports and patches for Rakudo Perl, (4) a brief review of the Rakudo compiler architecture, and (5) review of current items where we can use some help (code, tests, website, and wiki updates). In the remainder of the hackathon we will focus on getting people to work directly on the items described in the presentation. Ideally people coming to the hackathon should already have a subversion client and development environment available to them.
* '''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.