Skip to content

Commit db5b025

Browse files
committed
Update hand-in-homework-guide.md
1 parent 16395b0 commit db5b025

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

hand-in-homework-guide.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,47 @@ Notes:
4242

4343
1. If you are in an AZC you may need to use HTTPS instead as the AZC may have blocked the network protocol used by SSH.
4444
2. This first week for which you need to submit homework is week 3 of the JavaScript module.
45+
46+
# Homework Review Process
47+
48+
## Before you start
49+
1. You get assigned a mentor at the start of the module in the slack group chat. (S)He is responsible for reviewing your work for the duration of the module.
50+
3. Please don't hesitate to contact Tjebbe or the class mentor if you are facing any issues. We are here to help you out!
51+
52+
## Review process
53+
Together with the mentor and other students in your group you have the freedom to decide on the way of communication. You can do video calls or get feedback via comments to the PR.
54+
55+
The mentor will start a group message on Slack and agree together on the way of communication. There, the mentor can keep the whole group informed of his/her availability and updates.
56+
57+
58+
### Video calls
59+
If your group chooses to do video calls, there're 2 options. Individual calls or a group call.
60+
61+
Please write down some questions before te start of the call. During the call it is important to make notes of the feedback from the mentor, so you know what has to be adjusted afterwards.
62+
63+
### Comments to the PR
64+
The mentor will place comments on your pull request. You have to adjust your work accordingly and reply on the feedback.
65+
66+
### Timeline feedback
67+
| Days | Activities |
68+
| --- | --- |
69+
|Tuesday (week 1) | Deadline for you to hand in your first version |
70+
|Wednesday (week 1) - Tuesday (week 2) | Mentor provides feedback |
71+
| Wednesday (week 2) - Tuesday (week 3) | you improve homework based on the feedback and mentor evaluates improvements |
72+
| Wednesday (week 3) | Core-team member Homework Approval Check. At this point every PR needs to be approved. |
73+
74+
It can happen that your mentor doesn't reply on your questions or your updated homework. Please send a reminder via slack. If that doesn't work and you're afraid you can't make the deadline, contact your class-mentor.
75+
76+
### Labels
77+
It is important for the you and the core-team to have up to date info about the status of the homework. This is why the mentors use two labels on your PR.
78+
79+
| Label | Description |
80+
| --- | --- |
81+
|no label |not reviewed yet |
82+
|Needs work |reviewed, but you need to implement feedback |
83+
|Approved |reviewed, and your homework has been approved |
84+
85+
Here is an example of this in action.
86+
87+
![labels](https://github.com/HackYourFuture/mentors/blob/main/assets/labels.png)
88+

0 commit comments

Comments
 (0)