As a software developer I’ve been using SourceForge for around six years now (I believe I joined in 2009). I’m using it to help develop and distribute dispcalGUI, an open source graphical user interface for Argyll CMS aimed at display calibration and characterization, utilizing these free services:
▪ Version control
▪ Hosting of binary and source code downloads over a distributed network of mirrors
▪ Support forums
▪ Issue tracker
▪ Mailing lists
▪ Wiki
The latest development is that the current owners of SourceForge, DHI Group (the former Dice Holdings, which had acquired SourceForge from GeekNet in 2012), is looking to sell off its Slashdot Media assets, which includes SourceForge. It’s too early to really tell what this means for its future, but nevertheless, I’m keeping an eye out for alternatives, and if SourceForge should cease to be an option for one reason or the other, I will be forced to move elsewhere—even considering self-hosting everything I need if I really can’t avoid it.


Es gibt viele Möglichkeiten, die Performance einer Website zu verbessern. Neben der Optimierung von Bildern, HTML, JavaScripts und StyleSheets sowie Kompression ist sowohl browser- wie auch serverseitiges Caching (das Vorhalten von Daten in einem Zwischenspeicher) eine gute Option.
Zur deutschen Version dieses Artikels
To conserve bandwidth and speed up page loading, it pays off to also compress static files like stylesheets and scripts in addition to the page itself with GZIP and set meaningful cache retention times. With Apache, this process can be set up with a custom .htaccess file as dynamic on-the-fly compression with either mod_deflate, or alernatively via PHP. In my case I settled with a PHP solution which stores the compressed data on disk, so repeated requests don’t cause the files to be compressed over and over again, but only on first access (or if the file has changed).
View english version of this article