I am very impressed with the significant amount of due diligence you've done here trying to sort this out. It reminds me of me in my early days.

You are exceptionally articulate, detailed (yet quite concise), big-picture/long-term thinking and respective of prior art. This is very impressive.

My gut says that with all the thought that went into just figuring out if you should extend a current namespace, you should come up with your own (under "PDF"), that doesn't include any acronyms that aren't particular to your distribution. I also think that you should request MAINT access to the existing distribution; not necessarily for updating it, but perhaps to update the README so that it claims the old software as either A: deprecated (because your software is backward compatible) or B: antiquated (because your software does *most* of what the older one does, but maybe not everything), either/or with a link to your distribution.

I stood on my head for my first couple of CPAN releases, waiting for feedback from others on how I should proceed. I was scared shitless. I was afraid of infringing on other's distribution names, their work, and perhaps mostly, breaching the conduct of creating a new CPAN name for my work.

Don't overthink it. You've worked overtime to ensure you're within the guidelines, and you've gotten wonderful feedback from many people.

Just do it. Get your distribution up there in what makes you feel best, and be very proud to be an official open source Perl CPAN contributor!

-stevieb

In reply to Re: Choosing namespace/name for (my first) CPAN module which is a sub-class of a well-known distribution by stevieb
in thread Choosing namespace/name for (my first) CPAN module which is a sub-class of a well-known distribution by Anonymous Monk

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.