Scribd
Upload
6 views

Hackathon rules

The hackathon rules require participants to treat everyone with respect and limit teams to a maximum of 5 C&P course students. All project work must be completed during the event, and while teams can use pre-existing ideas and resources, they cannot work on projects prior to the hackathon. Disqualification may occur at the organizers' discretion for rule violations.

Uploaded by

kumarpraveen60899
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

Hackathon rules

The hackathon rules require participants to treat everyone with respect and limit teams to a maximum of 5 C&P course students. All project work must be completed during the event, and while teams can use pre-existing ideas and resources, they cannot work on projects prior to the hackathon. Disqualification may occur at the organizers' discretion for rule violations.

Uploaded by

kumarpraveen60899
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Hackathon rules

1. Participants must treat all team members, competitors, judges, coaches, volunteers, etc., with respect and courtesy.
2. Hackathon teams will be a maximum of 5 people.
3. Students can freely make up a team but teams should be made up exclusively of C&P course students.
4. All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.
5. Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
6. All work on a project should be done during the hackathon.
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.
9. 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.
10. Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after
time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it’s
okay to fix that. Making large changes or adding new features is not allowed.
11. Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking
the Competition Rules.

You might also like