Judging about code-curiosity

[anujaware]

Scoring can not be done only on number of lines changed. There are other factors need to be considered like sometimes for small change you need to learned a lot if its a large repository and when it affects in so many places. Or sometimes large number of lines may not be that valuable. Also we may need more numbers (score) for judging ;)

[gautamrege]

@anujaware This is not automated scoring but a guideline. The judging is for the scoring not the learning. So initially you will take a lot more effort and have very little to show for it but if you are consistent with your work on that repos - the scores will get bigger as you will make larger fixes!

5 is enough for a score range - we were contemplating 4 (like a GPA) but have kept it to 5. We need to minimise discrepancies. Of course, in due course if we deem fit, we shall increase the range.

[anujaware]

👍

[anilmaurya]

2 Minor code change will give me 2 + 2 = 4 points.
1 feature will give me 4 points.

Its very easy to make 2 minor change Vs 1 feature.
Indirectly code curiosity is encouraging minor changes instead of feature building.

I support 0-9 scoring range .

[gautamrege]

@anilmaurya We are scoring each commit and it's highly unlikely that you have a feature with 1 commit. (if that is the case, I'm not sure that would be considered a feature. If you had 1 commit with 4,000 lines of code, chances are it's going to be rejected anyway).

So, for a feature, you may have 10-15 commits with various ranges of scores.

[pramodshinde]

👍 @anilmaurya - Its not always true that feature have 10-15 commits, many times authors asks to quash the commits for feature as well.

[gautamrege]

well said @pramodshinde We need to think about how to score squashed commits.

The thing is that we know that the squashed commit has multiple commits in it - but how will we judge that? Do we keep a "multiplier" element in scores if we detect squashed commit? Of course, if the user deletes the squashed commit details from the comment, there is nothing we can do about it.

@jiren, thoughts ?