I chose to examine
broom. From the insights tab I can see there are several active issues and pull requests. There are also hundreds of stars and forks, indicating the project is active and frequently utilized (not surprising, as it is a major package in the
While the majority of the commits are written by a handful of authors, there are also at least 20 authors with only 1 or 2 commits. These probably come from pull requests for minor changes to the codebase, indicating project managers are open to incorporating improvements from a wide userbase.
This could be useful to assess collaboration in a class group setting, perhaps by examining frequency of commits from different students, activity responding to issues and pull requests. Of course, this also depends on how frequently students stop and commit file changes. One commit could be extremely minor or containing major changes to the codebase depending on if the student follows best practices. It would still be better to examine the underlying codebase and commits/PRs independently for each student (if this is feasible for the class size).