Project migration to GitHub in progress !

Here’s what’s left to do in the Sourceforge->GitHub migration:

  • Trac documentation => Updated version on GitHub (16 February 2013 : Pursued work on RAM manager page, added a page for PIDs, updated index to reflect latest changes, other minor fixes)
  • Trac milestones and issues => GitHub bugtracker (31 October 2012 : Sourceforge content has been fully backed up)

3 thoughts on “Project migration to GitHub in progress !

  1. Amenel September 9, 2012 / 4:10 pm

    I didn’t know Sourceforge was so ailing.

    GitHub seems to be THE next big thing. I keep wondering “What’s with GitHub?”.

  2. Hadrien September 9, 2012 / 5:45 pm

    Well, I’d hazard a guess that people like GitHub because it is one of the few free open-source project hosting service whose CMS does not look and feel like a Geocities website. Google Code is not bad either on this front, but its UI design has more rough edges and not everyone want to put his project in the hands of Google…

    The GitHub guys obviously have taken quite a bit of time to figure out what would be the minimal feature set for such a service, and have polished most of these features until they would shine instead of spreading too much their effort*. They have also somehow managed to fund the service without covering project pages with ads, which makes navigation more pleasant.

    Also, some people just love git, and GitHub offers better integration with its features (with a way to visualize code branches, “pull requests”, and stuff like that).

    As for SourceForge themselves, their CMS used, until recently, to be not only relatively slow, bogged down with ads and confusing, but also really short on development tools like bug trackers with milestones and project wikis. It mostly focused on final software distribution (with screenshots, a review system, a way to provide direct access to binaries in an arch-dependent way…), not the former parts of the development cycle. SourceForge compensated for this by providing projects with a few web apps like Trac, called the Hosted Apps, that could be set up in a few clicks from the project administration panel. Recently, however, they have decided to shut down that service and include the relevant functionality back in their CMS.

    Now, I can understand why they did that. And they have indeed done some good work during the last few months with the new version of the CMS : faster page loads, less confusing settings, and finally some dev-oriented features. What pisses me off, however, is the way they have handled the whole transition. Essentially, back in July, I have received a mail stating that they were shutting the service down in early September, that they had no migration plan ready yet but hoped that they could come up with one in the remaining weeks, and that it was up to us to do the hard work. Since then, they have recovered some sanity and pushed the deadline back by a few months, but the fact that they have left the remains of the service rot and could even imagine that this could work made me lose all confidence which I had left in them.

    * Well, except for the “Pages” one, used to build custom project websites, which is truly some awful abuse of git’s branching capabilities.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s