Rules

  1. All submissions must be original and must not have been submitted for previous Hackathons. The code submitted will be checked online and points will be deducted accordingly, depending on the extent of plagiarism
  2. Refer to submissions format for specifications on allowed submissions.
  3. All submissions must be done by 9th November 2024 at the latest, 13:30 via Microsoft Forms and Github. Any group that fails to submit before the stipulated time will be disqualified.
  4. All groups must submit some software even if it does not function. This serves to provide proof of their ideas as Creativity and Usefulness account for 40% of the total score in the Judging Criteria.
  5. All participants will be allowed to take reference from existing code online, but they must adapt the code accordingly. Direct plagiarism, or making slight changes to existing/public projects is not allowed. Participants are encouraged to make their repos private to prevent possible cases of plagiarism. 
  6. Judges will request participants to run their code as they explain their project. Each team has strictly 7 min of presentation time (2 minutes for demo and 5 minutes for presentation is recommended) and 3min for Q&A.
  7. Except a valid reason is provided, participants are expected to be present for the entire duration of the hackathon.

Submission Format

  1. Submission of all source code will be as a link to a public GitHub repository, which should contain
    1. Their code/application
    2. Everything necessary to run the application on the target architecture (Windows 11, Android, or x64 Linux)
    3. Clear and detailed instructions to run the application in the form of a README file
    4. .exe binary, .jar, or .apk files are preferred for submission. However, it is fine if such file types cannot be produced as long as the program can be run on either a Windows 11, Android, or x64 Linux machine.
  2. Groups will have to submit the hash of their latest commit to prove that no modifications are made after the deadline.
  3. The organising team will be providing guides on how to use GitHub which includes basic operations such as creating a commit, or obtaining the hash of their commit to ensure that groups do not face difficulty in submitting their code. Groups can also reach out to any of the facilitators if they need help for submitting their code.
  4. Groups are to submit their presentation as a PPTX / PDF file. The presentation should include key information about the app such as its functionalities, and screenshots if any.
  5. The individual size of the files is not to exceed 1 GB.
  6. All deliverables including videos, slides and the link to the Github repository will be submitted via Microsoft Forms. 
  7. Submissions will not be accepted after the stipulated time, nor will modifications to the submissions. In the case of duplicate submissions, the last submission before the deadline will be taken.
  8. Groups are only to submit under their own team. Doing otherwise will result in disqualification.