Whither SourceForge?

oliver on 2009-08-17T14:14:36

Every day, it seems, another Perl module is posted up to GitHub. Collaboration, of course - great stuff!

But it got me thinking about why everyone is settling on GitHub. Surely not just the fact it's all web two point oh, combined with groupthink. What happened to poor old SourceForge, the previously canonical location for open source software on the web?

I wanted a bit more infrastructure for one of my own CPAN hosted modules, so went to look at GitHub. The first thing which struck me was the lack of mail list support, so in fact GitHub turned out to be a non-starter.

Having not visited SourceForge in a while, I found the site has had quite a nice front-end facelift, along with a bunch of new features.

Yes, there is actually git support (and bazaar, svn, mercurial, cvs). There's also a wiki, forums, image gallery, issue tracker, blog, and much more, if you want.

So I was left feeling a little underwhelmed by GitHub, but SourceForge at first glance seems to offer all the infrastructure I need instead.

Any comments on what I have missed? Would anyone who consciously chose GitHub over SourceForge like to comment?


I find SF too messy

pshangov on 2009-08-17T16:29:56

SF has been undergoing a lot of positive changes lately. It is the only open-source hosting solution that provides all the features you need under one umbrella - version control, timeline, support forums and mailing list, bug tracking, website hosting, etc. Also, it can provide a lot of visibility by occasionally listing your project or news in a prominent location such as its front page.

The downside for me is that the user interface is pretty messy and not as polished as in most modern two point oh apps. I am currently facing a similar dilemma and I am not yet decided if I will go for SF or use a combination of several tools (github for version control and issue tracking and google groups for support).

Re:I find SF too messy

oliver on 2009-08-17T17:36:46

Fair point, although it's not as ad-cluttered as it could be, for what I pay for it ;-)

I hope that most interaction will be via mail list, git/svn commands, and so on.

I also like that SF can host a full custom homepage for the project - that's always been a nice touch.

Thanks for the comment!

Re:I find SF too messy

Aristotle on 2009-08-17T19:59:59

I also like that SF can host a full custom homepage for the project

GitHub Pages.

Re:I find SF too messy

Dom2 on 2009-08-17T17:38:09

I use both github and google code for one of my projects. It works, and I like both, but if I were starting again from today, I'd be a lot more tempted to settle on just github. Purely from the consistency of having a single site for users.

Re:I find SF too messy

Tadman on 2009-08-18T15:39:23

I've always loathed SF and I might even go so far as to say I hate it. Every trip to SourceForge to get something I needed was one filled with frustration, disgust, and irritation, as something as simple as finding a module or downloading a file was always a process of figuring out where to ask, what to click on, and, even then, of digging through several pointless layers of garbage simply to get to the destination. It's like they're hurting for page-views and will do anything to increase them.

GitHub serves as an example of making the same process much easier. You search, you copy, you clone, you're done. A lot can be learned from the way they have things organized.

I have to say their current re-design of SourceForge has advanced the site around the level of TUCOWS in 1999, which is a step forward, though still so awful as to require goggles. I understand that many developers have zero or negative design sensibility, but are designers so hard to find?

In much the same way Digg trumped Slashdot, GitHub has likely overtaken SourceForge for the simple reason they have gone to great lengths to consider the usability of their product. I'm sure if SourceForge took the same approach they could do wonders with the massive archive they have.

On a related note, it is interesting that this site still requires the injection of HTML to get a simple comment to format. I feel like I'm in a time machine.

SourceForge is not about people

Aristotle on 2009-08-17T19:53:22

What you missed on GitHub is:

  • You can watch repositories and follow people
  • Every repository has a [Fork] button
  • Creating a new repository has minimal cognitive load (3 text inputs and away you go) compared to SourceForge project creation; also, last I knew, SourceForge tried to encourage you to find and join a similar project instead of starting your own

GitHub is MySpace for Hackers. It’s about coders and the stuff they do, throw-away hacks and big projects alike, not about faceless projects run by barely identified contributors.

(And in any case, regarding your knock-out criterion, last I looked at the SourceForge mailing list web archives, they blew chunks. Admittedly that was a long time ago and maybe they’ve overhauled that part. But I never had much interest in the site anyway, and only ever used it out of necessity.)

Re:SourceForge is not about people

oliver on 2009-08-18T06:09:49

There seems be a lot more to it than just the tools, I think you're saying. This is really useful stuff, thanks for taking the time to respond.

You mention the SF mail list sucks - no argument there! - but all I want to do really is replace the CPAN Forum, which sucks even more than that!

Git support on Sourceforge is very minimal

grantm on 2009-08-17T20:56:59

Yes, Git support was added to Sourceforge recently, but the support is very minimal - one repository per project. I like to use one repo for the project itself and another for the web site. Some projects (e.g.: Perl-XML) use the CVS modules facility to have one repository per distribution. Subversion kind of supports this through its "tag-isa-branch-isa-module-isa-directory" model. In Git you could have completely independent branches for different purposes but that just seems wrong.

Re:Git support on Sourceforge is very minimal

grantm on 2009-08-25T01:19:06

It looks like SourceForge have fixed this problem and now projects can have multiple git repos. Unfortunately at this moment all git URLs on their site are broken as what was git://project.git.sourceforge.net/gitroot/project should now be: git://project.git.sourceforge.net/gitroot/project/project

Different Goals

erikh on 2009-08-18T05:18:38

I think of the two having different goals.

Github is a code repository, where SF.net, search.cpan.org, rubyforge, etc, are release repositories.

f.e., I release my code on both CPAN and Rubyforge and use the trackers there to deal with things (Rubyforge has list support, and TBH I have nothing on CPAN to warrant a mailing list so it's never crossed my mind to check).

When I want to develop, or share test/beta versions, or share a hacking assignment on one of my projects with an interested developer, Github is a preferable alternative because all the tools are there to share code. I was previously hosting all my repositories myself, which didn't lack due to uptime/accessibility issues; but the UI on Github just makes everything easier, from being able to instantly fork repos to using gist (a pastebot), and actually being able to clone the results from the pastebot and merge/hack on them.

HTH.

Re:Different Goals

oliver on 2009-08-18T06:05:16

That does help, many thanks!

For me it's about control

david_on_cpan on 2009-08-18T06:26:15

Sourceforge is traditionally a CVS/SVN host. I liked hosting my CVS and SVN repos myself because it's not easy to clone them and I didn't want to give up control of my change history to a third party. I saw lots of projects on sourceforge but I never ever considered using it myself.

Since github is git based, this is no longer an issue. It costs me nothing to push my stuff up to github--I always end up with a full repo in my local copy. No history or metadata is out of my reach. I believe they even use git for their custom web pages--meaning even your project docs and such are similarly protected.

With github you won't lose anything if they go out of business or become evil.

Mailing lists

petdance on 2009-08-18T17:09:25

the lack of mail list support, so in fact GitHub turned out to be a non-starter

Why does the mailing list need to be hosted at the same place the code is?

I have a number of projects floating around and they all use Google Groups for the mailing list, whether or not the code is hosted on any given Google property.

Re:Mailing lists

oliver on 2009-08-18T18:30:59

Yes I was coming to the same conclusion myself - using GitHub (which seems to have been given the thumbs up all round, here, in the comments) and then putting the mail list elsewhere.

I'd like to do this only once, and get it right first time. Moving lists around is annoying.

Thanks for the comment.