If you're curious about Parrot, please join us. You don't have to be an expert programmer. If you can follow the build instructions (or report where they fail for you), manage a source code checkout, and work an IRC client, you're plenty qualified. There are plenty of ways to get involved in almost any capacity you can conceive.
After taking the maintainership of Win32::API, I have been busy trying to build several useful environments to be able to test the module, including combinations of:
"So I don't really have an answer for you. When faced with a similar situation, I punted and did a PerlIO_fdopen(fileno(stdio)) instead of a PerlIO_importFILE(stdio). This way you know you are creating a unixio layer which gets ref counted properly." -- Craig A. Berry, somewhere in the sprawling PerlIO layers saga.
Wellington.PM are holding a quiz night on Tuesday December 12th at 6:00pm start.
Don't imagine that you need to be a Perl expert to take part - in fact that probably wouldn't help at all. The questions will cover a range of topics related to computers; programming; the internet; and free and open source software. The emphasis is on fun. The teams will be organised at random, so you really don't need to do anything except turn up on the night. Please bring friends and workmates along, but don't assume you'll end up on the same team.
With patch Change #29430 the regex engine should now be sufficiently abstracted that it is reasonably feasable to write a plugin to use a different regex engine in perl. The documentation for most of the interface is contained in the perlreguts module although one needs to understand the flags in the regexp.h in order to make it work.
I've created a Perl Community calendar on Google Calendar. I've wanted to do this sort of thing for a long time to help track that stuff for The Perl Review's print listing. I've given up on writing my own calendar application. Google Calendar has a decent interface that I don't have to support, and it provides feeds: XML, iCal, and HTML.