Migrating away from Sourceforge

Jeremy Newman jnewman at codeweavers.com
Thu Jun 4 15:02:16 CDT 2015

On 06/04/2015 02:48 PM, Austin English wrote:
> 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.

I second this proposal.

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

The hardware can handle it just fine. The problem comes down to 
bandwidth. The server is on the same pipe as the CodeWeavers server. If 
it starts to cut into our cap, it can make the staff (marketing in 
particular) grumpy.

A better solution would be to setup a mirrored CDN. The CDN could mirror 
the http://ftp.winehq.org/ file structure. CodeWeavers uses CDNetworks 
for our CDN and have been pretty happy with them.


More information about the wine-devel mailing list