Rakudo.org

Everyone

Writing working Perl 6 code really helps, especially if you submit bugs you found, or share your work in form of an open source library.

Bugs can be submitted by sending an email to rakudobug@perl.org. Existing bugs can be seen on the perl.org bug tracker.

Some good relevant articles about helping with Perl 6 are available from
* http://use.perl.org/~masak/journal/39445
* http://perlmonks.org/?node_id=780001

If you still would like pointers where to start, jump over to irc.freenode.net/perl6 and say "Hey how can I help?"

Developers willing to learn Parrot

Join the perl6-compiler mailing list. Read the Rakudo ROADMAP. Ask on IRC how best to help; the current Rakudo developers are the best people to answer this.

Developers wanting to help without learning Parrot

The best way to do this is to learn Perl 6, and write some real code. This will help uncover bugs. When doing this, please ensure that there is not an existing bug, and then file a bug report. One of the best ways to find out whether it is an existing bug is to ask on IRC. At most times of day, someone will be able to help; otherwise just file a bug.

Developers wanting to help with documentation

Would you like to contribute to rakudo.org? After creating an account, email Andy Lester (andy at this domain) and ask for page creation privileges.

Join the perl6-language mailing list. Read the existing documentation. Ask on IRC how best to help.

Have a look at the Official Perl 6 Specifications. If any of the ones marked "DRAFT" still look like they could use some work, and you can see how to improve them, then ask on IRC for an appropriate commit bit, and get to work on your chosen area. All final decisions will be made by Larry Wall, our benevolent democritator, but contributions (especially of the sort that spot inconsitencies or incompletenesses) are very useful.

Another way to help is to help Carl Masak with his u4x (Userdocs for Christmas) project.