I'm not sure whether all of my previous messages regarding the SourceForge outage got through, so forgive me if any of this is old news.
Let me start by saying that I think (hope) that the rumors of SourceForge's demise have been greatly exaggerated. They have largely owned up to their mistakes regarding the DevShare program and have taken steps to mitigate misleading ads (i.e. ads with fake download buttons) that were being served up by Google. I also feel that they handled this outage in the best way they could. I've been using SourceForge since 2004-- you know, back when they were in pretty much exactly the same position that GitHub is in now. I've been around this block enough times to be wary of jumping onto the latest & greatest platform just because it's the latest & greatest. That being said, while I have had no major issues with SourceForge (before now), this outage made me finally admit that the advantages of a DVCS (such as git) far outweigh the pain of learning a new system. To that end, I took advantage of the downtime to get familiar enough with Git that I can be productive with it. When our subversion repository came back online on Sunday, I immediately started the (somewhat painstaking) task of migrating our code to GitHub. I could just as easily have migrated it to SourceForge's Git or Hg servers, but I am a believer in using the best tool for the job. Part of maintaining a healthy open source community is making it easy for developers to contribute, and GitHub's popularity and rich collaboration tools make it a clear winner in that department. The code migration is now complete, and you can find our main repository at: https://github.com/VirtualGL/virtualgl Supporting repositories (build scripts, etc.) can be found at https://github.com/VirtualGL Please update any sandboxes you may have. The subversion repository is frozen and will eventually be decommissioned. The following provides a comprehensive list of project services and where to find them, going forward: -- Code hosting: GitHub only (https://github.com/VirtualGL/virtualgl) I double-checked and triple-checked the new repository against the old, but please let me know if you find any issues with it. -- Issue/feature tracking: Either GitHub (https://github.com/VirtualGL/virtualgl/issues) or SourceForge (https://sourceforge.net/p/virtualgl/_list/tickets) There are advantages and disadvantages to both (for instance, you can't attach files with GitHub), so for the time being at least, use whichever one you prefer. I have moved the open feature requests to GitHub, but all other items are still on SourceForge. If, at some point in the future, the SourceForge tracker stops being used or the GitHub tracker improves its feature set, I will consider freezing the SF tracker. -- Patches: Either GitHub (https://github.com/VirtualGL/virtualgl/pulls) or SourceForge (https://sourceforge.net/p/virtualgl/patches/) If, at some point in the future, the SourceForge tracker stops being used, I will consider freezing it. -- Official Releases: SourceForge (https://sourceforge.net/projects/virtualgl/files/) My automated pre-release and release scripts are heavily tied to the SourceForge file release system, I like certain features of that system (such as the statistics it provides), and there are a lot of links to those files out there, so at least for now, I will continue using SourceForge to distribute official releases. I will, however, sign all RPMs and DEBs on that site with my GPG key and all Windows installers with my code signing certificate, in order to ease any concerns about binary tampering. Look for a follow-up message announcing the completion of that project (SourceForge has not yet restored the file upload and SSH features, so access to the file release system is currently read-only.) This article http://michaeltunnell.com/blog/15-miscellaneous/53-14-potential-alternatives-to-sourceforge-for-binary-downloads echoes my thoughts on the decision to stick with SF for file releases. Note that GitHub includes metadata and automatically-generated tarballs for all of the release tags (https://github.com/VirtualGL/virtualgl/releases.) For VirtualGL 2.0 and newer, these tarballs should match the ones on SourceForge (the pre-2.0 tarballs on GitHub are missing the license files, due to an issue with the old CVS repository that was never resolved prior to converting it to subversion.) -- Web site: hosted on an external web server (http://www.VirtualGL.org) All of the links mentioned in this message can be found there. -- Mailing lists: SourceForge (https://sourceforge.net/p/virtualgl/mailman/) -- Discussion forums: SourceForge (https://sourceforge.net/p/virtualgl/discussion/) As always, please send me any questions or concerns you may have. DRC ------------------------------------------------------------------------------ _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
