"Leopold Toetsch" <lt@toetsch.at> wrote: >[ cc'ed list ] > > On Sep 18, 2005, at 17:52, Nicholas Dronen wrote: > >> >> Hi, Leopold: >> >> I'm interested in contributing to Parrot development. I'm in grad school >> and working 25 hours/week, so I can only afford to give a few hours >> per month. Even so, I think the best thing for me to do is to pick a >> thing to do, and just do it. Does #34394 seem like a good place to >> start? > > Great, thanks. All contributions are very welcome. > Indeed, welcome Nick. :-) Picking something that needs doing and doing it is a good way to get involved - I started out by sending in patches to deal with Win32 related issues. #34394 is probably a decent thing to start out with - it'll get you familiar with PMCs and doesn't require knowledge of a massive amount of the Parrot codebase to acomplish. I guess if I could offer any advice, it'd be don't be afraid of asking questions and also expect to have to look at the source to figure some stuff out, because the docs aren't always as great or up to date as you might hope. Noting where the docs seem wrong/missing/unclear, or if you can and have the time sending in a patch to correct them, would be a big help. JonathanThread Previous | Thread Next