| Your team name | Team to review 1 |
|---|---|
| seniors | the-outliers |
| the-outliers | team-e |
| team-e | juniors |
| juniors | team-c1 |
| team-c1 | nico-val-rian |
| nico-val-rian | glam |
| glam | seniors |
Peer review
Milestone 4
Project
Important
You must attend this lab in person and participate in the peer review in person to be eligible for the points for this milestone. Team members who are not in lab in person for this milestone will not be eligible for these points, regardless of their contribution throughout the rest of the project.
During the peer feedback process, you will be provided read-only access to your partner team’s GitHub repo. You will provide your feedback in the form of GitHub issues to your partner team’s GitHub repo.
Goals
The goals of this milestone are as follows:
- Review others’ project drafts as a team and provide feedback
- Post issues on GitHub using an issue template
- Learn from others’ projects and improve your own project based on their strengths and weaknesses
Instructions
Review one other teams’ project. As a team you should spend ~30 minutes on the review.
Find the names of the team whose project you’re reviewing below. You should already have access to this team’s repo.
Each team member should go to the repo of the team you’re reviewing.
-
Then,
1-2 team members clone the team’s project and renders it to check for reproducibility.
1-2 team members open the team’s project in their browser and starts reading through the project draft.
1 team member opens an issue on the team’s repo using the peer review template.
All team members discuss the project based on the prompts on the issue template and one team member records the feedback and submits the issue.
-
To open an issue in the repo you’re reviewing, click on New issue, and click on Get started for the Peer review issue. Fill out this issue, answering the following questions:
Peer review by: [NAME OF TEAM DOING THE REVIEW]
Names of team members that participated in this review: [FULL NAMES OF TEAM MEMBERS DOING THE REVIEW]
Describe the goal of the project.
Describe the data used or collected, if any. If the proposal does not include the use of a specific dataset, comment on whether the project would be strengthened by the inclusion of a dataset.
Describe the approaches, tools, and methods that will be used.
Provide constructive feedback on how the team might be able to improve their project. Make sure your feedback includes at least one comment on the statistical reasoning aspect of the project, but do feel free to comment on aspects beyond the reasoning as well.
What aspect of this project are you most interested in and would like to see highlighted in the presentation?
Were you able to reproduce the project by clicking on Render Website once you cloned it? Were there any issues with reproducibility?
Provide constructive feedback on any issues with file and/or code organization.
What have you learned from this team’s project that you are considering implementing in your own project?
(Optional) Any further comments or feedback?
Review pairings
| Your team name | Team to review 1 |
|---|---|
| the-rchitects | team-awesome |
| team-awesome | something-down |
| something-down | standard-deviants |
| standard-deviants | merge-conflict |
| merge-conflict | the-outliars |
| the-outliars | three-of-a-kind |
| three-of-a-kind | stat-legends |
| stat-legends | the-rchitects |
| Your team name | Team to review 1 |
|---|---|
| r-squad | mdc |
| mdc | forkball |
| forkball | render-me-that |
| render-me-that | all-in |
| all-in | stats-stars |
| stats-stars | matcha |
| matcha | r-warriors |
| r-warriors | data-dudes |
| data-dudes | r-squad |
| Your team name | Team to review 1 |
|---|---|
| s-tier | pushing-n-praying |
| pushing-n-praying | ae-cc |
| ae-cc | dejjp |
| dejjp | jacksons-mommys |
| jacksons-mommys | pumpkin-rolls |
| pumpkin-rolls | lebronisticians |
| lebronisticians | s-tier |
| Your team name | Team to review 1 |
|---|---|
| data-devils | git-kat |
| git-kat | team-purple-f1 |
| team-purple-f1 | jacz |
| jacz | 404-found |
| 404-found | three-musketeers |
| three-musketeers | data-devils |
| Your team name | Team to review 1 |
|---|---|
| plz-give-an-a | we-r-4-real |
| we-r-4-real | git-hubbards |
| git-hubbards | geom-jitters |
| geom-jitters | r-u-serious |
| r-u-serious | r-chitects |
| r-chitects | plz-give-an-a |
| Your team name | Team to review 1 |
|---|---|
| alexa | jjc-studio |
| jjc-studio | charisma |
| charisma | map-b |
| map-b | mean-machine |
| mean-machine | watermelon |
| watermelon | render-commit-push |
| render-commit-push | beegees |
| beegees | alexa |
| Your team name | Team to review 1 |
|---|---|
| the-pipe-operators | visionaries |
| visionaries | dataframe |
| dataframe | the-dolphins |
| the-dolphins | dwl |
| dwl | the-a-team |
| the-a-team | 11f |
| 11f | the-pipe-operators |
Grading
Peer reviews will be graded on the extent to which it comprehensively and constructively addresses the components of the reviewee’s team’s report.
Only the team members participating in the review during the lab session are eligible for points for the peer review. If you’re unable to make it to lab in person, you should arrange to virtually connect with your team during your lab session.
0 points: No peer review
1 point: Feedback provided is not constructive or actionable
2-4 points: Feedback provided is not sufficiently thorough
5 points: Peer review is constructive, actionable, and sufficiently thorough
Note
The feedback issue will come from one team member on GitHub since you can’t collectively edit an issue. However it must represent the opinions of the entire team. It is not a single team member’s responsibility to provide feedback, they’re just the record keeper for the team.