Late deliveries definition

[CatarinaSilva]

Context: In the summit we discussed that we should be more strict with late deliveries. Right now we spend too much time planning them and aligning with students. We also block students from having access to the solutions untill all late deliveries are completed.

Goal(s):

Close and document decisions on late deliveries of hackathons for batch6

Starting point (from summit)

1. Set one single strict late delivery date per hackathon on calendar, so that students know all dates beforehand. A student will only be considered to have delivered if he satisfies this deadline and shows up (online) to present on the day.
2. Shorten the delivery dates - last year it was the end of the month after the hackathon, however this creates discrepancies between hackathons and may lead to students only seeing solutions 2 months later. Suggestion: 2 weeks for each late delivery
3. Finally, share the solutions even if there are late deliveries: we have a code of conduct and we should see in the presentation if the student just followed the baseline (we could reinforce this message to students throughout the academy)

Acceptance criteria:

• [x] Define deadlines for late deliveries
• [x] Document in wiki late delivery process and rules
• [ ] Book late delivery dates on calendar

Deadline 24th June

[cimendes]

I'm in favour of having late deliveries pre-booked in the batch student calendar, exactly one month after the deadline.

[minhhoang1023]

2 weeks seems reasonable in my opinion. The sooner we close the final status, the better - both for students and instructors.

[SaraOGomes]

2 weeks is OK. If you postpone the deadline students may tend postpone the delivery too.

[CatarinaSilva]

As everyone that spoke out agreed and this was shared multiple times, will move forward with 2 weeks and document it

[CatarinaSilva]

Opened https://github.com/LDSSA/wiki/pull/371