Event Rules

Eligibility

This hackathon is open to:

  • Students who are studying in any Singapore educational institution, anywhere from primary school to graduate studies, and stay in Singapore
  • Anyone awaiting entry into an educational institution (including NSFs and PhD candidates) and stays in Singapore

We are unable to accommodate international participants this time as prizes and swag will only be delivered to addresses within Singapore.

Teams

  1. A team can consist of up to 4 members.
  2. Teams are formed only after your individual registration is accepted.
  3. You can form teams with your friends or form teams with other accepted participants.

Project

  1. You can build whatever you want!
  2. The hackathon lasts 24 hours - you can begin hacking when the timer starts, and you must stop, and must have submitted the project to Devpost when it ends.
  3. All work on your project should be done at the hackathon.
  4. You are allowed to use an idea you had before the project.
  5. You can work on an idea you have worked on before (as long as you do not reuse code).
  6. You are allowed to use frameworks/libraries/open-source code in your projects. Remember to credit your sources appropriately in your submission!
  7. Adding new features to an existing project is allowed, but you should clearly communicate to the judges what work was accomplished during the 24 hours of the hackathon.
  8. A team can consist of up to 4 members.
  9. Teams are formed only after your individual registration is accepted.
  10. You can form teams with your friends or form teams with other accepted participants.

Project Integrity & Cheating

Please refer to the Project Integrity & Cheating section below.

Intellectual Property

Any intellectual property developed during the hackathon will belong to the team that developed it. We expect that each team will have an agreement between themselves regarding the IP, but this is not required.

Presentation

After the hackathon finishes, your team is required to submit your project to Devpost. Your team will then present twice to different judges. You should plan for a presentation length of ~3 minutes. There will be time allocated for Q&A.

You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It’s okay if you didn’t finish your hack - that happens all the time!

Judging Criteria

Due to the open-ended nature of this hackathon, the judging criteria will be based on four main factors. Your team will have to be able to fully articulate the features of their projects in order to fit the following categories:

  1. Creativity (40%)
  2. Technical Accomplishment (30%)
  3. Polish (20%)
  4. Usefulness (10%)

These criteria will guide the judges, but they are ultimately free to make decisions based on their gut feeling of which projects are the most impressive and deserving. So, do try to impress them!

Code of Conduct

By participating in Hack&Roll 2021, you agree to abide by the NUS Hackers Code of Conduct. Failure to comply with the above-stated CoC may result in your team’s disqualification.

Project Integrity & Cheating

Cheating is a serious offence and goes against the spirit of Hack&Roll. If found, offenders could face consequences such as but not limited to: returning all prizes won (if any), a ban from future iterations of Hack&Roll etc.

If a team is suspected of cheating, they will be obliged to provide the source code, version control history (if applicable) and any other pieces of information that will help the organizing team to make an informed decision.

However, we also recognise that the definition of cheating can be a little vague, and as such have provided a short explanation to better address this issue.

Cheating

The Hack&Roll website defines a proper project as “Build something new. You may reuse code for specific components, but recycling an entire project is not okay.”

Given that Hack&Roll is a 24-hour hackathon, some degree of code reuse is inevitable. To this end, teams may opt to use frameworks and libraries. For example, for a webpage, a team may consider using the standard create-react-app tool to come up with a website, and even component libraries such as react-bootstrap. For a machine learning project, you may also have already pre-trained a model for your project given the time constraints of the hackathon.

Changes to the README file or downloading packages are also permissible. However, the team should not customize the project prior to the start of the hackathon. For example, this would include changes such as writing your own components, stylesheets, especially if they are specific to the product you plan to build during Hack&Roll.

Moreover, any libraries/frameworks/dependencies used should be made clear on the DevPost submission and to any judges so that they will be better able to judge the merits of your project.

The above applies to teams who are planning to build their own products from scratch. A significant number of Hack&Roll participants however, have personal boilerplate templates or are planning to build on a previous project.

This is also fine. However, such teams should include these frameworks/projects with the other libraries/frameworks/dependencies in the DevPost submission. Furthermore, teams should also provide a link to the original project/template/framework used, so that the organizing team and judges can accurately see the amount of work done during the hackathon duration. This is to prevent instances of teams submitting great projects that turn out to be a few lines of code layered on top of an already advanced product.

For hardware teams, please do take a picture of the unfinished product before the start of the hackathon so that judges will be able to note the amount of work done during the hackathon.

There is also a zero-tolerance policy for plagiarism and it will result in an instant disqualification.

Further Actions

The organizing team has the final say on what constitutes cheating in the event of a dispute.

It would be extremely unpleasant if the organizing team has to disqualify any projects at the end of the hackathon, and we do not enjoy doing it. If you have any questions regarding code reuse for your project, please DM one of the organisers on Discord, or email us at coreteam@nushackers.org. We are more than happy to answer any such questions so that your efforts during the hackathon do not go to waste. Please provide any information that would help us along with email, such as the source code for software projects or the list of equipment used for hardware projects.

Effective date: 7 January 2021
Last updated: 7 January 2021