Yeah, I remember us discussing this at the time. It was opt-in, and I remember thinking that if I ever used an open source project that did opt-in, I'd immediately switch to a competing open source project, but until and unless Sourceforge somehow required projects to use their build tools to insert extra stuff not controlled by the project itself into binaries, it was completely irrelevant to THIS project.
That opinion stands. I don't see how their "anti-consumer practices" have anything to do with us using them as a svn server for source code. Doubly so for ASH scripts which will don't even HAVE a "binary" form to download.
Now, if they start to require all source code hosted on their site to use the GPL license - rather than Berkeley (as we do) or Apache, or the non-virus license of the project's choice - THAT would be a reason to cease using them for SVN.
Given the recent (and current) Sourceforge downtime, I'd like to resume this conversation, but in a separate thread. I don't have much faith in a service that reports updates more or less every twelve hours, and only has part of the problem addressed more than 48 hours after the initial report.
One alternative that's been discussed is for fewyn to set up a svn server on the same server that hosts kolmafia.us.
I've considered trying to setup an SVN server for usage here but I've yet to find a software package which would make managing them not a pain in the rear. If anyone has seen any I'd be open to giving it a try.
Some googling revealed the following options that provide a web interface for SVN repository management:
- VisualSVN; Windows-only.
- SCM-Manager.
- Several other projects hosted on Sourceforge, which, surprise, are currently unavailable
SCM-Manager looks like it'd fit our needs rather nicely. I literally downloaded the package, unzipped the tarball, and ran bin/scm-server, and I had a server running on localhost:8080 in a matter of seconds. The getting started page may also be of some use (namely, initial user / password).