Migrating away from Sourceforge

Kyle Auble kyle.auble at zoho.com
Thu Jun 4 16:35:32 CDT 2015

On 06/04/2015 01:48 PM, Austin English wrote:
> 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.
One other thing still on SourceForge is part of the original CVS repo, 
which is empty except for the old version of the wiki. I still have a 
git repo with (AFAIK) the most recent version of the wiki at my 
Bitbucket account. I was going to ask at some point if everyone wanted 
it moved upstream to source.winehq.org, but now seems like an 
appropriate time.

I was waiting because it has a couple branches at the very end (for 
different upgrade paths on the server), but I guess those don't have to 
be cloned into the upstream repo. I could just keep my repo open in case 
Dimi wants to use those last patches to help with the upgrade. I tried 
emailing him a while back to see if I could do anything else to wrap up 
loose ends on the wiki, but he didn't reply so I figure he's busy.

- Kyle

More information about the wine-devel mailing list