Re: Leveraging the Gitpan repos

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.

Comment on Re: Leveraging the Gitpan repos

Replies are listed 'Best First'.
Re^2: Leveraging the Gitpan repos by davido (Cardinal) on Aug 16, 2012 at 19:59 UTC
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. Dave	[reply]

Replies are listed 'Best First'.

Re^2: Leveraging the Gitpan repos
by davido (Cardinal) on Aug 16, 2012 at 19:59 UTC

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.

Dave

[reply]