Should I read all the exegesis and apocalypses first?
That'd be a good start, although the language is constantly changing (and I don't believe the exegesis and apocalypses are updated so frequently). If you'd like to know what's been covered and where perl6 is going I'd recommend checking out the perl6-language mailing list and because it's a public forum you can easily contribute.
I take it Perl 6 and Parrot are completely separate projects. Which one requires more assistance?
Perl6 is basically ideas, discussion, documents and a bit of code at the moment and is developed quite separately (not entirely by any means) from Parrot. I couldn't say which needs more assistance but Parrot is there and running (so is some of Perl6, which comes with parrot) so is somewhat more hands on and could always to do with extra brain.
Documentation - where's it at? What needs to be written?
The perl6 docs consist of the exegesis and apocalypses and Michael Lazzaro's Perl6 Object Oriented Cookbook (with help from the community of course :). There's also the perl6-documentation mailing list that is trying to get the perl6 spec down on paper.
As for parrot, there's a good deal of documentation that comes with the download and of course you'll a lot of info/discussion about it on the perl6-internals mailing list.
If these mailing lists seem a bit daunting then I highly recommend the informative, succint and always entertaing perl6 summarys, summarized by none other than the wonderful pdcawley himself!
Level of skill required?
This really depends on what you're doing. Having C skills definitely helps with parrot development but you'll also need to get your head around some pretty nifty stuff. But if you're documenting then it's a different story altogether and really depends on your knowledge of what your documenting and subject surrounding it. However if you'd just like to be a casual contributor then the mailing lists are perfect tweaking ideas, adding syntax (seems to be quite popular among some of the regulars ;) and generally being another pair of eyes to look at what's going on.
HTH

_________
broquaint

In reply to Re: Perl 6 Involvement by broquaint
in thread Perl 6 Involvement by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.