Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Leveraging the Gitpan repos

by davido (Archbishop)
on Aug 16, 2012 at 18:11 UTC ( #987849=perlquestion: print w/replies, xml ) Need Help??
davido has asked for the wisdom of the Perl Monks concerning the following question:

Most here are probably familiar with the gitpan repos: 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?


Replies are listed 'Best First'.
Re: Leveraging the Gitpan repos
by jdporter (Canon) on Aug 16, 2012 at 18:27 UTC

      Great link! At least at the moment I think it's safe to say that Gitpan isn't "competing", since it seems to have dropped out of the competition a couple years back. ;)


Re: Leveraging the Gitpan repos
by chromatic (Archbishop) on Aug 16, 2012 at 22:55 UTC
Re: Leveraging the Gitpan repos
by jgamble (Pilgrim) on Aug 16, 2012 at 19:52 UTC

    I believe the point was to give those of us with long-standing packages a leg up on transferring our code to github. After all, some of us had many, many versions to transfer if we were going to do that, which was something of a barrier to starting.

    So, a big thank-you to Schwern, who is indeed responsible for getting me onto github.

      That does make sense. The README suggests that the goal was originally to also continue pulling new versions as they get uploaded to CPAN, and that seems to have not happened. ...and as the links others have provided explain, one big reason is how labor intensive the existing methods are; there lacks a fully automated process.

      I can see how, even in its current condition, it can be helpful to an author who wants to pull old history into his own current repo. Perhaps the best thing that can be done to make Gitpan more useful in the short-term is to bring the README more up to date.


Re: Leveraging the Gitpan repos
by Anonymous Monk on Aug 16, 2012 at 18:30 UTC

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://987849]
Front-paged by bulk88
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (2)
As of 2018-01-24 02:36 GMT
Find Nodes?
    Voting Booth?
    How did you see in the new year?

    Results (255 votes). Check out past polls.