• Help end licensing under “same terms as Perl itself”

    I've posted before about the problems with "same terms as Perl" licensing, not the least of which is the question "which version of Perl are you referring to?" I bet that most people who use "same terms as Perl itself" used it for the same reason I did: because it was the easiest way to do it, and I was lazy.

    So to help out my lazy sisters and brothers in Perl, here is a block of POD that you can go paste into your modules right now, all formatted and pretty.

    =head1 COPYRIGHT & LICENSE
    Copyright 2005-2009 Andy Lester.
    This program is free software; you can redistribute it and/or
    modify it under the terms of either:
    =over 4
    =item * the GNU General Public License as published by the Free
    Software Foundation; either version 1, or (at your option) any
    later version, or
    =item * the Artistic License version 2.0.
    =back
    

    You'll want to change the "Andy Lester" part. I don't want to take credit for half the CPAN.

  • Perlmonks users, your passwords have been published

    Just in case you missed my Tweets about it, or don't read any other Perl blogs, or didn't receive the mail sent out from Perlmonks, Perlmonks was compromised. Passwords for users were published to the net. Carl Masak has this [analysis of the passwords](http://use.perl.org/~masak/journal/39373) and their weakness. It's clear, too, that many of the passwords were standard passwords meant to be used on multiple sites.
  • Updates to perl-begin.org

    Shlomi Fish wrote in to tell about updates on the site for Perl beginners with which he's involved:

    After the last news item, a lot of work was invested into Perl-Begin.org, the Perl Beginners' Site, making it even better than it used to be. Here's a summary of the changes:

    We hope you enjoy the new Perl Beginners' Site and please recommend it to your friends. All content on Perl-Begin is made available under the Creative Commons Attribution Licence which allows almost unlimited re-use.

  • My to-do list always grows post-OSCON

    Every year at OSCON I come home with a head full of ideas, and better yet, a huge list of new things to work on. Since [the book](http://www.pragprog.com/titles/algh/land-the-tech-job-you-love) is now done, and OSCON is now over, there's a chance I could work on them. * Ack plug-ins * I've been wanting to have plug-ins for [ack](http://betterthangrep.com/) for at least a year now, and I've connected with a number of people like Randy J. Ray who are on board to help me out. First task: Move it on over to github. * Coverity scans for Parrot * Met with David Maxwell of [Coverity](http://coverity.com/) and he fired up the Coverity bot for Parrot, and now I have new niggling bugs to pick at. * PR work for first big release of Rakudo * There will be the first major release of [Rakudo](http://rakudo.org) in spring 2010, and I got some plans going with Patrick Michaud to figure how we were going to build up buzz for that. I also have the notes from Damian's Perl 6 talk which are a fantastic summary of Perl 6's cool new features. * Human Creativity * Julian Cash has been having Jos Boumans do all his Perl work for the [Human Creativity](http://humancreativity.org) project, but I offered up my services to do whatever he wants. Turns out the Julian is also working with Devin Crain, who I've known for years in an entirely non-geeek context. * Hiring horror stories * Got some great response to [my talk on job interviewing](http://en.oreilly.com/oscon2009/public/schedule/detail/8074), and as always the stories resound the most. I talked to a few people afterwards who said they'd give me some horror stories I can run on [The Working Geek](http://theworkinggeek.com) as instructive examples of how not to do things, and why they're so awful. For those of you leaving OSCON, what tasks did you just assign yourself in the past week?
  • Quickies from Wednesday, OSCON 2009

    I'm sitting in the communication lobby on the fringe of the p5p meeting discussing potential ways of doing releases for Perl 5. It's quite a brain-dump of Perl 5 names: Chip Salzenberg, David Adler, Patrick Michaud, David Wheeler, Robert Spier, Paul Fenwick, Jacinta Richardson, Tim Bunce, Michael Schwern, Ricardo Signes and Jesse Vincent. Here are twelve brilliant programmers in the Perl world, and they're talking about a rancorous topic, but there's no anger, no animosity. The talk is honest and frank, but the benefit of having everyone present is clear. It makes me happy to see. In sessions today, Jacinta's survey of Perl frameworks was great, in that it was pragmatic and aimed directly at the programmer wondering "What should I do my next talk in?" I skipped out early on Tim Bunce's Devel::NYTProf talk, but I've seen a couple of tweets being very impressed with it.