GatorEducator
Add a feature to analyze commits for each member of a team
It would be useful if it was possible to analyze how the individuals in a team contributed to the submitted solution. The idea would be to continue to use the GitPython tool to extract the commit history for a team's Git repository. Then, you could use this history to see how many commits were made by each member of the team. Finally, you could look at the "size" of each commit by determining the number of lines inserted and deleted as part of each commit. This blog post outlines some of the code that we would need for this feature: https://bbengfort.github.io/snippets/2016/05/06/git-diff-extract.html.
Just as a note, @Michionlion and @castellanosr, I do not plan to finish this feature by the time that the academic semester starts. However, I could imagine that it would be useful to have this feature in place by the time that we start running group projects at the middle and end of the semester.
Hello @blackeuler, yes, this is a desirable feature. With that said, right now I would place it at a lower level of priority than some of the other issues in the issue tracker. There are at least two reasons for this: (i) while there are certain courses that have a lot of team-based projects, there are other courses that have little team-based work and (ii) several other contributors have suggested that it is really difficult to have an objective measure of the contributions of the individuals in a team. How would you implement this feature? What is the timeline by which you think that you might be able to have a working prototype? Finally, it is great to hear from you again! I hope that you are doing well!
Also, @blackeuler here are two issues that I would rank as more important than this one:
#207 - if there was a tool to generate a GatorGrader configuration based on an existing project, that would be awesome! #215 - I'm not sure (yet) if this is a defect in GatorGrader's Python source code or in the Java-based Gradle plugin. But, multiple people have now replicated this defect, which would be great to fix!
Okay, please let me know what you think! Thanks!
If this is not a high-priority feature I will work on something else, I hadn't thought in implementation details yet. I saw this was an open issue with not much discussion so I thought I would inquire. I will look at issue #207 that looks interesting. Thought I would help out over the winter break.
Nice hearing from you as well.