Advertisement
Tag Archives: myths

More of our favorite Sourceforge myths

After my article about Sourceforge myths a few days ago, several of the engineering and support team told me about other myths that they hear on a regular basis, so here’s a quick followup.

We’re not Open Source

Actually, Sourceforge itself is Open Source. About a year ago we launched a rewrite of the base Sourceforge dev tools, and they were Open Source from day one.

That rewrite is called Allura, and it’s under the Apache License. It’s an ongoing effort, so there are parts of it that are not yet under that Open Source umbrella. But we’re getting there, and it’s our goal to have the entire site running on Open Source components.

It’s hard to upload files

Like many of the complaints about Sourceforge, this one comes from many years ago. I guess that people used Sourceforge long ago, and assumed that nothing has changed since then. Not a very sensible assumption, if you stop and think about it, but one that most of us make at one time or another about something we used, once, long ago.

Uploading files is done via a standard HTTP file upload form. You know how to use those.

add_file

There’s also a button to add a folder inside the current folder, if you want to arrange your files into folders. That’s pretty easy to use, too.

add_folder

In the old days, you had to use FTP or SCP to upload your files, and it was a little cumbersome, but those days are long past. Of course, if you still want to use those methods, those tools are still available, too.

We have anti-Iran export controls

Sourceforge is a US company, and, as such, is subject to US laws. One of those laws restricts the export of certain types of software to certain places.

When you register your project, we ask you if your software is one of those types. Specifically, it looks like this:

export

It is a legal requirement that we ask you this. If your software doesn’t fall into that category, you need to select no to that question.

If you don’t select “no”, then folks in Iran (and various other countries) won’t be able to download your project. This is not because we hate Iran, but rather because of the above-referenced law.

That was then …

Most of the myths about Sourceforge come from memories of long ago. Unfortunately, it’s awfully hard to dispel what people think they know. Take a look at Sourceforge now, and you’ll find that we’ve come a long way since those days.

We’re just as dedicated to Open Source as we’ve ever been, and we’re actively using our own tools to develop the next generation of the site.

The Top Myths About SourceForge

Since starting at SourceForge about a month ago, I’ve been paying close attention to media and Twitter mentions of SourceForge. I’ve been astonished at the sheer volume of misinformation that’s just accepted as fact. I suppose when things are said often enough you just can’t help but believe them. Here are some common myths about SourceForge.

You have to use CVS

Sourceforge has offered Subversion for many years – pretty much since Subversion was available.

But we’ve also offered Git for many years. We had Git long before Git was cool. In fact, Git is the default when you create a new project. And, the Sourceforge codebase itself (Codename: Allura) is developed in Git. On Sourceforge. The Sourceforge code is released under the Apache Software License (ASL2) and is just as free as everything else on Sourceforge.

Much like another popular code hosting service you might have heard of, our Git implementation provides one-button forking, and one-button pull requests.

Oh, we offer Mercurial (hg) hosting too, if you prefer.

SCM options

We do, in fact, still offer CVS, but only to support older projects that haven’t gotten around to migrating yet – and there are a few. We’re available to help you migrate between various different SCM solutions, if you need that help.

New projects have to be approved

Long, long ago, we required that new projects be approved. This was a spam prevention measure. I remember those days, vaguely. That was at least four jobs ago, and a lot has changed since then. These days, creating a new project takes less than a minute, and does not involve any approval step.

You can’t customize your website

One default Sourceforge project site looks like another. But you have the option of creating a virtual host where you can put up a site that looks like whatever you want. Virtual hosts have tools you’d expect from a typical webhost, including php and mysql, but you can also install a variety of other things in order to make your project website whatever you need it to be.

We’ll answer requests for any hostname you have registered, as well as for PROJECTNAME.sf.net, and you can have up to ten virtual hosts per project. You then have access via your login shell to update those sites.

Sourceforge Is Dead

Ah, yes, the standard tech meme of announcing the death of whatever it is that you don’t like. As usual, it’s somewhat exaggerated.

We have almost 3.5 million registered users. The number of projects on Sourceforge is right at 325,000, and continues to grow every day. The existing projects continue to develop software, committing over 5,000 changes a day, closing tickets, and pushing out new releases, every day. And visitors from 40,000,000 unique addresses visited the website last month, downloading releases more than 4,000,000 times a day.

And Google seems to think we measure up pretty well to those other hosting sites. (via @robilad)

Google site stats

Meanwhile, yes, there are a lot of dormant and abandoned projects. This is also the case at Google Code, GitHub, and any other code hosting service you care to think of. It’s the normal lifecycle of Open Source software that some projects fall by the wayside because they are done, and there’s nothing more to do. Also, some end because the developers lose interest and move on, while others do because something else has been created that obsoletes it.

It is natural, and expected, that an older code hosting service will have a larger number of abandoned projects than the newcomers. We’re working on some ideas of community health metrics so that you can more quickly identify whether a particular project is active or not, while still keeping around the older projects that someone might still find useful. And we already incorporate project activity into search result ranking, so that these less active projects won’t be the ones that you find, most of the time, when you’re looking for software.

So, we think we’re pretty much alive, but we’re not resting on our laurels. The engineering team is working constantly on the platform, making it work better, look better, and scale better. And, for the criticisms of Sourceforge that are true, we’re working hard to correct them.

We think it’s worth your time to look into Sourceforge for yourself, and not just accept the myths.