Earlier quoted context omitted.
This was in progress, 830GB was downloaded before a Sourceforge guy popped onto the IRC and said he's ok with the archiving, but that the robots.txt should be respected. This would put things at a practical standstill. So the downloading was paused, I'm not really sure what's happened in the week since. Right now Xfire's videos, several URL shortners' links, and Toshiba Support material are being archived. If you hav…
Honestly I think ignoring robots.txt in this case is acceptable. Even if he programs in code to respect robots.txt - once the management at sourceforge get wind of what he is doing - what is stopping sourceforge from putting up robots.txt everywhere blocking him?
Show HN: Effort to clone unmaintained SourceForge projects to GitHub
81–90 of 90 posts
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#82Please add "SVN" (Subversion)
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#83Why 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
This was in progress, 830GB was downloaded before a Sourceforge guy popped onto the IRC and said he's ok with the archiving, but that the robots.txt should be respected. This would put things at a practical standstill. So the downloading was paused, I'm not really sure what's happened in the week since. Right now Xfire's videos, several URL shortners' links, and Toshiba Support material are being archived. If you hav…
So the mirrors should just cut the upload write permission for Sourceforge and transfer it over to archive.org or ArchiveTeam.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#84Earlier quoted context omitted.
All of your criticisms of Savannah seem oriented around aesthetics rather than its actual functionality. Personally I don't need much eye-candy for a git host because 99% of my work is done from the command line, but even if I cared about that I'd still pick Savannah over SF any day of the week.
I thought this had been resolved years ago, but aesthetics aren't about eye candy. They are about productive and pleasant experiences. As a tangible example, imagine yourself working in a dank, contaminated 6' diameter sewer pipe with spotty pirated electricity, vs. a well-designed, large interior space with plenty of natural light and reliable utilities. Regardless of how irrelevant appearances are to you, I'd wager…
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#85Note 1: Moving things to GitHub or elsewhere does not remove them from SourceForge. So SF can continue to host and enjoy links on unmaintained websites, search engines etc. Note 2: If their business model is offering popular binaries and source, they can just copy these from other sites and repackage them. Open source software allows you to do this. If no one else is interesting in bundling and monetizing, then they…
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#86Earlier quoted context omitted.
I thought this had been resolved years ago, but aesthetics aren't about eye candy. They are about productive and pleasant experiences. As a tangible example, imagine yourself working in a dank, contaminated 6' diameter sewer pipe with spotty pirated electricity, vs. a well-designed, large interior space with plenty of natural light and reliable utilities. Regardless of how irrelevant appearances are to you, I'd wager…
That's a terrible example and it doesn't address my point at all.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#87What about creating a torrent containing all these unmaintained SF projects (with binary downloads included)? This would dramatically increase the odds that the content is never lost.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#88Earlier quoted context omitted.
Ten years from now for all we know we could all have so much cheap storage and bandwidth and good, open p2p software that all coders get to archive their own full copy of github's repos. So the focus should be on getting today's job done now.
> open p2p software that all coders get to archive their own full copy of github's repos Do you mean git?
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#89What about creating a torrent containing all these unmaintained SF projects (with binary downloads included)? This would dramatically increase the odds that the content is never lost.
The problem with torrents is the lack of incremental update support. If the base torrent gets updated it gets a new hash identifier. How do you know its been changed to ensure you get the latest version. When you do the swarm effectively gets diluted because some are on the new architecture and some are on older versions.
Re: Show HN: Effort to clone unmaintained SourceForge projects to GitHub
#90Earlier quoted context omitted.
That's a terrible example and it doesn't address my point at all.
It does actually. UX, aesthetics, all of it is important and stuffing your head in the sand saying "Hey, I don't care about aesthetics, I just use the command line" is a very irresponsive attitude.