Get it while it's hot (and Plack is certainly hot):
Gentle into to Plack.
OK. So I've installed almost every one of my modules, to check each Build.PL is up-to-date.
Now I can process every Build.PL and send thanx to the authors whose modules I use, using perlthanks, a version of perlbug.
But it hangs. I'm running it in test mode, i.e. outputting the 'mail' to a file, before doing anything silly like sending real, live, email. And this is from within a script, using `perl...`.
Turns out that when you use perthanks (I did not try perlbug - but see below), and you use test mode (-F), and you specify the body on the command line (-b), it ignores the -b and stops to ask you for the path to your editor, so you can enter a body! Grrr.
OK. So I write the body to a file, and use -f to feed it back in. It works!
Off go 159 emails. Let me know if you received yours.
Now to file a bug report on perlthanks. But the program 'knows' perlthanks is not a core module, so recommends trying to log a bug report via RT.
But on RT a search for perlbug fails.
Ah well, like perlthanks itself, it's the thought that counts.
I could have said something like 'CPAN Rules!', but of course you knew that.
After an exchange of emails with Matt "The Enforcer" Trout
If you're looked at CGI::Office::*, there are some things to be aware of:
o The namespace prefix has changed (obviously).
o The directory names have changed, for CSS and HTML template files, from
o The contents of the config files have changed, where they contain the directory names in the last point.
Yes, folks, it's finally happened:
CGI::Office::Contacts, CGI::Office::Contacts::Import::vCards, and CGI::Office::Donations have been uploaded to CPAN.
Well, not today, but in a few days I'll release:
and shortly thereafter:
Sigh. After proof-reading 'take 2' several times, and posting it, it has vanished , so now it's 'take 3':
Thanx to daxim for valuable comments on omitting any discussion of the http method names. I've put a new section in the doc, near the front, spelling out what I intend the doc to cover.
And thanx for Aristotle for valuable comments on the phrase RESTful urls. I've wiped out all trace of that phrase, which means even the disk file name has changed.
 I should have expected that, since it almost always happens at weekends, although you'd like it to not happen at all...
Well, no word from Perlsphere, so here's the first in the series:
I've written 420 lines (incl blanks) on the second article, but there's a way to go yet...
After a few detours, I'm slowly building the free time to start blogging on what I've been doing with Perl over the last few years.
I'm going to call my series 'Perl@Work'.
I've almost finished the first article, and have 3 more in mind. These stories are all utterly different from each other, which is one thing about programming I find fascinating.
My first plan for publishing was to go to the Perl Foundation's web site  and search for 'advocacy'. I expected to find a place to submit stories, but couldn't see anything.
Then I tried their wiki . Probably the section 'Who uses Perl?' would be the place to put a link to my stories.
But the question remains: Where to blog?
Like many, I'm not happy with use.perl.org, although I do appreciate the effort that's gone into it over the years.
I like the look of Perlsphere  so that's where I'm headed, if they'll have me
If not, I'll be back soon.