fbpx
Skillnagar - Grab a new skill today!

Rules

Please read all the rules carefully!

  1. Starting date for this hackathon is 5th July 03:00 PM
  2. Ending date for this hackathon is 18th August 11:59 PM
  3. Hackathon mode – online, no need to visit any special venue
  4. Team size – 1 – 4(max)
  5. Teams should be made up exclusively of students (must have a valid college identification) who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
  6. Teams can of course gain mentorship from technology experts
  7. Teams can use an idea they had before the event.
  8. Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
  9. Teams can work on an idea that they have worked on before (as long as they do not re-use code).
  10. Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
  11. Teams must stop hacking once the time is up. Teams will be given grace of 12 hours to fix any bugs or issues
  12. Projects that violate the Code of Conduct are not allowed.
  13. Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour.
  14. Organiser reserve all right to make amendments in the rules and various process of the event
  15. Winner will be decided at the sole discretion of the committee

Judging Criteria

Teams will be judged on these four criteria. Judges will weigh the criteria equally. During judging, participants should 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”?
  • Completion: Does the hack work? Did the team achieve everything they wanted?
  • Learning: Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before? 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.

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

It’s important to note that these judging criteria do not include:

  • How good your code is. It doesn’t matter if your code is messy, or not well commented, or uses inefficient algorithms. Hacking is about playing around, making mistakes, and learning new things. If your code isn’t production ready, we’re not going to mark you down.
  • How well you pitch. Hacking is about building and learning, not about selling.
  • How good the idea is. Again, hackathons aren’t about coming up with innovative ideas. It’s about building and learning.
  • How well the project solves a problem. You can build something totally useless and as long as you’re learning and having fun, that’s a good hack! Sometimes a pointless project is one of the best hacks!

So don’t worry about coming up with the next big idea or building the next Facebook. You’ll have plenty of time for that outside the hackathon. just focus on learning, having fun, and making new friends. At the end of the day the skills you learn and the friends you make might lead to the next big thing—but you don’t have to do that to win a hackathon.

Preventing cheating

The following is a guide of actions to be taken in the case of an accusation that a team cheated or otherwise violated the rules of competition. Violations of the Code of Conduct is handled at hi@skillnagar.com Accusations of cheating may include but are not limited to:

  • A team using somebody else’s code
  • A team misrepresenting the work they did
  • A team having too many team members
  • A team using code that was written outside the event

To determine the validity of cheating instances Major League Hacking defers to the rules adopted by the individual event. If the event did not adopt a unique set of rules.

Remember!

The competition is just a part of the hackathon. To make the most out of the event, try something new, teach other people, and make new friends!

Stay in touch

If you have any questions or doubts, feel free to reach us on various social networks!