Skip to content

Commit 4e4780b

Browse files
MLH League Teamgitbook-bot
authored andcommitted
GitBook: [#67] Alba Updates!
1 parent 87dbfb1 commit 4e4780b

File tree

11 files changed

+27
-28
lines changed

11 files changed

+27
-28
lines changed

general-information/build-your-leadership-team.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,11 @@ It’s vital to get your team onto the same page for your hackathon so you’re
1717
* Assign each team to lead different tasks on your **project management tool** (Trello, Notion, Asana etc.) with deadlines. 
1818
* Follow up with each of the individual heads to **get status updates** on their tasks to keep them accountable.  
1919
* **Team management**: As you all integrate new team members, there’s a bunch for them to learn about from team dynamics to how to do their role. To start off, continue doing [team building activities](../organizer-resources/host-exciting-mini-events/) while relaying the importance of them to your team. In addition, reach out to everyone individually to join the team building activities to create a sense of accountability as well. 
20-
* **Staying Organized:** Working towards organizing any event becomes difficult if there's any communication gap in your team. There are tons of ways to keep your team hackathon planning team organized and on track. If your team is working remotely, it's even more important to have a system in place. The actual tools you use don't matter as much as picking them and sticking to it. As hackathon organizers, it can be easy to over-engineer your planning process. Keep in mind that sometimes the simplest solutions are the easiest for the whole team to adopt and use.
20+
* **Staying Organized:** Working towards organizing any event becomes difficult if there's any communication gap in your team. There are tons of ways to keep your hackathon planning team organized and on track. If your team is working remotely, it's even more important to have a system in place. The actual tools you use don't matter as much as picking them and sticking to it. As hackathon organizers, it can be easy to over-engineer your planning process. Keep in mind that sometimes the simplest solutions are the easiest for the whole team to adopt and use.
2121

2222
Some tools we've seen work well for organizing teams are:
2323

2424
* **Chat:** Slack, Discord
2525
* **Documents:** Google Drive (G-Suite, if possible), Notion, Airtable 
2626
* **Task Management:** Asana, Notion, Trello
27+

general-information/creating-your-hackathon-schedule/README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,31 +10,31 @@ Make your volunteers responsible for specific tasks. They should be working on s
1010

1111
## Event Start:
1212

13-
* \[Physical]Serve breakfast
13+
* \[Physical] Serve breakfast
1414
* Welcome and brief sponsors
1515
* Welcome and check-in attendees
16-
* \[Physical]Check ID, collect liability waivers and minor forms
16+
* \[Physical] Check ID, collect liability waivers and minor forms
1717
* Give out promotional materials (swag or credits)
18-
* \[Physical]Give attendees wrist bands or name tags
18+
* \[Physical] Give attendees wrist bands or name tags
1919

2020
## **Opening ceremony**
2121

2222
> Note about speakers: Your attendee’s time is valuable. Many sponsors are going to ask for speaking spots… optimize for interesting speakers rather than lucrative speakers.\
2323
> \
2424
> Invite-only API demos (developer evangelists) are another good option.
2525
26-
* \[Physical]Round up people to attend presentation
26+
* \[Physical] Round up people to attend presentation
2727
* Welcome address
2828
* Announcements
2929
* Keynote speaker
3030
* MLH talks
3131

3232
## During Hacking
3333

34-
* \[Physical]Collect garbage
34+
* \[Physical] Collect garbage
3535
* Tech talk facilitator: rounding people up to listen and handling speakers (tech talks usually sponsors). 
36-
* \[Physical]One volunteer should be in charge of each special area or activity at the hackathon: for example, the hardware room, photo booth, etc.
37-
* \[Physical]Checking in on hackers: feeding them snacks, making sure their power and WIFI are working, etc.
36+
* \[Physical] One volunteer should be in charge of each special area or activity at the hackathon: for example, the hardware room, photo booth, etc.
37+
* \[Physical] Checking in on hackers: feeding them snacks, making sure their power and WIFI are working, etc.
3838

3939
## Hacking Deadline
4040

general-information/draft-up-your-mentorship-plan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Managing mentors during the day-of means can be enhanced by taking advantage of
2323
* Create an @mentor role and add all mentors to there so hackers can easily differentiate mentors
2424
* Have a set of guidelines for mentors on what to do during mentorship, giving them a process
2525
* Encourage volunteers to stay alert on Discord to look for hackers who need help and push them to the above-mentioned mentorship channel.
26-
* \[Physical]Have a dedicated mentor area that hackers can walk up to with questions
26+
* \[Physical] Have a dedicated mentor area that hackers can walk up to with questions
2727

2828
## Connecting Mentors to Hackers
2929

general-information/event-logistics/softwares-for-digital-hackathons.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ Before joining and once on the platform, make hackers know that their behavior a
2020
* **Mentors-Internal:** Channel for mentors to talk with each other and with organizers. 
2121
* **Admin:** Channel for your organizing team. We recommend creating an admin voice channel as well! 
2222

23-
## Streaming/Video Conferencing Platform\[Digital Events]
23+
## Streaming/Video Conferencing Platform \[Digital Events]
2424

25-
Digital hackathons depend entirely on the different you wish to choose to host them over. Making or breaking your hackathon will highly depend on the flexibility and the experience of using the platforms and how well your team is able to manage it. We highly recommend organizers to be aware of the different platforms they might be using so as to avoid any difficulties or edge cases on the day of.
25+
Digital hackathons depend entirely on the different platform you wish to choose to host them over. Making or breaking your hackathon will highly depend on the flexibility and the experience of using the platforms and how well your team is able to manage it. We highly recommend organizers to be aware of the different platforms they might be using so as to avoid any difficulties or edge cases on the day of.
2626

2727
Your team may choose to stream different aspects of the event including the opening ceremony, workshops, mini-events, and closing ceremony.
2828

general-information/event-logistics/working-with-food-vendors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,13 @@ Delivery If your vendor is delivering the food to your venue, make sure you are
1414

1515
When you put in your food order, you should be specific about where the food should be delivered and who they should contact upon arrival. Give them a backup phone number in case the first organizer doesn’t pick up.
1616

17-
If your food vendor is providing a family-style meal (on large platters meant for sharing, rather than as individual plates) they will need more time to set up. We recommend scheduling the drop-off for 60-90 minutes prior to the meal start time. In this case, we don’t have to worry about food getting cold because it’s likely they will be using chaffing dishes to warm up the food.
17+
If your food vendor is providing a family-style meal (on large platters meant for sharing, rather than as individual plates) they will need more time to set up. We recommend scheduling the drop-off for 60-90 minutes prior to the meal start time. In this case, we don’t have to worry about food getting cold because it’s likely they will be using chafing dishes to warm up the food. However, some venues have restrictions on the use of chafing dishes due to them involving flammable material, so check the rules before you plan on using them. 
1818

1919
### Distributing Meals
2020

2121
If your food vendor is providing a family-style meal make sure you coordinate with them on who will be serving the food. Some vendors like university catering services have special requirements that require you to utilize their staff for food distribution and preparation.
2222

23-
When putting in the initial order, make sure to ask how the food vendor how they would like you to return the chaffing dishes, table cloths, and other reusable goods. If they plan on picking up the goods after the meal and helping you clean up, make sure you coordinate a time in advance. You don’t want to be left with tables full of leftover food, and dishes after a meal with no plan.
23+
When putting in the initial order, make sure to ask how the food vendor how they would like you to return the chafing dishes, table cloths, and other reusable goods. If they plan on picking up the goods after the meal and helping you clean up, make sure you coordinate a time in advance. You don’t want to be left with tables full of leftover food, and dishes after a meal with no plan.
2424

2525
### Negotiating 
2626

general-information/getting-sponsorship/budgeting-your-hackathon.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,17 +12,17 @@ _Digital events have significantly lower costs compared to in-person events. Thi
1212

1313
## Major Costs to Consider
1414

15-
* **Food\[In-Person Only]:** Providing hackers with food is one of the major costs associated with any hackathon. Everyone expects their dietary restrictions to be fulfilled alongside having high quality good at the hackathon. This comes in as one of the major aspects of hacker experience at almost any hackathon we have seen. 
15+
* **Food \[In-Person Only]:** Providing hackers with food is one of the major costs associated with any hackathon. Everyone expects their dietary restrictions to be fulfilled alongside having high quality good at the hackathon. This comes in as one of the major aspects of hacker experience at almost any hackathon we have seen. 
1616
* **Tooling:** The platforms you'll be using during the course of your hackathon. This include the event platforms like the 
1717
* **Communication Platform** for building up conversations within the hackathon. It can also be used for announcements or updates and to share resources with hackers. _Recommended Platform: Discord_
18-
* **Streaming Platform\[Digital Only]** for Opening & Closing Ceremonies. _Recommended Platform:_ [_Streamyard_](../../organizer-resources/logistics-resources/streamyard.md)
19-
* **Video Calling Platform\[Digital Only]** for hosting your workshops, mini-events, live demo judging, webinars etc. _Recommended Platform: Zoom_
20-
* **Virtual Conference Platform\[Digital Only]** can be used for running the whole event in a consolidated space. These platforms are a bit costly but the hacker experience they provide is much better than using different streaming and calling platforms. _Recommended Platforms: Hopin, Gather.Town_
18+
* **Streaming Platform \[Digital Only]** for Opening & Closing Ceremonies. _Recommended Platform:_ [_Streamyard_](../../organizer-resources/logistics-resources/streamyard.md)
19+
* **Video Calling Platform \[Digital Only]** for hosting your workshops, mini-events, live demo judging, webinars etc. _Recommended Platform: Zoom_
20+
* **Virtual Conference Platform \[Digital Only]** can be used for running the whole event in a consolidated space. These platforms are a bit costly but the hacker experience they provide is much better than using different streaming and calling platforms. _Recommended Platforms: Hopin, Gather.Town_
2121
* **Swag (Schwag):** "Stuff We All Get" T-shirts, stickers, water bottles, lanyards, etc.  
2222
* _Distributing swag is a digital world might look a bit difficult as the costs of shipping are associated with them. We would recommend you to look at the different options available which can be easily fulfilled from your side within a budget._ 
2323
* **Prizes:** Prizes are the driving factor in most of the hackathons these days. Though giving out prize money might seem like an easier option, we recommend giving out something that can help hackers learn, grow and utilize for their personal development. 
2424
* _For Digital Events we recommend checking for prizes that can be easily fulfilled with free delivery through Amazon or any other online service._ 
25-
* **Shipping Prizes and Swag\[Digital Only]:** This is an added cost in digital events. We recommend getting quotes from different shipping services based on your estimate of swag and prizes. We recommend using the local postal services (like USPS or Indian Post) as they often are the most reliable & economical shipping providers. We recommend to check out [MLH Organizer Event Fulfillment](broken-reference) to see how MLH can help you curb these costs!
25+
* **Shipping Prizes and Swag \[Digital Only]:** This is an added cost in digital events. We recommend getting quotes from different shipping services based on your estimate of swag and prizes. We recommend using the local postal services (like USPS or Indian Post) as they often are the most reliable & economical shipping providers. We recommend to check out [MLH Organizer Event Fulfillment](broken-reference) to see how MLH can help you curb these costs!
2626
* **Web Hosting/ Internal Toolings:** One of the starting costs for any hackathon. Though these are one of the most important costs which might get overlooked we recommend checking out the [GitHub Education Student Developer Pack](https://hackp.ac/github) and different open source alternatives for the tools you might be paying for unnecessarily.
2727

2828
Before you can begin asking for money, get a sense of how much cash you need to pull off your hackathon. Create a [budget template based on estimated costs and your expected number of attendees](https://docs.google.com/spreadsheets/d/1ADKWatCbC3AhBKlyWOtVSqMcD6O6Y3FcwMTZwynPwDA/edit).
@@ -33,7 +33,7 @@ Note: We recommend you build in a buffer of $1,000 to $3,000, depending on the s
3333

3434
Over the years we've found the averages costs for major budget items are as follows (US Hackathons):
3535

36-
* **Food:** $7 per person per meal
36+
* **Food:** $8-10 per person per meal
3737
* **Snacks & Drinks:** $10 per person
3838
* **T-Shirts:** $5-8 per person (dependent on volume)
3939
* **Buses:** $3,500 per bus

general-information/getting-sponsorship/introduction-to-fundraising.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ With the **right communication and target**, you can expect a lot of positive re
1919

2020
* As we have noticed with time, **sponsors can get much of the same value** from a Digital Event as they can an In Person one. 
2121
* **Prize categories** and **Workshops** can both be run much the same, though sponsors should practice running their workshop through streaming or pre-recorded video. 
22-
* Give sponsors them their **own channel on the chat platform (Slack/Discord)** to talk to hackers, and have them introduce themselves so everyone knows who they are how they can be helpful for them. As long as they’re online answering questions from hackers about their company/prize category/workshop/anything else they’re doing that weekend, they’ll have a lot of great interactions with hackers. 
22+
* Give sponsors their **own channel on the chat platform (Slack/Discord)** to talk to hackers, and have them introduce themselves so everyone knows who they are how they can be a resource for them. As long as they’re online answering questions from hackers about their company/prize category/workshop/anything else they’re doing that weekend, they’ll have a lot of great interactions with hackers. 
2323
* We also strongly recommend doing **Office Hours** with sponsors.
2424

2525
### When you’re finished reading this section of the guide, we strongly recommend watching our fundraising webinar: [Raising Sponsorship - A Workshop by MLH](https://www.youtube.com/watch?v=QI9NVe2wA5w) and [Creating Compelling Sponsorships. ](https://www.youtube.com/watch?v=W9miqQzxT-0)

general-information/getting-sponsorship/setting-goals/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: >-
77

88
# Understanding your Sponsors
99

10-
Sponsorship is one of the most crucial parts of every hackathon. When you're reaching out to sponsors, it's necessary to understand their perspective of supporting your hackathon and the outcome they're expecting out of it. You should consider this as a sales pitch for your hackathon. To understand it further, let's first understand the different types of sponsor hackathons generally target to.
10+
Sponsorship is one of the most crucial parts of every hackathon. When you're reaching out to sponsors, it's necessary to understand their perspective of supporting your hackathon and the outcome they're expecting out of it. You should consider this as a sales pitch for your hackathon. To understand it further, let's first understand the different types of sponsors hackathons generally target to.
1111

1212
## Hackathons target five categories of sponsors:
1313

general-information/judging-and-submissions/draft-up-a-judging-plan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ $$J =$$ Number of Judges\
3131
$$P =$$ Number of Submitted Projects\
3232
$$n =$$ Number of Judges for each project (or number of rounds of judging per project)\
3333
(MLH recommendation: 3 rounds per project)\
34-
$$t =$$ Time taken by a Judge per project (MLH recommendation: 5 mins per project)\
34+
$$t =$$ Time taken by a Judge per project (MLH recommendation: 3 mins per project)\
3535
$$T =$$ Total time allocated for Judging (in minutes)
3636

3737
For eg.: Consider you have **150 projects submitted** at your hackathon and you have **allocated 2 hours for judging**. As per our recommendation, we are having **3 rounds of judging** per project and **3 minutes are allocated per project** for a judge to take their decision.

overview/mlh-community-values.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,15 @@ MLH Member Events serve as examples of excellence to other hackathons and commun
1818
* Have **enough food on-site** to reasonably feed attendees during the event.
1919
* Events should **provide healthy food options** and have options available for hackers with dietary restrictions.
2020
* Ensure that **participants own any intellectual property** they produce at the event.
21-
* Clearly **communicate** any major changes to the event \(Ex. venue, location, schedule, theme, etc.\) as soon as they occur.
21+
* Clearly **communicate** any major changes to the event (Ex. venue, location, schedule, theme, etc.) as soon as they occur.
2222
* **Check in all attendees** as they arrive at the event and make sure they have an up-to-date name, email, mobile phone number, and school for each of them.
2323
* Have **at least one lead organizer** who has full ability to make decisions on-site at any time during the event.
2424

2525
## MLH Member Events are open and accessible to all students.
2626

2727
* **Do not have entry fees**.
2828
* **Advertise well** enough in advance for hackers in the area to learn about the event.
29-
* **Do not discriminate** on the basis of race, religion, national origin, color, sex, gender identity, sexual orientation, social class, economic status, veteran status, disability, or age.
30-
* Make a good-will effort to advertise and make the **application for admission publicly available**.
29+
* **Do not discriminate** on the basis of race, religion, national origin, sex, gender identity, sexual orientation, social class, economic status, veteran status, disability, or age.
3130
* **Aren’t secret** or invite-only events**.**
3231
* Have a straightforward and publicly known **general application process**.
3332
* Publish the **criteria for admission** to their event.
@@ -43,7 +42,7 @@ MLH Member Events serve as examples of excellence to other hackathons and commun
4342
* Adopt, make available, and enforce the **MLH Code of Conduct**.
4443
* All **organizers sign and agree** to the MLH Code of Conduct.
4544
* Have a clear and widely known **reporting system for incidents**.
46-
* Have a link to the Code of Conduct on their website and ask **all registrant to agree** to the Code of Conduct during registration \(e.g. a compulsory checkbox\).
45+
* Have a link to the Code of Conduct on their website and ask **all registrant to agree** to the Code of Conduct during registration (e.g. a compulsory checkbox).
4746
* Make it clear that the **Code of Conduct extends to all attendees**, including hackers, volunteers, organizers, sponsors, judges, mentors, and MLH staff.
4847
* Make sure that bad actors and attendees who violate the Code of Conduct or rules will not attend the event.
4948
* **Respect and enforce the drug and alcohol laws** and customs of the local country _\*\*_and only allow moderate alcohol consumption in locales where drinking is allowed.
@@ -52,4 +51,3 @@ MLH Member Events serve as examples of excellence to other hackathons and commun
5251
* Whenever possible, events **provide sleeping spaces for attendees** and encourage attendees to take advantage of them.
5352

5453
Creating an empowering environment where hackers of all skill levels can create amazing things is MLH’s main priority. The MLH Community Values codify this belief in a way that describes not only the MLH Member Events but also the types of events that MLH wants to work with because of their positive contributions to the student hacker movement.
55-

0 commit comments

Comments
 (0)