Earlier quoted context omitted.
Do you have any other suggestions? Hosting these repos on donated/personal machines is (IMO) significantly less likely to stand the test of time. 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.
> Do you have any other suggestions? Archive.org ? And weird that nobody suggested the Bitcoin block chain. I don't think binaries are a good fit but source code doesn't require a lot of space. With the current and future block size it will take sometime to make it happen.
Show HN: Effort to clone unmaintained SourceForge projects to GitHub
21–30 of 90 posts
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#22Nice! But in my opinion better help archiveteam with their efforts!
Agreed. This article sounds more like an advertisement for GH. Also, why not using other platforms like bitbucket? Centralizing everything at GH is the worst scenario for open source.
Gitlab has a community edition, and then there's Gogs, Kallithea and a few others.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#23Why 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.
Do you have any other suggestions? Hosting these repos on donated/personal machines is (IMO) significantly less likely to stand the test of time. 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.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#24Why aren't you mirroring the binaries? These are vital for people in the future who do not have the time to set up a build environment for software from a decade ago. I'd also echo the concerns of others about GitHub. Proper archivists should do for SourceForge what they did for other projects. Archive Team, maybe? Looks like they have a wiki page: http://www.archiveteam.org/index.php?title=SourceForge
Regarding binaries, I know these could be useful and I'd like to provide them, but I'm afraid some "not (yet?) very popular mirroring project" can't show how we can trust it regarding binaries. After all, a known site like SF is untrustable, so why would an unknown site would be more?
I think you're taking the right approach by capturing the code and the history. In fact, I think you're going above and beyond what most people should ask for or expect.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#25This seems much more like a temporary fix, not really a solution. A few years from now GitHub can do the same thing that sf did. This after all seems to be the fate of commercial companies that explore open source, once they start to lose users to new competitors.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#26Why 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.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#27Earlier quoted context omitted.
> Do you have any other suggestions? Archive.org ? And weird that nobody suggested the Bitcoin block chain. I don't think binaries are a good fit but source code doesn't require a lot of space. With the current and future block size it will take sometime to make it happen.
Archive.org (while an amazing resource created lovingly by amaing people) is not a great front-end for stuff like this. Github is very easy to get started with and excels at code hosting. As for the blockchain that's a terrible idea, there are so many things wrong with it including the cost to push all of that data into the blockchain and the fact that while source code can be small it isn't always and it's magnitude…
I said: With the current and future block size it will take sometime to make it happen.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#28Earlier quoted context omitted.
Regarding binaries, I know these could be useful and I'd like to provide them, but I'm afraid some "not (yet?) very popular mirroring project" can't show how we can trust it regarding binaries. After all, a known site like SF is untrustable, so why would an unknown site would be more?
Yes, this is a more challenging and potentially risky one. I think you're taking the right approach by capturing the code and the history. In fact, I think you're going above and beyond what most people should ask for or expect.
http://sourceforge.net/p/forge/documentation/Join%20as%20a%2...
http://sourceforge.net/p/forge/documentation/Mirrors/
I bet at least one techie working at one of those organisations would lend a sympathetic ear to the effort, if you could find them
edit: running 'rsync -r' on a local mirror shows 512,000 directories from a..ju, but only 43k files. Mirroring all the downloads should be easy
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#29Why 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.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#30Why 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.