hackathons/vienna: Add links to the tasks spreadsheet

Replace TODOs with links to the spreadsheet containing the tasks.

Signed-off-by: Stefan Jumarea <[email protected]>

content/hackathons/2024-12-vienna/index.mdx

@@ -77,7 +77,7 @@ If you did not create an account already, signup [here](https://console.unikraft
 You will be using that in the following sessions.
 
 Once you have a token, follow the steps [here](https://unikraft.cloud/docs/quickstart/) to deploy your first unikernel.
-If everything went well, deploy more applications following the tasks [here](TODO).
+If everything went well, deploy more applications following the tasks [here](https://docs.google.com/spreadsheets/d/1nrIG9j0ea5YMBCzMvjA1K9EiQWWq-2zO05jOgO9xqMY/edit?usp=sharing).
 
 ### Behind the Scenes: Using KraftKit to Operate Unikraft Applications
 
@@ -86,7 +86,7 @@ Now you will build and run Unikraft-based application locally.
 With this, you will get a better look at what `kraft cloud` does behind the scenes.
 
 Follow the steps [here](https://unikraft.org/guides/using-the-app-catalog) and bring the cloud to your machine.
-After you are done with all of them, take a look to some more applications, following the tasks [here](TODO).
+After you are done with all of them, take a look to some more applications, following the tasks [here](https://docs.google.com/spreadsheets/d/1nrIG9j0ea5YMBCzMvjA1K9EiQWWq-2zO05jOgO9xqMY/edit?usp=sharing).
 Go through them orderly and aim to complete all items until the `Extra` section.
 If you have extra time on your hands, go through the `Extra` section as well.
 
@@ -97,16 +97,16 @@ We do that using `docker`.
 This is useful both to understand what is happening behind the scenes and to have a test environment for your application.
 In case there are issues with Unikraft Cloud / KraftKit, you can use Docker to see if everything is in the right place and to assist in debugging.
 
-Follow the steps [here](TODO) (only the ones under `Redis`) to see how you can port a new application on top of Unikraft.
-Mark the items as completed [here](TODO).
+Follow the steps [here](https://unikraft.org/docs/contributing/adding-to-the-app-catalog) (only the ones under `Redis`) to see how you can port a new application on top of Unikraft.
+Mark the items as completed [here](https://docs.google.com/spreadsheets/d/1nrIG9j0ea5YMBCzMvjA1K9EiQWWq-2zO05jOgO9xqMY/edit?usp=sharing).
 Go through them orderly and aim to complete all items until the `Extra` section.
 If you have extra time on your hands, go through the `Extra` section as well.
 
 ### Debugging Unikraft / Unikraft Cloud Applications
 
 When porting new applications, you can run into issues both on the Docker build and on the Unikraft runtime.
 To debug the issues, you can follow the instructions [here](https://unikraft.cloud/docs/guides/features/debugging/).
-Get a hands-on experience with debugging by following the items [here](TODO).
+Get a hands-on experience with debugging by following the items [here](https://docs.google.com/spreadsheets/d/1nrIG9j0ea5YMBCzMvjA1K9EiQWWq-2zO05jOgO9xqMY/edit?usp=sharing).
 
 ### First Principles Approach: Using Make and VMMs Directly
 
@@ -135,7 +135,7 @@ For every step, there is a section in the `README` file that goes into detail ab
 For the hackathon, please create teams of 2-3 people, and create your very own cloud-native application to run on Unikraft Cloud.
 Think of a cool application you've been waiting for a while to implement.
 Use your preferred programming language (supported by Unikraft Cloud), employ any frameworks or existing software components as required, and then deploy it on Unikraft Cloud.
-After you create a team and decide on a project, fill [this spreadsheet](TODO) with the team name, members and project idea.
+After you create a team and decide on a project, fill [this spreadsheet](https://docs.google.com/spreadsheets/d/1nrIG9j0ea5YMBCzMvjA1K9EiQWWq-2zO05jOgO9xqMY/edit?usp=sharing) with the team name, members and project idea.
 
 At the and of the hackathon, you should make a PR in the [Unikraft Cloud `examples` repository](https://github.com/unikraft-cloud/examples) with your work.
 We will be evaluating the project, focusing on functionality, originality, robustness, complexity, code quality and team work.