Eligibility

1. Participants from all backgrounds, genders, and geographies are welcome. The age restriction is limited between 18-35. In case you are under 18, your parents/legal guardian should contact the hackathon to request a waiver authorizing you to participate in the hackathon.
2. The Hackathon is a virtual hackathon.
3. Committee members are not eligible to participate in the hackathon. They may, however, assist teams and mentors during the coding/development phase.
4. Participants need to reside legally in South Africa.

Team Formation

1. Teams must consist of at least 4 team members to a maximum of 6 members.
2. All teams should have at least one designer and one member with gamification capabilities.
3. Changes to team members are not permitted after the submission closing date. Exceptions can be made on a case-by-case basis as decided by the rules committee.

Project Development

1. No development may start before the actual date and time of the event. Any teams that violate this rule will be automatically disqualified. The first line of code should be written on or after 4 May 2023 at 8 am after the team has registered. However, we encourage you to brainstorm ideas and create wireframes/mockups.
2. Any software development tools, game engine, IDE, and/or programming language can be used for the event. If a team member uses a purchased tool licensed to him nor her and the license is not transferable to other members the member’s team must choose one available to all developer teams.
3. To ensure a level field for all contestants, all code must be created only at the hackathon. You are permitted to use publicly developed and openly licensed API’s and SDKs for your project.
4. You will only be able to use a pre-public release of a product in developing your project if you bring at least one extra version that can be used by other teams in the Hackathon, and provide any user support needed to teams using the device.
5. Assets, SDKs, APIs or other tools or components available under a trial license may be used.
6. A team can submit only one entry for the hackathon. Participation at the hackathon is subject to a “per-team” basis meaning you are not allowed to be on more than one team at the event.
7. Any intellectual property developed during and within the scope of the hackathon is solely owned by the FSCA. This clause is applicable to all participants, and not just the winning team and runners-up.
8. The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. The public code used inside your application should also list the licenses the code is subjected to.
9. A team may not code applications that violate the code of conduct. For example, Racially insensitive ideas for an application will automatically be disqualified.

Project Submission

1. All teams should have a team name and be registered.
2. All team members will be listed with brief biographies.
3. Short abstract of the project
4. The hackathon theme - Promoting SMME growth through gamification.
5. Team location is virtual, all software needs to be declared:
   1. SDKs used in the project
   2. APIs used in the project
   3. Any assets used in the project
   4. Any libraries used in the project
   5. Any components not created at the hackathon
   6. A link to the team Github repository
6. All projects should be submitted to the hackathon GitHub account (TBA) before judging begins on 5 May 2023. Failure to submit will result in disqualification. should commit regularly throughout the hackathon to the team repository.
7. All projects submissions will be randomly code-reviewed. Applications will be spot checked by code reviewers. All the projects selected by the judges as finalists will be code reviewed to confirm that the code is original work created at the hackathon and all components and assets conform to the licenses allowed in these rules.
8. When development ends at least one member from each team will meet with the judging team for a brief review of their submission. A presentation is required. Attendee Code of Conduct
9. Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, previous hackathon attendance or computing experience (or lack of any of the aforementioned).
10. We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery are not appropriate for any hackathon venue, including hacks, talks, workshops, parties, social media and other online media. Hackathon participants violating these rules may be sanctioned or expelled from the hackathon at the discretion of the hackathon organizers.
11. Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, or religion, sexual images in public spaces, deliberate intimidation, stalking, following, photography or audio/video recording against reasonable consent, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
12. Photography is encouraged, but other participants must be given a reasonable chance to opt out from being photographed. If they object to the taking of their photograph, comply with their request. It is inappropriate to take photographs in contexts where people have a reasonable expectation of privacy (in bathrooms or where participants are sleeping). All participants are required to adhere to the Protection of Personal Information Act (POPI Act).
13. Participants asked to stop any harassing behavior are expected to comply immediately. As this is a hackathon, we like to explicitly note that the hacks created at our hackathon are equally subject to the anti-harassment policy.
14. Sponsors and partners are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material.
15. Sponsor representatives (including volunteers) should not use sexualized clothing/ uniforms/costumes or otherwise, create a sexualized environment.
16. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the hackathon staff immediately.
17. Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon.
18. We value your attendance. If a participant engages in harassing behavior, the hackathon organizers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behavior to local law enforcement.
19. We expect participants to follow these rules at the hackathon and workshop venues and hackathon related social events.