Hackathon Lifecycle

Hackathon Lifecycle (temp)

For the moment a simple change of status will be used to decide the stage in the hackathon lifecycle.
This can be changed at a later stage and combined with dates (e.g. registration_open_date, registration_closed_date, etc.)

Status <> Meaning:

1. draft - Hackathon is still being worked on, only admin who created the hackathon can see it
2. published - All users can see the hackathon (if the organisation is Code Instatitute or they belong to the selected organisation)
3. registration_open - Users can sign up to the hackathon
4. hack_in_progress - Users can no longer sign up to the hackathon; hackathon is in progress
   • This can also be used to trigger special events such as specific content being viewable, etc.
5. judging - The judges are scoring the teams' projects and deliberating over the final outcomes. This also includes team demonstrations and any other "clean up" activities such as feedback sessions, etc.
6. finished - The hackathon is over, all activities have concluded. This (or the previous status) can be used to trigger special events such as the projects being visible publicly, prizes being released to participants, etc.