Differences

This shows you the differences between two versions of the page.

--- events:birminghack [2026/05/28 15:09] – Add up to Tracks + Prizes root
+++ events:birminghack [2026/05/28 16:01] (current) – root
@@ Line 15: / Line 15: @@
   * Who on committee is going to be there
   * Security
-  * Room Bookings (Talk to Mo)
+  * Room Bookings
   * Tickets
   * Website
@@ Line 39: / Line 39: @@
 We have personally done 3 tracks in the past: Best Hack, Most Fun Hack and Best Newcomer. You will need to provide prizes for these, with Best Hack having the most expensive prize, and the other tracks the prize will depend on how much money you have from sponsors.
+==== Mini-events ====
+Mini-events are always fun little things that happen throughout the hackathon. Previously we have done: Chess Tournament, Paper Airplane contest, Midnight movie screening and a git workshop. Decide on a couple to run throughout but make sure you don't do too many. I would highly recommend a git workshop though. You can also have some small prizes for these, even if its something random from the cupboard
+Hackathons UK also runs a cup stacking competition and they will provide a prize for this. We have red cups in the cupboard somewhere for this but they may also supply their own cups, ask them how they are running it.
 === Collabs ===
@@ Line 49: / Line 55: @@
 ==== Sponsors ====
+If you are going to do anything early for this event, getting sponsors is the main thing you should be doing. You need to ensure that contracts are signed at least 3 weeks before the event at the absolute latest (especially if they want to have someone at the event), but the earlier the better.
+Talk to your current sponsors and look at companies that have sponsored other hackathons around the country at first as they are most likely to be looking at sponsoring a hackathon. Please don't go asking random American companies as they aren't gonna do it and they will think you are in Alabama.
 ==== Theme ====
+You can be creative with this, but it needs to be decided before the event. You can announce the theme beforehand, or you can announce it at the opening ceremony. Completely up to you what you decide to do. Previously we have done 'Building Foundations' and 'Project Lazarus'. I'd recommend having something broad to let people use their imaginations but completely up to you with that.
 ==== Hackathons UK ====
-==== Who on committee is going to be there ====
+Hackathons UK is one of the most useful companies we have worked with. They are a non-profit who work with university societies to run Hackathons and have been so helpful for us in the past. Apart from general advice they have a spreadsheet for grading hacks and choosing prizes which turns a 3 hours job into an hour and a half one.
 ==== Security ====
-==== Room Bookings (Talk to Mo) ====
+The only reason we have had security is because Mo has required us to have some when the building is not op[en on the weekend (5pm-9am). In past we have got security from the guild + Matty. Ask Matty about this if Mo requires you to have security.
+==== Room Bookings ====
+While talking to Mo about booking the building you also need to ask about having areas for hacking (the labs), a quiet area (either a room in the building or sloman), potentially a prayer room depending on when you are running it and you also need a Ceremony room for the opening and closing ceremony. The lab will not be big enough. Aston Webb is a possibility but is a pain since it isn't meant to be open on the weekend, I would recommend trying to find somewhere else. Good luck with that.
 ==== Tickets ====
+For tickets, we have used ti.to to organise it and hold all the data, especially for registration and tracking people entering/leaving the building. Look at previous years tickets on their website in order to see how to organise the tickets. The login is on the vaultwarden.
 ==== Website ====
+The most important things on the website is to update the main page with the date, tickets link and schedule. Most of it is automated if you just add the data into a file called `/_date/<year>.yaml`. Check previous years yamls for how this is laid out. There might be some documentation on the github for how to do this properly but I wouldn't count on it. If you need any help ask in #handover on discord.
+==== Discord ====
+Every year we make a new discord server for each iteration of birmingHack. You can basically just copy the template from each previous year and modify it accordingly. There is a bot that automatically grants people access based on the discord name they put on their ti.to ticket so you don't need to manually grant access. People will moan that it isn't working, they have just spelt their name wrong on the ticket.
+This server is also used for all the announcements before and during birmingHack to let people know when things are happening, especially food and mini-events.
 ==== Standby Queue ====
+We haven't done this in the past but it's a great idea. Just make sure you publicise it if you do manage to get the school to approve it since there will be a lot of people that don't end up attending.