Welcome to Retrospective Week! This is a chance to get your first taste to contributing to Open Source. You'll get the opportunity to give back to the community by adding features, fixing bugs, or adding documentation to projects built by Fellows!
By the end of the week, you will have:
- Add features / bugs to GitHub Issues on one of your Explorer Projects repositories
- Made a Pull Request for one of your Explorer Projects
- Made a Pull Request to another teams Explorer Project
This week is about improving the projects everyone worked on over the last few weeks. You'll be working in pairs this time, instead of teams. In your pairs, you can work on projects together, but can also split up issues between you. You'll be counting your contributions as a team on your submission.
Your challenge is to add as much impact to projects as possible. Impact means making a difference to projects as a whole, not the impact you make per project. You could work on a load of small pull requests, or a couple of larger ones. The choice is up to you!
We'll be giving some swag to the highest impact pairs.
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:
- Record a 3-5 minute video overview and demo of your contributions.
- Link to all of your Pull Requests somewhere in the Devpost writeup.
The full page can be found here.
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.
$100 in prizes
Best Contributions using DFINITY
HyperJuice 100W USB C Charger
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
Open Source Best Practices
Did they write a detailed pull request? Did they tag themselves on the issue to show they were working on it.
How impactful are these contributions?