The language design process has been and continues to be a long rough road. Opening up the design process to the entire community and filtering everyone's "good" ideas hasn't made it any easier. While a vast amount of the language has already been designed and decisions rendered, on paper only about 1/3 of the Synopses
have been published.
So how can you help out and learn Perl6 at the same time? You can post patches to the Perl6 mailing list against the change controlled documents and pmichaud has volunteered to moderate commits. So what are some things that patches are needed for?
- For unwritten Synopses, an outline of what is to be covered (reference Perl6 Timeline By Apocalypse)
- For written Synopses, any missing headings that need to be filled in
- When a decision is rendered by @Larry on the list, a patch to the appropriate documented
- Searching the archives for the latest decisions that haven't been incorporated yet