It get's a little complicated, and it's still being tweaked, but goes something like this.
15 points for every text file changed, added or removed.
40 points for every binary file changed, added or removed.
1 point for every character in the commit message ( per changeset, not per file ).
1 point for every line added, removed, or changed from a file. This does NOT include cases where a file is removed, and another file added within the same changeset, so that file renamings etc don't get any points for increasing or decreasing code.
Then we take the net change and add that as well, so that net additions are boosted, and net removals are dropped, somewhat. This is usually not a big change.
Finally we cap the per changeset karma at 10,000, to limit the benefit of doing huge imports and such.
What this all means is that the following things help boost your karma.
1. Make your comments larger and more detailed.
2. Do your commits in smaller, more managable, chunks ( less per commit, but more total )
3. Use branchs, as you will get karma for the commits along the branch, and then more for the merge.
4. Manage a repository. If one person does the coding along a branch, and a different person does the merge, the person who does the merge will get a reasonably large amount of karma from doing the merge, although probably not as much as the person who did the coding on a branch. Also, the repository manager doing imports, re-organisations, and deletions tends to accumate a lot of karma.
5. Re-factoring. Although it doesn't increase the features or size, just changing and refactoring code accumates karma. This helps make karma a better indicator of "is an employee working" than just code size of feature count.
Of course, karma is exploitable. However, it's been designed intentially such that MOST of the ways of boosting your karma also happen to be good development traits ( those listed above ).
Hope that helps
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Heh. My karma is just slightly higher than my co-worker's. I think the difference is that he doesn't write commit comments and I do. Should I tell him that commit comments affect his karma? I think not... :)
(On second thoughts, I will, because his gigantic no-comment changes are driving me nuts)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How is karma computed in cvsmonitor?
It get's a little complicated, and it's still being tweaked, but goes something like this.
15 points for every text file changed, added or removed.
40 points for every binary file changed, added or removed.
1 point for every character in the commit message ( per changeset, not per file ).
1 point for every line added, removed, or changed from a file. This does NOT include cases where a file is removed, and another file added within the same changeset, so that file renamings etc don't get any points for increasing or decreasing code.
Then we take the net change and add that as well, so that net additions are boosted, and net removals are dropped, somewhat. This is usually not a big change.
Finally we cap the per changeset karma at 10,000, to limit the benefit of doing huge imports and such.
What this all means is that the following things help boost your karma.
1. Make your comments larger and more detailed.
2. Do your commits in smaller, more managable, chunks ( less per commit, but more total )
3. Use branchs, as you will get karma for the commits along the branch, and then more for the merge.
4. Manage a repository. If one person does the coding along a branch, and a different person does the merge, the person who does the merge will get a reasonably large amount of karma from doing the merge, although probably not as much as the person who did the coding on a branch. Also, the repository manager doing imports, re-organisations, and deletions tends to accumate a lot of karma.
5. Re-factoring. Although it doesn't increase the features or size, just changing and refactoring code accumates karma. This helps make karma a better indicator of "is an employee working" than just code size of feature count.
Of course, karma is exploitable. However, it's been designed intentially such that MOST of the ways of boosting your karma also happen to be good development traits ( those listed above ).
Hope that helps
Heh. My karma is just slightly higher than my co-worker's. I think the difference is that he doesn't write commit comments and I do. Should I tell him that commit comments affect his karma? I think not... :)
(On second thoughts, I will, because his gigantic no-comment changes are driving me nuts)