Most here are probably familiar with the gitpan repos: https://github.com/gitpan. My question is this: What is the best way to make this project meaningful?

It seems like a lot of work went into pulling all of the modules in the Gitpan project into public repos. But the work was done a couple of years ago, and the repos are aging; I don't think that newer and updated modules are finding their way in (contrary to what's mentioned in the Gitpan README), and existing modules are more current either on CPAN or in authors' own public repositories. Many authors have their own preferences that don't include git. And even those who use it mostly ignore the gitpan project. It seems to me that the current situation is at least undesirable if for no other reason than it contributing to confusion as to what repo an interested party ought to be looking at.

There must be a way of making this monumental effort worthwhile. One thought was that authors or maintainers with their own repos could issue a pull request against the gitpan repo whenever it makes sense. But this requires two things: (1) Authors/maintainers will have to know to do it, care to do it, and remember to do it. (all three are probably unlikely) (2) Pull requests aren't even enabled for the gitpan modules, from what I can determine. That feature would need to be enabled.

So are these repos destined to grow increasingly outdated and increasingly irrelevant? Is there something we can and should be doing to make them a useful resource?


Dave

In reply to Leveraging the Gitpan repos by davido

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.