Module 3 Exercise 3: Assessing collaboration


(Patrick Reimers) #101

@ccannon94

It’s possible to see when and who worked on this project.

Example:
1 user commited ~80% of code, he/she might have done it alone.

Other example: A task was assigned on January 1st and they have to do it by March 31st. If they start commiting mid march, they properly didn’t do anything before.

I hope you understand what I try to tell you.


(Chris Cannon) #102

Perfect @PReimers, thanks!


(Pol Benedito Momplet) #103

Lots of pull requests active at the same time and lots of closed issues for the week.
It’s useful for analizing the amount of work that every contributor has done in the project.


(Chris Jones) #104

In most of the classes where I’m really using GitHub the teams tend to be self-directed. I mandate the sprint lengths and sometimes I mandate the sprint goals, but I let the teams manage their overall delivery schedule as they work toward an MDP at the end of the term. I’ll mentor them in terms of capturing velocity, determining realistic goals for the following sprint and encouraging them to find a cadence that’s sustainable for their team members. In some ways managing their overall expectations and contributions is the most challenging part.


(Chris Cannon) #105

That’s very cool @christopheralanjones. What is the experience level of this class? I’m just imagining my sophomores trying to manage and direct a project and it seems terrifying.


(Chris Jones) #106

It’s a combination, but generally these are seniors or masters students working on their capstone project. What better way to help folks understand agile frameworks like Scrum than to have them actually be responsible for its execution? At least in class mistakes have comparatively minor consequences, especially if a strong mentor-mentee relationship exists between the instructor and the students.


(Vasil Markov) #107

Whos of them are most committed in the project and how they contribute for it. How often they push etc…


(Antonio Gámez) #108

Chosen repo: https://github.com/OAI/OpenAPI-Specification

  • How quickly pull requests are reviewed: within days. There are more than 630 PR
  • Data in Insights : image
  • Number of forks or stars: 11,877 stars, 4,028 forks
  • Some other metric: 405 issues open, 707 closed; 1733 commits, 12 branches, 6 releases and 134 contributors

(Caponte94) #109

Select the django repository from @django, you currently have 23 extraction requests, 10 proposed extraction requests, 33 active extraction requests, no active problems.

37,570 starting forks and 16,210 , his last assignment was made today, the last throw requests was reviewed 4 hours ago.


(Thomas Sauerwald) #110

As a teacher i can use the statistics to see who is contributing to the project for real and who is just a member of the team, but is not coding at all. In addition i can see if the students followed their milestone plan, or just tried to make something up, just before the deadline of the project. So i can give them advice in how to improve their timing skills and become a better software developer.


(Paula Waite) #111

Here is an assessment of Wordpress/gutenberg.

The overal repository view shows a high number of contributors, commits, branches pull requests and releases, with a change as recent as a couple hours ago:

Digging further into the pull requests, we can see that the project is very active as there were several pull requests just today!

With regard to using Github to assess team work in my own classes, I think the number of commits, lines of code, and time line can be very helpful, but it’s also important to examine the actual work in those commits.


(Vladimir Jovanović) #112

Project that I looked into https://github.com/facebook/create-react-app/graphs/contributors

Proof that it is active:

Watching at the contribution metric data is interesting as it can show you just how much the project is active and who are the top contributors. The data is interesting, as the students can see how open-source community works and how a group of people can create an awesome project.


(Kevin ROBERT) #113
  • 20 commits the past week and the latest commit an hour ago
  • Pulse section shows 28 Pull requests merged by 21 people

Insights section is really helpful to asses collaboration in group work. I can check who and how team members are contributing to a project.


(Héricles Emanuel) #114

I believe the number of forks and stars show that the repository is famous, and many people try to contribute with it (visible by the number of contributors, PR’s and Issues). I believe that group work is frequent, since PR’s are reviewed quickly and there is always interaction with the community, in issues and PR’s.


(J Rice) #115

I like being able to click quickly on a student in the Insights section, and see which other repositories are consuming their time. I think this is a nice way to see if maybe one of the students is assisting another group, or spending too much time on personal side projects instead of the task at hand.


(John Isaacs) #116

Using “insights” to look at student work on a project last year. I like how you can see when and how ofter commits were made and by who. This is really helpful to determine who contributed to the project and who didn’t. The latest commits clearly show that the students have not been active on this project since the submission last year.


(Ethan McGee) #117

I used https://github.com/joncampbell123/dosbox-x for this portion of the assignment. We can see that the project is active because issues and pull requests are being resolved within a relatively short time span. We can also see that it is active because it has more than just a single contributor.

One of things that we can use here is the number of contributors to ensure that one student is not completing all the work himself. This is a major pain point among many of my group projects. being able to track who is working and submitting commits and the average size of each will help greatly.


(Bgarnb) #118

Assess a live project:

  • 4069 forks, 20242 stars, 17357 commits, and 737 contributors
    image
  • Reviews and merges for pull requests seem very often e.g.
    image
  • Data from Insights:
    Contributors:
    image
    Commits:
    image

I think this is a very big active project. The metrics from the Insights option could be used for assessing the group’s collaboration


(Chris Cannon) #119

How could metrics like this help you evaluate group assignments completed by your students @antgamdia?


(Chris Cannon) #120

That’s an interesting angle that I hadn’t previously considered. Thanks for that input @inoculant!