Conference Code of Conduct Considered Crucial

I’ve decided to follow Jacob Kaplan-Moss’s lead and pledge that I won’t speak (or attend) any conference that does not publish an acceptable (to me) code of conduct/anti-harassment policy. I’ve already written about what should go into such a code, and I think Jacob’s post makes a number of good points on why a policy is important. What would a code need for me to consider it acceptable? First, it needs to define acceptable conduct.

My Code is Now Mirrored on GitHub

Per the request of various folks, all of my code is now mirrored on GitHub. I’m still pushing to my personal server, but I’ve set up hooks to then mirror to GitHub. I’ll be happy to accept patches via a github repo and/or pull request. I wrote some code to manage the mirroring, which can be found in my git-bits repo. It’s not ready for CPAN, but it might be useful to others who want to do something similar.

Distros Which Need Some Love

I have way too many modules. Want to take one or two? Here’s some modules that I own (or co-own) that need some love: DateTime-Format-Mail - has some open bugs that could use some attention. DateTime-Format-MySQL - I may have a new maintainer lined up, but the more the merrier, I suspect. DateTime-Format-Strptime - I took co-maint on this to do a few quick fixes, but it could use more attention.

Conference Code of Conduct Considerations

A recent discussion on the YAPC::NA blog reminded me of the importance of having a code of conduct for conferences. I wrote about this previously in the context of creating a policy for my animal rights group. Now that the issue’s come up with YAPC, I’m thinking about what the ideal policy for a conference should look like. I do sympathize with people who don’t like these policies, and think they should be as short as possible.

Google Plus Circles Don’t Solve My Problem

When I first saw Google Plus circles, I thought this was a great idea. On Facebook, I have a bunch of “friends”, most of whom are people I talk to only rarely, some of whom I haven’t spoken to in years. With Google Plus, I can categorize these “friends” into different circles. How awesome is that? Most of the people I’ve had contact with on Plus are people I know through programming, so I made a “Geeks” circle and started filling it in.

Intro to Moose Class at Pittsburgh Perl Workshop 2011, Maybe

I’d like to offer my Intro to Moose class at the Pittsburgh Perl Workshop this coming October, but we’re not sure if there’s enough interest to justify it. If you think you’d like to take the class, please put your name on the Moose Class wiki page for PPW. This isn’t a binding commitment, but don’t sign up just cause you’re vaguely considering it. Some recent feedback about the class …

Perl 5 Core Principles

Way back when, the Perl (1, 2, 3, 4, 5) core was defined as “whatever Larry Wall says it is”. Since the advent of the Perl 6 project, Larry has spent less and less time on Perl 5, and he hasn’t been an active participant on the perl5-porters list for years. Absent Larry, I think the Perl 5 core would benefit from an explicit set of principles. I don’t get to decide what those principles are, but I have some suggestions.

Courriel: What and Why

I recently released new distribution on CPAN called Courriel. The word “courriel” is the official French word for email. I chose it because the Mail and Email namespaces are already very crowded, and there’s really no good namespaces left there. This gets to the why. Courriel is a distribution for processing and creating modern email. What’s modern? In ye olde dayes of RFC822 email, an email was a bunch of headers followed by a message for the recipient.

Flymake Versus the Catalyst Restarter

I recently started using flymake-mode in emacs, which does a “make on the fly” for the buffer you’re currently editing. For Perl, that basically means checking the code by running perl -c on it. If it sees any errors or warnings, it highlights this in the buffer. This is pretty handy for catching typos, although I’ve seen some weird false positive. Anyway, it’s a great tool, except that it does its checking by creating a file in the same directory as the one you’re editing.

Moose Class at YAPC::NA 2011

I’ll be offering a one day Intro to Moose class at YAPC::NA 2011 in lovely Asheville, NC. To register, log in to the YAPC::NA site and then go to purchasing page. If you haven’t registered for YAPC yet, you can buy your conference ticket at the same time too. Intro to Moose Join us for an interactive hands-on course all about Moose, an OO system for Perl 5 that provides a simple declarative layer of “sugar” on top of a powerful, extensible meta-model.