Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Don't give up just yet trying to contact the author. Ping the author again via email. Search other modules the author wrote to see if there's a more current email address. Try a web search for the author as well. Give yourself maybe another week after your best efforts at tracking down him/her.

If you still haven't heard anything by then, send mail to, or post to comp.lang.perl.modules, asking whether anyone is still claiming to maintain the module in question. If no one in those forums can vouch for someone currently owning and maintaining the module (after another reasonable wait, another week or two), then you can probably feel free to take over and upload a new version to CPAN yourself.

If you do, don't take this ownership lightly. If you're really going to take over, be prepared to field questions, fix bugs, etc., in the future. If you're not interested in doing that, but really just want to make your one fix available, then at least document the fact that the ownership is up for grabs, so the next person in your situation isn't left wondering like you are now...

(Eric Raymond covered this property/ownership aspect of open source software in his Homesteading the Noosphere, essay, which will be part of his eventual The Cathedral and the Bazaar book.)

In reply to Re: What to do when a module is no longer being maintained by knight
in thread What to do when a module is no longer being maintained by BlueLines

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

  • 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.