Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • While I'm currently in a badly overloaded period, and not doing my shift on as a module@ person until late next month, the standard for contacting authors I generally ask people to apply is "several times over several weeks by several methods". It's not a hard and fast rule, but it works in most cases.

    That is, you try to contact the author a number of times by various email accounts you can find (because sometimes ones might go dark) over a period of time, and look for any other avenues you have to hunt them down (Instant messenger, Skype phone, land line telephone, etc).

    Sometimes it's obvious they are gone. For example, in one case last year the author had only every released one module 5 years ago, and was now the CIO of a fairly large company.

    And yes, having no action on their CPAN account for 3 years despite bug reports hanging around is a pretty good sign. And most of the time, once you track the author down they'll either fix the bugs now you are squeaking, or be happy for you to take over maintainership.

    And if you can't, give me buzz via my cpan.org address and I'll sort it out for you.