• Perl::Critic is looking for help

    Jeffrey Thalhammer has posted about how the [immensely helpful Perl::Critic](http://search.cpan.org/dist/Perl-Critic) system [needs some help](http://perlmonks.org/?node_id=736290) slogging through its backlog of bug tickets. If you're a user of Perl::Critic, please consider pitching in and helping close some tickets. If you're not yet a user of Perl::Critic, today's a great day to start. I hope you love it as much as I do.
  • Perl 5 source repository now hosted in git

    Perl 5's source code is no longer locked into the odious proprietary Perforce repository where it's been hosted for years. It's now hosted in the git distributed version control system. This is a huge win. [The announcement](http://use.perl.org/article.pl?sid=08/12/22/0830205) lists a number of benefits: - With a public repository and Git's extensive support for distributed and offline work, working on Perl 5's source becomes easier for everyone involved. - Because Git is open source, all developers now have equal access to the tools required to work on Perl's codebase. - Core committers have less administrative work to do when integrating contributed changes. - Developers outside the core team can more easily work on experimental changes to Perl before proposing them for inclusion in the next release. - A vast array of improved repository and change analysis tools are now available to Perl's developers. - The new Git repository includes every version of Perl 5 ever released, as well as every revision made during development. Before this move, if you wanted to submit a patch to Perl 5, you had to submit the patch against bleadperl, the main development branch, which was an always moving target. The repository wasn't directly available, so you had to either keep your own repository that got updated with patches as they were applied, or just deal with your local changes getting stomped on. Now, that's all over. It's butt simple to get the Perl source:
    $ sudo yum install git
    (Your package manager may vary)
    $ git clone git://perl5.git.perl.org/perl.git
    (Time passes as much downloading happens)
    $ ls
    AUTHORS       configure.com    perl.h
    Artistic      configure.gnu*   perl_keyword.pl
    Changes       cop.h            perlapi.c
    That's it. Now you have a copy of everything, and can make patches much more easily. Thanks to Sam Vilain and everyone else involved in this huge move.
  • Booking.com puts their money where their infrastructure is

    [Booking.com](http://booking.com/), a global hotel reservation service based in the Netherlands, has [donated $50,000 to the Perl Foundation](http://www.hsyndicate.org/news/4039070.html) to help in further Perl development, specifically Perl 5.10. As Richard Dice, president of TPF says, "booking.com has demonstrated extraordinary vision and community spirit," but they also know that their infrastructure needs ongoing support. Their IT team is 50+ persons, and Perl is the "language of choice." Thanks to booking.com for this donation, and let's hope it is part of an ongoing trend. Now, if only TPF could get, say, $5 from every company that used Perl. Think how many programmer-years that could buy to help get [Rakudo](http://rakudo.org/) out the door.
  • How to spot bad Perl code, 2008 edition

    [Max Kanat-Alexander](http://max.kanat.us/) posted an article called ["How Not To Get Hired."](http://avatraxiom.livejournal.com/95669.html). Since I'm in the end stages of finishing [my book on geek hiring](http://oreilly.com/catalog/9781934356265/), I was hoping there would be swell interview horror stories. The first bullet talks about not following instructions in a job ad, but the rest is really a laundry list of Perl practices that nobody should be doing any more, and a few more on what we should be doing, starting with using Moose. I'm sure there'll be some crabs out there who say "Aw, that's just all common sense," but common sense rarely is. It's well worth a read.
  • Perl 5.8.9 is out

    Perl 5.8.9 is [available for download](http://search.cpan.org/dist/perl-5.8.9/). From reading the changelog, it doesn't seem like there's too much earth-shaking in it. There is a wonderful new utility added. An analogue to *perlbug*, the [new *perlthanks* program](http://search.cpan.org/~nwclark/perl-5.8.9/pod/perl589delta.pod#perlthanks) lets you send your thanks to the development team. What a great idea that is.