Your team name | To review 1 | To review 2 |
---|---|---|
001 | ||
Elegant Cassowary | Elegant Wombat (repo) | Elegant Wallaby (repo) |
Elegant Dingo | Elegant Cassowary (repo) | Elegant Wombat (repo) |
Elegant Echidna | Elegant Dingo (repo) | Elegant Cassowary (repo) |
Elegant Koala | Elegant Echidna (repo) | Elegant Dingo (repo) |
Elegant Wallaby | Elegant Koala (repo) | Elegant Echidna (repo) |
Elegant Wombat | Elegant Wallaby (repo) | Elegant Koala (repo) |
Lab - Project draft peer review
The project peer review is due Friday, November 22 at 11:59pm.
No submission on Gradescope needed, just post issues on GitHub by this time.
In this lab, you will…
- 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
Project peer review
Each team will review two other teams’ project. As a team you should spend ~25 minutes on each team’s project.
Find the names of the teams whose projects 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. This includes both the Quarto documents (use the “Build” tab and “Render project” to render all of them simultaneously) as well as any additional materials (e.g. R scripts). Hopefully the team provides documentation so you know what to look for.
1-2 team members open the team’s draft report (
docs/report.pdf
).1 team member opens an issue on the team’s repo using the appropriate issue 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 “Peer review (students)”. Fill out this issue, answering all the prompts in the form.
Review pairings
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.
0 points: No peer review
1 point: Only one peer review issue open, feedback provided is not constructive or actionable
2 points: Both peer review issues open, feedback provided is not constructive or actionable
3 points: Both peer review issues open, feedback provided is not sufficiently thorough
4 points: Both peer review issues open, one of the reviews is not sufficiently thorough
5 points: Both peer review issues open, both reviews are constructive, actionable, and sufficiently thorough
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.
Acknowledgments
- This assignment is derived from STA 199: Introduction to Data Science