Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,131 | Comments: 45,565

filter by tags archive

Open Source Success Metrics

time to read 4 min | 667 words

I got into a very interesting discussion with Rob Conery recently, talking about, among other things, the CodePlex Foundation. You can hear it TekPub’s Podcast #2, when it is out later this week. Tangential to our discussion, but very important, is how an Open Source project owner defines success for their project.

Usually, when people try to judge if an open source project is successful or not, they look at the number of users, and whatever the general response for the project is positive. But I am involved in a lot of open source projects, so you might say that I have an insider’s view on how the project owner view this.

Now, let us be clear, I am talking about OSS project that are being led by an individual or a group of individuals. There are different semantics for OSS projects that are being led by a company.

There are several reasons for individuals to be involved in OSS projects, those are usually:

  • Scratch an itch – I want to do something challenging/fun.
  • Need it for myself – This is something that the owner started because they needed it themselves and open sourced it for their own reasons.
  • Reputation building – Creating this project would give me some street cred.
  • I use it at work – Usually applicable for people joining an existing project, they use it at work and contribute stuff that they require.

We must also make a distinction between OSS adoption and OSS contribution. Typically, maybe a tenth of a percent of the adopters would also be contributors. Now, let us talk about the owner’s success metric again. Unless the owner started the project for getting reputation, the number of people adopting your project is pretty meaningless. I think that DHH , the creator of Ruby on Rails, did a great job describing the owner sentiment:

I'm not in this world to create Rails for you. I'm in this world to create Rails for me and if you happen to like that version of Rails that I'm creating for me, than you are going to have a great time.

Even if you are interested in OSS for reputation building, after a while, it stops being a factor. Either you got your reputation, or you never will. A good example of a project started to gain reputation is Rhino Mocks. And you know what, it worked. But I think that it is safe to say that I am no longer just that Rhino Mocks guy, so the same rules applies as for the other motivations.

So, what does it mean, from an owner perspective, when you ask if an OSS project is successful or not?  The answer is simple: it does what I need it to do.

I asked a popular OSS project owner the following question: What would your response be if I told you that I am taking a full page ad in the Times magazine proclaiming your stuff to be the best thing since sliced bread? You’ll get a million users out that that.

His response was: Bleh, no!

Tying it back to the discussion that I had with Rob, I feel that much of the confusion with regards to the CodePlex Foundation role is when you try to talk to projects led by individuals as if they were commercial enterprises. The goals are just completely different, and in many cases, adding more users for the project will actually be bad for the project, because it put a higher support cost for the project ream.

In the .NET ecosystem, most of the projects aren’t being led by a company. They are led by individuals. That is an important distinction, and understanding it would probably make it clear why the most common response for the CodePlex Foundation was: What is in it for me?


Dario Solera

Some random thoughts from the trenches.

As you noticed, there are three types of OSS projects:

  1. company-funded, necessary for the company's business (or at least for getting visibility) or complimentary to it (e.g. they sell support)

  2. individuals-led, done for fun or need.

I think the most successful and big projects of type (2) eventually turn into type (1). If a project has thousands of users and requires constant active development, the management overhead starts to becoming too big or, alternatively, causes the project to grind to a halt.

Attracting developers is another matter altogether. In my experience it's much harder to attract developers for projects that target end-users, while it's a lot easier when the product is a dev tool.

On the other hand, it's hard to keep the feature set consistent and the goals defined when you have a lot of contributors (look at PHP6).

I personally still have to learn how to manage my project, as there are a lot of things that are simply beyond my comprehension. So far, I learned to say no and to do a strong triage on feature requests, which is a start.


Dario - What's the 3rd type of OSS project?


there are 3 types of people in the world, those who can count and those who can't.

Dario Solera

He he, I can't seem to count one-two-three...

Comment preview

Comments have been closed on this topic.


  1. RavenDB Conference 2016–Slides - 15 hours from now
  2. Proposed solution to the low level interview question - about one day from now

There are posts all the way to Jun 02, 2016


  1. The design of RavenDB 4.0 (14):
    26 May 2016 - The client side
  2. RavenDB 3.5 whirl wind tour (14):
    25 May 2016 - Got anything to declare, ya smuggler?
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series



Main feed Feed Stats
Comments feed   Comments Feed Stats