Home

Welcome to the HackathonMunon wiki!

You can use this as a reference to know what to expect at a Hackathon Muñón or as a guideline to organize your own. Also feel free to use this as a template and remix it, just like we did with the MLH guidelines.

Schedule

1. Hack: Create and network non stop until the time is up.
2. Review: Rate everyone based on how you perceive their skill, execution, and innovation.
3. Split the pot: Get a reward corresponding to your rating compared to all participants.

Story

The Hackathon Muñón was originally created at San Pedro Sula, Honduras by the local technology community around 2013. There have been 4 events to date and the aim has always been to have a good time while creating, networking and getting feedback on what we do. During every event, all participants create a pot by paying an entry fee, at the end of the event that pot will be distributed proportionally to how they did at the hackathon with the help of peer review. So for example, you could pay 10 bucks to enter and at the end, you would get 25 back, or 3 back depending on how the other participants perceive your work. The topics and duration varied from event to event, from 8 to 12h and the topics have been 100% freestyle, game dev, Angelhack warmup and “finish that project that has been idle for a while”. We found out that we could automate the process with the help of smart contracts so on 2019 we are doing a 5th Hackathon Muñon but this time running on top of Ethereum.

Rules

1. You as a participant can form and join as many teams as you like.
2. There is no maximum or minimum team size.
3. This is not a themed hackathon. You can pick the theme you want. For example: videogames, food, biz, IoT etc...
4. Teams can start a fresh new project or work on something they had before the event. This includes adding a new feature to a project, or continuing a WIP.
5. Teams must stop hacking once the time is up.
6. Every participant will rate each other from 0 to 5 being 0 the worst rating and 5 the best. Remember: you are going to rate your peers individually, you are not going to rate the projects. Demos
7. After hacking finishes, teams will show their projects each other. You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. All team members will explain his contributions to the projects and every participant will rate them individually. If you participated on multiple projects, communicate it! So the participants don’t rate you until you presented your work on all projects.

Judging criteria

Participants will be judged on these four criteria. During judging, every participant will try to describe what they did for each criterion in their project.

• Technology: 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"?
• Design: 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 (e.g. is it easy to use or does it use a cool interface?).
• Innovation: Is the hack interesting? Is it a fresh and cool idea?
• Completion: Does the hack work? Did the team achieve everything they wanted?
• Team work: Was the participant able to express his idea in a comprehensive way? Extra points for hacking as part of one or multiple teams!

These criteria will guide participants but ultimately, everyone is free to make decisions based on their gut feeling of which projects are the most impressive and most deserving.