I would think at the very least I should update it and push up a new version with my contact information in place. Obviously credit needs to be maintained with respect to the original author. What should be changed? What should be left alone?

I recently took over Log::Dispatch::Win32EventLog. I added my name and contact info on the top of the AUTHORS list, but also updated the installation style to work with Module::Build, included a META.yml etc.

Of course, I took it over to fix some warnings related to newer versions of Perl and update the test suite. (Which led to finding more subtle bugs....)

I did update the documentation with some things that I thought needed explicit mention, and rather shamelessly added reference to another module I wrote with overlapping functionality to the SEE ALSO section.

What I meant to do but have just realized that I did not do, was to put a link to rt.cpan.org for reporting bugs, rather than to have people send E-mail to me. That's the best way since there's a list of outstanding bug reports and feature requests.

I did not remove references to the other authors, since they put a bit of work into the original. Nor did I update the wording on the license.

In reply to Re: Adopting Modules by rrwo
in thread Seekers of Perl Wisdom by PublicAccess

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.