6 months is not a long time for an open source project me thinks. For example if your country has a Mandatory Military Service law, then you'll not be doing anything for at least 6 months (in Turkey this is upto 15 months if you did not graduate from collage). So, yes you can not know what the module author is dealing with. He can be ill, can have finance probs, $work can take all his/her time, he/she may even be dead (eg: Nick Ing-Simmons)

I think it's better to ask for co-maintainership if you think that the bugs are really critical and you can even take full control over a specific module if the author is abandoned it (I abondoned a module and gave the maintainer rights to someone else for example). Another option is asking a co-maintainer permission from PAUSE admins (you are not Andreas König right? :) if the bug is causing critical failures. I think this was done for Template Toolkit some time back...

If none suits you, you can always fork it and re-create Abc.pm as AbcX.pm and apply the fixes / release to CPAN if the license of the original module permits this.

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.