Show HN: Effort to clone unmaintained SourceForge projects to GitHub
a-sf-mirror.github.io
Show HN: Effort to clone unmaintained SourceForge projects to GitHub
1–10 of 90 posts
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#2Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#3Nice! But in my opinion better help archiveteam with their efforts!
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#4Nice! But in my opinion better help archiveteam with their efforts!
[1]: http://archiveteam.org/index.php?title=SourceForge
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#5Nice! But in my opinion better help archiveteam with their efforts!
I confess my ignorance regarding archive.org's various collections. There seem to be a lot of them, which one are you referring to?
The best place to pop in is probably on IRC. For the Sourceforge project it's #coldstorage on EFnet, http://chat.efnet.org:9090/?nick=&channels=%23coldstorage&Lo... for the web client. Though note, the ArchiveTeam project seems to be paused right now.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#6Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#7In 10 years time, Github may be the tired old service that gets acquired by a hedge fund that decides to monetize their repos. Such things are part of the corporate lifecycle.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#8Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#9For CVS, though, I suspect cvs-fast-export [1] will do a better job than git-cvsimport.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#10Why Github? Copying from one commercial provider to another doesn't solve the fundamental problem. Using git helps, but most of those old repos will never get cloned. In 10 years time, Github may be the tired old service that gets acquired by a hedge fund that decides to monetize their repos. Such things are part of the corporate lifecycle.
At least with a commercial entity there is a bit more "trust" involved that they won't disappear out of the blue one day. And if the time comes that Github starts to collapse, the process can be repeated.
Just because something isn't permanent doesn't mean it's pointless.