Pugs Janitor Tasks.

During the YAPC::NA hackathon, chromatic++ had this great idea of a weekly-refreshed list of Janitor Tasks from Parrot and Pugs -- things that requires no internal knowledge to implement, can be done within a couple days, but nevertheless would have a significant positive impact on the project.  He plans to syndicate this list as part of the perl.com weekly newsletter; here is this week's list for Pugs:

• Go through examples/ and see if any of the examples fails to run; if so, seek advice at #perl6 to get them fixed.  Along the way, write regression tests for those examples -- currently only a handful of examples are tested under t/examples/.
• Harness Pugs's interactive shell with perl5's IPC::Run (or something else) and produce a web-based evalbot, similar to http://tryruby.hobix.com/.  Remember to set the PUGS_SAFEMODE environment variable to true -- use &Pugs::Safe::safe_getc, &Pugs::Safe::safe_readline and &Pugs::Safe::safe_readline for interaction with the user, if needed.
• Put the current http://pugscode.org/ homepage into the repository and merge it with the docs/feather/, and reorganize the homepage a bit to make e.g. downloads easier to locate.
• Look over test files in t/bugs/, especially the ones that has been fixed (i.e. without :todo in them), and move them into other more descriptive directories under t/.

If you are interested to help out, please apply for a commit bit on irc.freenode.net #perl6, or perl6-compilers. More suggestions welcome!