Perl 6
Getting Involved: Revision 6
^^^ Hacking on Perl 6 code
If you haven't already, [Download Perl 6] to prepare. The "Perl 6 Community Development Server"<http://feather.perl6.nl/> provides free accounts for Perl 6 development.
^^^^ Reading Material for Pugs Hackers
Besides these links, the Pugs distribution also provides README, `READTHEM` and `READTOO`.
* "Pugs Apocryphon 1"<http://svn.perl.org/perl6/pugs/trunk/docs/01Overview.html> Overview of the Pugs project.
* "Doing Pugs-related development"<http://svn.openfoundry.org/pugs/docs/getting_started>.
* "A Peek Into Pugs Internals"<http://perlcabal.org/%7Egaal/peek/start.html>
* "German language notes about compiling Pugs"<http://dresden-pm.org/cgi-bin/twiki/view/PM/PugsFirstBlood>
^^^^ General Perl 6 Tasks
A running list of tasks to work in kept in the repo at "TASKS"<http://svn.openfoundry.org/pugs/TASKS>. It's a catch-all list. Something on it is bound to match your skill set!
^^^^ Perl 6 Tasks for Perl 6 programmers
[Preludification Candidates] discusses parts of Perl 6 that can be written in Perl 6.
There's also plenty to do related to the test suite, which is written in Perl 6. See "t/TASKS"<http://svn.openfoundry.org/pugs/t/TASKS> for work to do there.
Also, scan through the "Synopsis which is cross linked with the test suite"<http://feather.perl6.nl/syn/%22>. Look for sections of the spec that don't mention test scripts. These means there is a either a test script without a smart link, or no tests have been written. (t/TASKS explains about smart links and much more!)
You might also be interested to "Start Your Own Perl 6 Module"[How to Start a Perl 6 module project], or work one of the existing ones.
^^^ Hacking the Perl 6 docs
In general, offical docs are stored in `docs/Perl6` and `docs/Pugs` in POD format, and they are fair game to improve directly. The exception is most of the documents in `docs/Perl6/Spec` which is the official Perl 6 specification. Improvements to the official spec should be suggested to the "perl6-language list"[Mail Lists, IRC, Archives].
* The "README"<http://svn.perl.org/perl6/pugs/trunk/docs/README> for would-be Pugs documentation contributors
* "The evil plan"<http://svn.perl.org/perl6/pugs/trunk/docs/notes/docs_evil_plan.txt>. This mentions many things you can do to help out with docs, although it is a bit dated.
* This plan is still current AFAIK: "Perl 6 developers are refactoring relevant introductions, tutorials, specifications into the Perl6::Doc namespace; expect to see this module subsumed by it in the near future.":
** (<http://www.annocpan.org/~AUTRIJUS/Perl6-Bible-0.30/lib/Perl6/Bible.pm>),
** (<http://search.cpan.org/~autrijus/Perl6-Bible-0.30/lib/Perl6/Bible.pm>).
If you haven't already, [Download Perl 6] to prepare. The "Perl 6 Community Development Server"<http://feather.perl6.nl/> provides free accounts for Perl 6 development.
^^^^ Reading Material for Pugs Hackers
Besides these links, the Pugs distribution also provides README, `READTHEM` and `READTOO`.
* "Pugs Apocryphon 1"<http://svn.perl.org/perl6/pugs/trunk/docs/01Overview.html> Overview of the Pugs project.
* "Doing Pugs-related development"<http://svn.openfoundry.org/pugs/docs/getting_started>.
* "A Peek Into Pugs Internals"<http://perlcabal.org/%7Egaal/peek/start.html>
* "German language notes about compiling Pugs"<http://dresden-pm.org/cgi-bin/twiki/view/PM/PugsFirstBlood>
^^^^ General Perl 6 Tasks
A running list of tasks to work in kept in the repo at "TASKS"<http://svn.openfoundry.org/pugs/TASKS>. It's a catch-all list. Something on it is bound to match your skill set!
^^^^ Perl 6 Tasks for Perl 6 programmers
[Preludification Candidates] discusses parts of Perl 6 that can be written in Perl 6.
There's also plenty to do related to the test suite, which is written in Perl 6. See "t/TASKS"<http://svn.openfoundry.org/pugs/t/TASKS> for work to do there.
Also, scan through the "Synopsis which is cross linked with the test suite"<http://feather.perl6.nl/syn/%22>. Look for sections of the spec that don't mention test scripts. These means there is a either a test script without a smart link, or no tests have been written. (t/TASKS explains about smart links and much more!)
You might also be interested to "Start Your Own Perl 6 Module"[How to Start a Perl 6 module project], or work one of the existing ones.
^^^ Hacking the Perl 6 docs
In general, offical docs are stored in `docs/Perl6` and `docs/Pugs` in POD format, and they are fair game to improve directly. The exception is most of the documents in `docs/Perl6/Spec` which is the official Perl 6 specification. Improvements to the official spec should be suggested to the "perl6-language list"[Mail Lists, IRC, Archives].
* The "README"<http://svn.perl.org/perl6/pugs/trunk/docs/README> for would-be Pugs documentation contributors
* "The evil plan"<http://svn.perl.org/perl6/pugs/trunk/docs/notes/docs_evil_plan.txt>. This mentions many things you can do to help out with docs, although it is a bit dated.
* This plan is still current AFAIK: "Perl 6 developers are refactoring relevant introductions, tutorials, specifications into the Perl6::Doc namespace; expect to see this module subsumed by it in the near future.":
** (<http://www.annocpan.org/~AUTRIJUS/Perl6-Bible-0.30/lib/Perl6/Bible.pm>),
** (<http://search.cpan.org/~autrijus/Perl6-Bible-0.30/lib/Perl6/Bible.pm>).
