Libre Software People's Front

don't confuse it with People's Front of Open Source

What do you need to be the developer #1 in

with one comment

Something is wrong with the way sort the developers by meritocracy. Well, uses Kudos to measure it, the definition that they offer for kudo is:

kudo: a statement of praise or approval; accolade; compliment.

Basically, kudos are a public way to show your appreciation or respect for an open source contributor. Remember that meritocracy is a very important part of the motivation to work in libre software projects. According to the explanation by the ohloh staff, contributors who have received the most Kudos will receive the highest KudoRank of 10 and only the 64 top people can receive the highest KudoRank.

Once the concept is clear, let’s have a look at the top ten contributors according to ohloh (based on the Kudos they’ve received). The top 3 committers according to the Kudo Rank are Jari Aalto, zeljic and Stefan Küng (see image below).

Now, let’s compare the first three contributors. If we add up the values of the two first committers (Jari Aalto and zeljic) we have 21 commits, 2 years of experience and 6 kudos received. On the other hand Stefan Küng, who is the third contributor, has received around 100 kudos (you’ll have to count them manually), has coding experience of 8 years and 9 months and is part of 15 software projects. The obvious questions is, what is wrong here?. The first two committers have not claimed the ohloh account for this contributions, could it be the root of the bug?

I think this is a bug, I’ll let the Ohloh staff know. Stay tunned.


Written by sanacl

January 4, 2012 at 12:21 am

One Response

Subscribe to comments with RSS.

  1. Interesting article.
    I think the “problem” is how kudos are given and calculated in Ohloh: not only directly from developer to developer, but also when somebody clicks “I use this” in a project, all of their contributors receive kudos proportionally to their number of commits. So if you are a small contributor of a project which many ohloh users “use it”, you get maybe more kudos than a big contributor to a project “less used”. Here Robin Luckey explains it:
    In addition to this, when a contributor gives “kudo”, the less kudos she gives, the more influence she transmit to the kudo-given developer. Here Robin Luckey explains it as well as other Kudo rating internals (the problem of sparse data, and others).
    I also used Ohloh kudos ranking in my writings about FLOSS leaders, but now that I have read about it a bit, I regret it, its algorithm does not match with my views about “popularity”.
    Thanks for this awakening!


    January 11, 2012 at 12:32 am

Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: