I participated in a Parrot hackathon at YAPC::EU last year. It's actually very informal: you identify some bug or issue with Parrot you want to address and start hacking. It of course helps a lot if a Parrot guru like Jonathan or Alison is present :-)<br>
However, there are lots of little jobs that need to be done that don't require in-depth knowledge of Parrot, like fixing the build system, writing unit tests etc. For example, I did some work on taking code out of C header files and putting it in proper source files.<br>
Have a look at <a href="http://www.parrotcode.org/todo.html">http://www.parrotcode.org/todo.html.</a><br><br>I'll freely admit that personally, I would like to hack on the Parrot backend for Pugs, though that may not be very popular :-)<br>
<br>Cheers,<br><br>Wim<br><br><br><br><br><div><span class="gmail_quote">On 21/04/2008, <b class="gmail_sendername">Chris Yocum</b> <<a href="mailto:cyocum@gmail.com">cyocum@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br> Well, there is a wikipedia page about hackathons<br> (<a href="http://en.wikipedia.org/wiki/Hackathon">http://en.wikipedia.org/wiki/Hackathon</a>) but this is going to be a bit<br> of an experiment and probably no longer than a day. I would hope that<br>
we would have something to check-in but even if it is just to learn<br> something about parrot in a collaborative environment and re-convene<br> another time to do serious hacking, I would call that a success.<br> <br><br>
Chris<br> <br><br> On Mon, Apr 21, 2008 at 10:38 AM, Nick <<a href="mailto:nickwoolley@yahoo.co.uk">nickwoolley@yahoo.co.uk</a>> wrote:<br> > Hi,<br> ><br> > Assuming it doesn't clash with a previous engagement, I'd come along and<br>
> participate, even if it were just to find out what a Hackathon is or<br> > learn something about Parrot.<br> ><br> > About both of which I know almost nothing, by the way. Is any knowledge<br> > or preparation required on behalf of the participants? Is the aim to<br>
> create something useful that can be sanely checked back into the Parrot<br> > repository, or just to learn about Parrot?<br> ><br> ><br> ><br> > N<br> ><br> > _______________________________________________<br>
> Edinburgh-pm mailing list<br> > <a href="mailto:Edinburgh-pm@pm.org">Edinburgh-pm@pm.org</a><br> > <a href="http://mail.pm.org/mailman/listinfo/edinburgh-pm">http://mail.pm.org/mailman/listinfo/edinburgh-pm</a><br>
><br> _______________________________________________<br> Edinburgh-pm mailing list<br> <a href="mailto:Edinburgh-pm@pm.org">Edinburgh-pm@pm.org</a><br> <a href="http://mail.pm.org/mailman/listinfo/edinburgh-pm">http://mail.pm.org/mailman/listinfo/edinburgh-pm</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>If it's pointless, what's the point?<br>If there is a point to it, what's the point?<br>(Tibor Fischer, "The Thought Gang")