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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Take a deep breath (Score:2)
As a module author myself, I try to respond to all problems as quickly as I can. However, it's not part of my job and it's not very high on my life priorities. Although I try to be helpful and timely, I feel absolutely no obligation to respond to bug reports, fix modules, or otherwise do anything that's less important than whatever I decide I would like to do, including sitting on my ass and watching TV.
Now, that being said, if a module author has gone missing, the PAUSE admins (of which I am one) can re-assign the module to an interested maintainer. Short of that, if you find the author doesn't respond to you and the module hasn't been updated, you don't have much risk in patching your local copy and getting on with life. Although informal, the system has worked out very well.
Sure, you may be annoyed that something goes unfixed. I'm quite sure you'd be more annoyed with having to do without it completely.
Have you ever considered the possibility that your social skills might be part of your frustration? I certainly wouldn't respond to you if you wrote to me in this manner.
Reply to This
Re: (Score:1)
At work, we do patch, subclass, and work around bugs. But nobody else ever sees those fixes. That is why users should have the courtesy to report bugs and ideally fix them. The maintainer should have the courtesy to respond. In the easy case, they check and apply the pa
Re: (Score:2)