Interesting idea, but falls short with any real use case IMHO.
Basically, it's unreliable, as anyone could just create its own private project and boost its own score secretly. Also, it doesn't show any "quality", just number of commits, which means nothing really.
But the idea itself is good!
I'd rather see something that is repository-based though, with a slightly different goal:
As OSS maintainer, I would like to show (e.g: in the README.md) all contributors to the project automatically, with statistics (like, the number of contributions and how recent was the last one?).
This would allow to highlight contributors, as per the initial goal.
Yeah, I know the commit points I was actually planning to change it to the number of lines but that would also result in adding unnecessary lines and option left would be the owner himself allotting points to the contributor which would result in much more work. I am also working on repository level grading. I would surely change the readme and update it with relevant information. Thanks
Number of lines isn't reliable either; some of the best improvements to code can result in a net loss of lines.
You may consider linking it to scores (managed with tags) on issues closed instead, using Gravity in Quantified Task Management for the actual scores. QTM was created for this exact purpose: to measure accomplishment.
Interesting idea, but falls short with any real use case IMHO.
Basically, it's unreliable, as anyone could just create its own private project and boost its own score secretly. Also, it doesn't show any "quality", just number of commits, which means nothing really.
But the idea itself is good!
I'd rather see something that is repository-based though, with a slightly different goal:
As OSS maintainer, I would like to show (e.g: in the README.md) all contributors to the project automatically, with statistics (like, the number of contributions and how recent was the last one?).
This would allow to highlight contributors, as per the initial goal.
Yeah, I know the commit points I was actually planning to change it to the number of lines but that would also result in adding unnecessary lines and option left would be the owner himself allotting points to the contributor which would result in much more work. I am also working on repository level grading. I would surely change the readme and update it with relevant information. Thanks
Number of lines isn't reliable either; some of the best improvements to code can result in a net loss of lines.
You may consider linking it to scores (managed with tags) on issues closed instead, using Gravity in Quantified Task Management for the actual scores. QTM was created for this exact purpose: to measure accomplishment.
Sure will check into it and make changes. Thank you for the Feedback