comment on

You make it sound as if the author owes you something.

CPAN is a volunteer operation, people donate code in the hope that it will be useful. Yes, it's rude not to acknowledge a bug report or patch, but there are any number of reasons: people may be too busy, the e-mail forwarding address may be obsolete, the author may have lost interest. It takes discipline to manage CPAN modules correctly and so it's only natural that there's a certain amount of attrition over the years.

If you have made a concerted effort to get in touch with the author (and ranting on Perlmonks doesn't count), can show that you are able to close out most, if not all, bugs on the RT queue of the distribution, then send a message to module-authors@perl.org documenting this, and you will be granted co-maint status on the module. This happens all the time.

• another intruder with the mooring in the heart of the Perl

In reply to Re: Losing faith in CPAN - unresponsive module authors by grinder
in thread Losing faith in CPAN - unresponsive module authors by andreas1234567

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks