Join us on December 1st, 2018 for MLH's Local Hack Day, a global hackathon and celebration of learning, building, and sharing!
12 Hours of Hacking at the University of Toronto - Scarborough Hosted by the University of Toronto Scarborough and Victoria Park Collegiate Institute Students
WHAT IS LOCAL HACK DAY?
Join us on December 1st, 2018 for MLH's Local Hack Day, a global hackathon and celebration of learning, building, and sharing! Whether you're a first timer who is learning to program or you go to hackathons every weekend, everyone is welcome to participate!
This is MLH's 5th year organizing Local Hack Day. In 2017, the event brought out more than 6,000 participants across 34 countries and 236 cities around the world. This year's event is shaping up to be the biggest one yet!
WHAT IS A HACKATHON?
Hackathons are learning focused invention marathons where participants dream up fun, interesting projects and work in small teams to bring them to life over the course of the event.
When you're not working on your project, there are plenty of other things to do like attending educational workshops, making friends, or showing off what you're learning or building. At Local Hack Day you can do these with other participants at your location or participants around the world at other locations!
Whether you're a seasoned hackathon veteran or have never been to a hackathon before, MLH Local Hack Day is the best way to kick off the 2019 MLH Hackathon Season.
Any student who has been ACCEPTED to participate and hacked at UTSC LHD is eligible to submit a project.
Teams up to a maximum of four (4) people.
All hacks must be built onsite at "UTSC Local Hack Day" by registered participants, from start to finish. Unregistered hackers will not be allowed to participate.
Remote participation is not allowed.
Please see Rules and Submission Requirements for further guidelines.
The UTSC Local Hack Day organizing team reserves the right to disqualify project submissions that do not adhere to the following guidelines. Please contact a UTSC LHD Organizer if you have any questions regarding these guidelines.
Projects can be completed individually or in a group with a maximum size of 4 students. All team members must be approved, registered UTSC LHD attendees present at the event.
All code written for UTSC LHD must be written between 9:30AM on Saturday, December 1st and 7:30PM on Saturday, December 1st, 2018 with the exception of code taken from public and open source libraries, APIs, or tutorials.
All hardware assembled for UTSC LHD must be assembled between 9:30AM on Saturday, December 1st and 7:30PM on Saturday, December 1st, 2018, with the exception of manufactured parts that do not require soldering or assembly with a breadboard outside of the factory (such as robotic arms, Myos, or 3D printed parts).
All art assets brought into UTSC LHD for your project must be free and publicly available.
Students are free to bring codeless wireframes for the layout of their projects. Hardware may be prototyped in advance to optimize the shape and size of parts, but the actual project presented for submission must be assembled at UTSC LHD.
The final product must be original: it must not be the same as the product of a tutorial, a submission to a previous hackathon, or a personal project completed before UTSC LHD. Attendees are trusted to ensure the originality of their projects in good faith. UTSC LHD retains the right to inspect the source code of projects in case of dispute. All projects and intellectual property produced at UTSC LHD belong to the attendees who produced it.
All participants must abide by the MLH Code of Conduct: https://static.mlh.io/docs/mlh-code-of-conduct.pdf
Adapted from https://hackwestern5.devpost.com/rules
How to enter
Space is limited - sign up at localhackday.mlh.io. Search for the "University of Toronto Scarborough" event and sign up there!
Computer Science Teacher @ Victoria Park Collegiate Institute
Full Stack Developer @ RBC
Co-Lead Organizer @ UTSC LHD
Organizer @ UTSC LHD
Web Developer @ GitHub
Does this project present a new way of doing/approaching things?
Has this project been done before in exactly the same context/form? If so, are there details that make it stand out from its competitors?
How practical is this project? Could you see it being implemented in the future?