There are many ways to help us develop Perl 6 and the Rakudo Perl 6 compiler, some of which don’t involve technical knowledge. Here’s an incomplete list:
- Use Perl 6, and give us feedback.
- Blog about Perl 6
- Contribute documentation
- Contribute marketing material (flyers, websites, artwork, …)
- Write and publish modules
- Organize workshops or meetings for Perl 6 developers
- Help to adminster our infrastructure (delete blog spam, maintain servers etc.)
- Hack on the compiler itself
- Provide benchmarks
- Answer questions on mailing lists, IRC and Q&A sites (stackoverflow, perlmonks)
- Don’t feed the trolls
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.
If you still would like pointers where to start, jump over to irc.freenode.net/perl6 and say “Hey how can I help?”
For code contributions to Rakudo itself, please see the Rakudo contribution guide on GitHub.
Developers willing to write C code
Developers how are willing to write low-level code help with MoarVM, the primary backend of the Rakudo compiler. There is an #moarvm IRC channel on freenode, which should be seen as the primary source of information about MoarVM.
Developers wanting to help without writing low-level code
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
General Perl 6 documentation is maintained on github. Look at the TODO and WANTED files in that repository, as well as into the issue tracker to get an idea for what’s missing. Also check out the README.
Would you like to contribute to rakudo.org? After creating an account, email Patrick Michaud (firstname.lastname@example.org) 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 Perl 6 design documentation. 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 inconsistencies or incompletenesses) are very useful.