For this format, we need to collect all potential hacking tasks and will need to be released along with the scholarship application.

Based on our experience and learnings from organizing several hackathons in the past, we’d like to try a slightly different format of program and participation. Usually, the tasks are populated a few days before the event, and selected participants sign up for specific tasks on the first day of the event. While this works well, it creates a challenge where we might not have tasks relevant to the skillset or interest of the participants. Also, during the hackathon, while we are able to solve bugs, it is hard to track the impact collectively.

For this hackathon, the tasks have been curated in a way that a set of tasks collectively complete the substantial development of a tool or workflow, so that it can be said to reach a stable version. This can also be useful to drive engagement post-event where developers can continue to work on the task to reach completion.