A peek at a new Sourceforge.net

So, I’ve been working on sf.net in various ways for about a year now.
http://sourceforge.net/p/. It’s written in Python using modern open source tools, from RabbitMQ, and MongoDB, to Git and Mercurial. And we are committed to making this the most open forge possible. We’re committed, to open processes, open code, and perhaps most importantly open data.

The first thing we did was create some new pages for downloads. Recently we releases a new service designed just for open source project leaders who want to use sf.net as a directory and downloads service.

But, we’re also aware that one of the most important services we provide is project hosting. For the last several months a small group of us have been trying to bring sourceforge.net’s tools into 2010. And now we’re releasing an early preview of those new developer/community tools:

We have a long way still to go, but every long journey begins with a single step, and today’s step is allowing you to try the new forge, to create new projects at:


Where you can go to get a new project, with our new tracker, wiki, git, svn, and other tools. Projects can have subprojects, and links to other tools hosted off site, along with the many features that sf.net brings (free web hosting, hosted apps, etc).

But, why do all this?

In 1999 SourceForge was cool.

It provided all the tools that an open source project needed to get going, from cvs hosting, to bug tracking, and e-mail list support.

They pioneered free free software project hosting, and helped to transform the software development culture from one which barely new about free software or open source, to one where nearly everybody I know uses open license software. Oh sure, some of them might not know it, but they have it on their phones, in their TVs, their wireless routers — not to mention all the websites they use everyday that run on open source.

But, time passed.

More alternatives came out, more projects (including my own) started self hosting, and the landscape of open source software development changed. SourceForge.net took a long time coming out with support for new tools like svn, and then git.

Still, SourceForge has a special place in my heart. Partly it’s nostalgia, I suppose, but I still think:

  • the core mission is still right
  • and there is still a real need

We (Open Source developers) still need tools like git, mercurial, and svn hosting. We still need bug trackers and mailing lists. And in a meeting of other open source project leaders last fall, nearly every single one of them identified the time wasted integrating and administering these tools as one of their most important frustrations.

Not enough…

But, for many sourceforge.net and other free project hosting services were just not good enough, they weren’t scriptable, the weren’t extensible, their data wasn’t portable, and so they felt like they had to take on that cost.

And I fundamentally believe that open source projects live an die by communication, and that sourceforge.net can do something new by integrating the various kinds of “conversations” that happen around the project. We can integrate mailing lists and forums, we can integrate SCM and ticket trackers, etc.

New and improved

So, a couple of us have been quietly working on something new. The new forge is designed around a few core ideas:

  • that data should be portable (every project gets their own database, which they can take with them if they want),
  • that the open source community ought to be able to extend and enhance the tools they need,
  • that integrating and cross linking the various kinds of conversations that open source projects need to have ought to be easier.

So, what we’re announcing today is more of a commitment to getting there on all these things, and a commitment to the “release early, release often” project management strategy.

So, expect us to take your feedback and make things better. Expect us to release lots of small fixes, and expect a few places where things are broken/incomplete because we value feedback more than polish at this point.

10 Responses to “A peek at a new Sourceforge.net”

  1. The thumbnail of the screenshot links to a thumbnail of the screenshot rather than the full-size version of the screenshot. I don’t think that’s what you intended.

  2. The registration link is also broken: there’s a “br” tag appended to the href.

    MARK: fixed now

  3. Nice write-up, Mark. It’s good to see Source Forge getting back to it’s old ways of openness, just like when Alexandria was a Free Software. Are you going to open the hood soon and let us see all the cool tech that you guys have been cooking to make it happen?

  4. 4Byro

    Great start, can’t wait till it goes live!

  5. I am *really* happy to see this happen. I, too remember when it was cool, and have been disappointed to see it atrophy.

  6. Are there plans to move back to a fully GPL’ed codebase, and perhaps reunite with forks like Savane / GForge, perhaps with the goal of being able to pool resources / development efforts?

  7. Jon,

    No, there is no plan to reunite with Savane/GForge/Fusion Forge etc. This is a new codebase in a new language, with a new architecture.

    We do intend to create an open and extensible system, and when the time is right we’ll welcome any efforts by anybody that’s interested in working with us. Unfortunately, that’s all that I can say right now, but I’ll be sure to blog about it when there’s more news.

  8. I remember reading SourceForge is about to use or already using TurboGears. Is this the project with TurboGears?

  9. 9Nebojsa Jovicic

    Hi, just a suggestion:

    Problem – Currenly I have to click on the name of the project on those “cards” to get to the project.

    Solution – It would be more intuitive to make the logo of the Project clickable as well. Or better, make the whole area from the name upwards clickable.

    Looks good thus far.

  1. [...] A peek at a new Sourceforge.net [...]

Comments are currently closed.