Does CPAN need a facelift?

If it wouldn't be a fact that almost every time A Grand Idea thunders into my mind and, after quickly searching CPAN for such, I'd find that this Grand Idea had already been conceived, put into coding action and completed with the result of Some::Fine::Module, and if I were only a bit ahead of my time, I would have long ago written a vim macro which does make, make test, make clean, make dist and post it to CPAN by just issuing

:publish

in vim, which does all PAUSE interaction in a neat perlish way, using LWP, WWW::Mechanize and whatnot.

And I would have extended that to also check whether that module is mine or somebody elses, and derived from that whether to just commit or issue a pull request and whatnot. Maybe I'll do that some day and publish the result here or elsewhere, but for now that isn't anywhere on my workbench queue.

Do I need JavaScript or fancy CSS to install Modules? No. Why should I need such to publish? There's perlbug to report perl bugs, mailing lists etc. Why should I use a browser?

So, no, CPAN doesn't need a facelift. It doesn't even need to have a face. It lives because of its content.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

In reply to Re: Efforts to modernize CPAN interface? by shmem
in thread Efforts to modernize CPAN interface? by nysus

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.