Published using Google Docs
Hackathon App Coding Challenge Rules.docx
Updated automatically every 5 minutes

STACKUP CODING CHALLENGE RULES

  1. The Hackathon
  1. These Hackathon Rules apply to the StackUp Coding Challenge (the “Hackathon”).

1.2        The Hackathon (the "Event") is a virtual hackathon taking place during the listed dates on the Hackathon app.

1.5        Age Restrictions: Participants must be at least 16 years of age.

1.6        Geographical Restrictions: This Event is open only to legal and eligible residents of countries across the Globe, excluding standard exceptions mentioned in the StackUp Terms of Service.

  1. Teams
  1. Participants are to form Hackathon Teams and each Hackathon Team must consist of at least one (1) members and shall not exceed three (3) members.  
  2. Each Hackathon Team shall appoint one (1) Participant as the Hackathon Team’s representative.
  3. The Hackathon Team’s representative is to submit the list of members in their Hackathon Team to StackUp, by the submission deadline.
  4. Participants are strictly not allowed to participate in more than one Hackathon Team and shall only participate in one Hackathon Team during the Hackathon Event. In the event where a Participant is found to be participating in more than one Hackathon Team, StackUp is entitled, in its sole discretion, to disqualify said Participant and/or the Hackathon Team and their Submission from the Hackathon.
  1. Participants’ Code of Conduct
  1. The Participants consist of people from countries around the world and we expect all Participants to respect the diversity of our community. Content containing illegal or excessive obscene or foul language, excessive violence, nudity, or sexual activity will be flagged and removed. Content that is abusive or likely to be offensive to others may also be flagged and removed.
  2. As the Hackathon is an ongoing process over a period of time, Hackathon Participants, StackUp may not be as responsive as you may hope for, due to reasons such as, amongst others, time zone differences, personal commitments outside the Hackathon, and work or education commitments. Therefore, we seek understanding from all involved parties in the Hackathon to respect each individual's boundaries, external commitments or circumstances. Acts of disrespect to Participants, StackUp, includes, but is not limited to, constant messaging within an unreasonably short period of time, flooding the Hackathon main channel(s) without providing a reasonable amount of time for responses to be made, use of abusive and/or demanding language, etc.
  3. We value integrity and expect you to represent who you are and your Hackathon Team honestly in your submissions and in any forms that we share with you during the course of the Hackathon.
  4. We celebrate makers, creators, developers and want to help each of you who are part of this community grow and improve your skills. When you share feedback, please keep it constructive. Any content that is abusive, threatening, expresses hatred, or is likely to offend others is unacceptable and may result in the content being removed, the suspension or termination of your account, or disqualification from the Hackathon, at the sole discretion of StackUp.
  5. Do not share or post any personal or private information about you or any other person. This includes any photos (unless you have explicit permission to do so), phone numbers, addresses, location details, personal email, social media profiles.
  6. Our community and platform showcase software, participate in virtual challenges and hackathons, share your ideas, code, get feedback and motivation. Do not upload anything unrelated, explicit, repeatedly post the same thing or post anything that is not relevant to the event that you are participating in or send excessive, unsolicited messages to other users.
  7. The Participant may be disqualified for any of the following actions, with or without warning, at the discretion of StackUp: (i) verbal abuse of another participant or StackUp staff; (ii) breach of any agreement entered into in connection with the Hackathon; or (iii) violating the spirit of the Hackathon. If StackUp has reason to believe that the Participant has compromised the integrity or the legitimate operation of any Hackathon, including, without limitation, by cheating, hacking, creating a malicious bot or other automated program, or by committing fraud in any way, the Participant may be required to discontinue participation in that Hackathon.
  1. All disqualification decisions are final and not subject to appeal.
  1. Project Rules
  1. The hacking period and Submission Period for the Hackathon shall be from the start of the hackathon date to the submissions deadline.
  2. The Hackathon Team’s representative must submit the Team’s Submission to the Hackathon app’s submission portal during the official Submission Period. .
  3. You and your Hackathon Team are strictly not allowed to submit Submissions that are not created by you or that are not what you have worked on during the period of the Hackathon. If there are other projects that could be great resources, kindly reach out to StackUp and request to add such projects to the resources.
  4. You and your Hackathon Team are not allowed to work on your project before the hacking period stipulated in Rule 4.1. Each team is required to use version control for your code throughout the course of the Hackathon. Any repositories with single commits of large files without proper history will be default assumed to be unqualified unless proven otherwise.
  5. Each Submission will be judged solely on what you and your Hackathon team has worked on during the duration of the Hackathon. Each team is required to share the source code of the Submission on the Submission Portal.
  6. If you or your Hackathon Team are using an existing project, you must credit the project by disclosing all details of the same and outline the improvements made to the project in your Submission, provided always that the Intellectual Property Rights of such existing project is exclusively owned by you or a member of your Hackathon Team. Failure to comply with this Rule 4.6 may result in the disqualification of you and your Hackathon Team and the team’s Submission.
  7. If someone has helped you or contributed to your Submission, you must credit them in your Submission for their contribution.
  8. Make sure to check the license of any public repository before you use it for your Submission and give the appropriate credit to that repository and the creator in your Submission. You cannot utilize content that violates any third party’s rights (including privacy, personality, moral or intellectual property rights, or that constitutes copyright infringement) unless you have acquired the necessary rights to do so or the content is subject to an open source license.
  9. When making your Hackathon Submission, you must ensure that your Submission adheres to the Fresh Code Rule (as defined below) or that you have the right to use any existing content that forms the whole or a part of your Submission. This includes, without limitation, images, lines of code or demonstration videos in your Submission.
  10. You must ensure that you have permission from all persons and/or entities who worked on or were engaged to work on or contributed in any respect to the Submission or any part thereof. Otherwise, please do not use such material and do not upload the same in your Submission.
  11. The Submission must be in English or otherwise accompanied by an English translation of all materials included in the Submission, including but not limited to, demonstration videos, text descriptions and testing instructions;
  12. The Submission must include testing instructions for purposes of judging;
  13. The Submission must not contain any Harmful Code. “Harmful Code” means any computer programming code constructed with the intent or likelihood of damage to or interference with other computer programs, data files or hardware, without the knowledge or consent of the computer user, and includes self-replicating and self-propagating program instructions such as viruses, worms, Trojans, backdoors, or the like;
  14. The use of AI tools are approved for the Hackathon as long as no personal, confidential, or restricted information is used with the AI tool. Participants and/or their Hackathon Team who use AI technologies do so at their own risk. In the event where the Participants and/or their Hackathon Team exposes proprietary, sensitive, confidential, or personally identifiable data to an AI tool, StackUp reserves the right to disqualify such Participant and/or their Hackathon Team from the Hackathon and any consequences arising thereof shall be solely borne by the Participant and/or their Hackathon Team.
  15. Unless otherwise stated, teams should only attempt one challenge statement and make one submission.
  1. The Fresh Code Rule
  1. All Hackathon Teams should strictly adhere to the fresh code rule, under which the following should be adhered to (the “Fresh Code Rule”):
  1. What can be done before the Hackathon
  1. Hackathon Teams can create wireframes, designs and user flow.
  2. Hackathon Teams can pre-train models or gather data sets prior to the event.
  1. What must be done during the Hackathon
  1. All code submitted as part of the Submission must be written during the Hackathon and submitted before the expiry of the Submission Period (as per Rule 4.1).
  1. Provided that the Fresh Code Rule is adhered to, Participants and/or their Hackathon Team are allowed to use any coding languages or open-source libraries as part of their Submission.
  1. Intellectual Property Rights

Save as otherwise agreed with the relevant Hackathon Team (including under these Hackathon Rules and the StackUp Terms of Service), all Intellectual Property Rights subsisting in a Hackathon Team’s Submission shall remain vested in such Hackathon Team.

  1. Prizes
  1. The prizes for the Hackathon are denominated in USD, and includes all applicable taxes and fees associated with prize receipt and/or use by the prize recipients. Prize recipients will have their reward deposited into their StackUp wallet.
  1. All prize recipients will be contacted by the stipulated date and prize administration will take place within the next fifteen(15) working days after the Hackathon has concluded.
  1. Prize distribution may be delayed due to processing time or where there are any issues with the information provided by a recipient of a prize.
  2. You agree that StackUp shall be deemed to have discharged its obligations in relation to the administration and distribution of prizes under this Rule 7 upon effecting the administration and distribution of such prizes. Save in the case of fraud, gross negligence or misconduct, StackUp shall not be responsible for any delay and/or failure to receive the prizes.
  3. Prizes are non-transferable and no substitution will be made.
  1. Removal of Content and Terms

StackUp reserves the right to remove your content and/or block or remove your account from the platform if we believe that you have violated any of the guidelines mentioned above.