Migrating away from Sourceforge

Austin English austinenglish at gmail.com
Thu Jun 4 14:48:06 CDT 2015

Howdy all,

I noticed there was some discussion of this on #winehackers a week or
two ago, but I haven't seen any formal discussion about it. Given
SourceForge's recent activities [1] [2] with taking over open source
projects for their own gain, I propose that we migrate away from
SourceForge. The main uses for SourceForge is for mirroring tarballs,
wine-gecko/wine-mono installers, and the wine-gecko git repository.

@Jeremy, would it be feasible for winehq's (existing) servers to
handle the additional load?

[1] http://www.extremetech.com/computing/206687-sourceforge-accused-of-hijacking-gimp-photo-editor-company-claims-project-was-abandoned
[2] http://www.extremetech.com/computing/206687-sourceforge-accused-of-hijacking-gimp-photo-editor-company-claims-project-was-abandoned


More information about the wine-devel mailing list