Thread: [Under consideration] Developers should get karma based on the relevance of their software
View Single Post
attila77 is offline attila77
2009-09-13 , 11:37
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#61
Originally Posted by qgil View Post
Could you please submit the idea?
OK, let's just clarify a few things beforehand, as there is no edit.

It seems that we can keep the ratio 100 downloads = 1 karma for these peaks? If v1.0 gets a peak 1000 downloads you get 100 karma points. If v1.1 gets a peak of 1500 you get 150 instead of 100. But if v1.1 gets a peak of only 200 then you get 20 instead of 100. Makes sense.
Not sure if it's just terminology, but I strongly suggest peak volume instead of peak value. It would be a shame to loose karma because your peak was at night (split across two days), influenced by day-of-week, holidays, etc.

BTW, you say 100 : 1 but the ratio is 10 : 1 karma in the examples

Can someone clarify the X axis relation in the graphs (Niels) ? I can see the data points are weekly, but I don't know if it means the value is SUM of dowloads that week, just a snapshot for a single day or daily AVG for that week which might influence karma multiplier choice... Or, if it is possible, could I get daily resolution data for a project just to see clearer ?

About updates being too close - this is actually not that big of a problem as I initially thought. It is on the current graphs as you can't differentiate between versions, but since these ARE separate files, they might just as well be statted separately for karma purposes.

Here's another graph, this time for OMWeather - it has updates more often than mapper so you can see the principle even better:
Attached Images
 
 

The Following 6 Users Say Thank You to attila77 For This Useful Post: