Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
well I got a short question,
basically I got 4 projects, wrote some reviews, are a very active developer to these projects and my cudo rank keeps and keeps dropping.
How can it be that somebody with 0 commits, 0 project keeps increasing his rank and my rank keeps dropping?
I honestly don't care much about this, just think that's a pretty weird behavior.
link?
Hi Gert,
Kudos come only from other developers. Just writing code is not sufficient to receive Kudos.
Your KudoRank will increase when other Ohloh members give you Kudos, or add your projects to their stacks.
hi robin,
yes this makes sense, but han how can a person have an increasing rank without any projects?
For example look at this link:
http://www.ohloh.net/people?show=14765
user:
Gert Wohlgemuth
Contributes to: BBCS, binbase, JaCuda, and pycuda
Kudo Rank
KudoRank 1
Kudo Position:
122280
Position Gain:
-844
rockyshark
Kudo Rank
KudoRank 1
Kudo Position:
122278
Position Gain:
+732
now can the second person gain 732 points, if he contributes to nothing?
My guess is that new developers get added all the time. So kudos position get bumped up?
i had the same idea, but than it would be for everybody equal more or less.
and new developer should be added at the end of the list.
@Gert,
Interesting -- I never noticed this behavior before.
The problem is that you and everyone in the list around you all have a kudo score of 0. We have thousands of people like this.
Since the list is sorted by kudo score only, the sort order for everyone with score 0 can change indeterminately every time the list is recalculated. However, the underlying rank scores are actually not changing.
We can add a secondary sort key to prevent this from happening.
Robin
ok thanks, as I said I was curios about this and you don't have to change anything for me :)
(ok gimme a cudo for logical thinking :P)