I'd suggest one of two options:

Do as ichimunki suggested and release the code as a separate module. The suggestion of MP3::OpenNap was a good one. This gives the end user the choice of which module to use.

Release a patch.

Whatever you do, don't release that submodule if what you're really doing is rewriting large portions of the internals. Submodules (IMHO) should only use the standard documented interface of the module, inless you're explictly putting the module in ISA, in which case all bets are off (and even then, I'd still recommend using as much of the documented interface as possible).

In reply to Re: a question of utility and ethics... by Hrunting
in thread a question of utility and ethics... by deprecated

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.