The theme for Sprint 0 will be Developer Tools. This will be your first full sprint! It can feel a little overwhelming but here are a number of aims you should achieve.
During this sprint, you'll work to achieve the following:
- A project associated with Developer Tools
- Experience using Git and GitHub
- Detailed project management using Project Boards on your repository
For this Sprint, the theme will be Developer Tools. You're probably wondering what that means, but don't worry! Our industry experts are here to help. In the video below, Ian made a great video explaining what Developer Tools are and what you should focus on. Find that below!
This is a great opportunity to explore new technologies you may be unfamiliar with. Maybe you try and build your first command line interface (CLI), or make a tool to help developers keep on track of tasks without having to leave the terminal. The possibilities are endless. We'd encourage you to try something different, as this teaches you something you and widens your skill set!
You must be an Explorer Fellow of the MLH Fellowship (Batch 2) in order to be eligible to participate.
As you know, you have until the beginning of your hackathon final demos to work on your project. As part of your submission, you’ll need to complete the following:
- Publish your project on GitHub with an appropriate Open Source license
- Record a 3-5 minute video overview and demo of your project.
The full page can be found here.
Publishing Your Project on GitHub
Before demos the repository should be set to public and should have an appropriate README and LICENSE included. One of the criteria that you will be evaluated on is your use of Git and GitHub best practices, so also try to make sure your commit history is visible on the repository.
Recording a Demo Video
You can use something like OBS to record your screen to showcase your project. You don't need to make any slides, but instead show us what your project does (regardless of how polished it is). Upload this to YouTube afterwards but make sure it's unlisted or public.
Arduino Kit per team member
Best use of the Internet Computer
iFixit Tool Set per team member
Submitting to this hackathon could earn you:
Pod Leader, Pod 2.1.0 and Pod 2.1.1
Pod Leader, Pod 2.1.2
Pod Leader, Pod 2.1.3
How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go "Wow"?
Did the team put thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is.
Does the hack work? Did the team achieve everything they wanted?
Did the team stretch themselves? Did they try to learn something new? If a team which always does virtual reality projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.
Open Source Best Practices
Did the team apply the Open Source best practices including, but not limited to, use of branches, pull requests, reviewing each other’s code, writing a comprehensive README, and using issues to track tasks.
Theme (Developer Tools)
Did this team actually create a project that fit the theme of the Hackathon, Developer Tools & Productivity? Did they solve a real problem in this space?