Find a solution to students ghosting the hackathons #377
Description
Context:
Hey all,
this year we had a recurrent problem with students that were silently not participating in hackathons - they were present, but not contributing to the group effort, or they even disappeared from the group call during hours. I would like to start the brainstorming about how to prevent these situations and how to deal with such unresponsive/ghost students. We came up with a few ideas during a recent sync, see below. I would love to hear your opinion on this and also if you have further suggestions for a solution. Thank you!
Possible solutions:
- talk to all students during the check ins, ask them what they are doing, ask to see their code.
- use a common team repo where we can see the contributions of each student. If they want to work in such a way that only one person writes the code and others make suggestions, that's fine, but they have to agree on it and tell us (and be aware of the risks).
- if a student is reported to be unresponsive, they will have to work alone in the next hackathon (or could even be excluded from the team and have to finish the hackathon alone).
Goal(s):
Find a solution to solve this problem.
Acceptance criteria:
Find a solution that is not too complicated and fair.