Github is catching up fast as the preferred destination for CPAN module development. But I wonder: Have we agreed yet on how to name our projects? Shouldn't there be a de-facto standard?

Obviously there's no such thing yet, as there is

http://github.com/gisle/libwww-perl

which is the true name of the CPAN module (indeed, the distro name is called "libwww-perl", which is very unusual for CPAN), then there is

http://github.com/mschilli/log4perl

which uses a short (but unambiguous) name and

http://github.com/boumenot/p5-Net-Amazon

which adheres to the RHEL/FBSD school of thought. Another possibility would be the Debian way, something like "libnet-amazon-perl".

Clearly, there should be a "-perl" (or -cpan) suffix (or prefix) to distinguish CPAN modules from the same projects, written in a different language.

Thoughts on a naming standard?

In reply to CPAN Modules on Github -- Naming conventions? by saintmike

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.