Mafiq Foundation

Menu
donate

Code of Conduct

This hackathon is a community event intended for learning, collaboration, and engagement in the developer community. We value the participation of each member of the developer community and want everyone involved to have an enjoyable and fulfilling experience.

Accordingly, all staff and participants are expected to show respect and courtesy to others throughout the event. To make clear what is expected, all staff, participants, volunteers, mentors, and judges in the hackathon are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event.

  • Be kind to others.
  • Do not insult or put down other attendees. 
  • Participants must remain civil and polite in their engagement with others.
  • Treating other persons with disrespect is not acceptable.

Rude conduct, including belittling or insulting comments, gestures, or negative attitudes, is not acceptable.

Moreover, competitors are expected to maintain a sporting attitude. A sporting attitude is defined as:

(1) a positive attitude toward the process of competition, not just winning

(2) a willingness to maintain positive attitude and effort throughout competition without becoming cynical about or in competition

(3) a commitment to fair competition and abhorrence of attempts to gain unfair advantages

(4) an understanding that opponents are legitimately engaged in attempts to win the competition and that their attempts to win are not insulting or personal

(5) the ability and willingness to positively recognize the achievements of opponents, even when those achievements come at the expense of the competitor, and

(6) the ability to treat defeated opponents with courtesy and respect.

Do your best and believe in yourself. Participants violating these rules may be asked to leave the hackathon at the sole discretion of the organizers. Thank you for helping make this a welcoming, friendly place for all.

Competitors are expected to treat their coaches and fellow team members with a high level of respect and courtesy.

The Director of the MY-HACK platform and the designated representatives, hired or volunteer coaches are to be addressed with courtesy and respect at all times.

Competitors should understand that they are expected to comply with specific directives given by the coaches regarding any MY-HACKT business or competition.

Problems or disagreements between team members that impact event should be brought to the attention of the Director.

Questions or disputes concerning the judging must be brought to the attention of the MY-HACK Director in writing at [email protected].

Competitors are expected to comply with all applicable laws and rules. Failure to comply may result in consequences for competitors.

Adopted from the University of Washington Debates code of conduct

Rules

MY-Hack is hosted in-person. MY-Hack’s theme is “Social Good”. We want MY-Hack to be an inclusive environment where you can learn new things, meet new people, and receive support with the end goal of creating a product for social good! 

Rules

*Please be respectful to everyone, including fellow competitors. *If you need to enter or exit a room, please wait to do so in between presentations, as to be respectful to the presenter. *Judges are not permitted to open or close doors, so that they may focus on the competitor’s presentation without distraction. *Participants that are waiting for their turn must remain silent. *Do not distract judges, the presenter or audience. Parents are not permitted to raise questions about the judging during the event. Any dispute must be submitted to [email protected] in writing Jazakum Allahu Khairun for your cooperation!

Fine Arts

Giving wings to the artists who’d like to take it up as a career or just a hobby. Our students are trained by professionals who help them develop, learn and polish their skills while at school.

Humanities

The study of ancient and modern languages, philosophy, history, and more. We take pride in offering top humanity courses from a dedicated and trained staff.

Science

The study encourages scientific reasoning, discoveries and inventions. Great teachers and well-equipped laboratories help students explore, discover and experiment new things under the best supervision.

Mathematics

Understanding the game of numbers and logic to solve real world problems. Learn mathematics from scholars and university toppers who not make it interesting, but also fun to learn.

Virtual Event Guidelines
  • 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 the first day of MY-Hack after the team has registered. However, we encourage you to brainstorm ideas and create wireframes/mockups via our private Facebook group.
  • Any software development tools, IDE, and/or programming language can be used for the event. If a team member uses a purchased tool licensed to him or her and the license is not transferable to other members, the member’s team must choose one available to all developer teams.
  • 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.
  • 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.
  • Project design/assets can be created before the start date of the hackathon. All assets should conform to the Creative Commons License agreement standard or are freely available and you have permission or license to use them. Proof of permission must be given upon request.
  • Assets, SDKs, APIs or other tools or components available under a trial license may be used.
  • A team can submit only one entry for the hackathon. Participation at the hackathon is subjected on a “per-team” basis meaning you are not allowed to be on more than one team at the event.
  • Any intellectual property developed during and within the scope of the hackathon must be open source and licensed under one of the licenses referenced in https://opensource.org/licenses.
  • 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.
  • A team can use multiple licenses in the application. For example, the public code used could be licensed under the Apache license agreement whereas the code written by the team for the application is licensed under the MIT license agreement.
  • A team may not code applications that violate the code of conduct. For example, racially insensitive ideas for an application will automatically be disqualified.
  • All teams should have a team name and be registered with Devpost.
  • The Devpost team page listing should have the following:
    • The team lead must list a mobile phone number on the teams DevPost page (after judging is complete the number may be removed)
    • All team members will be listed with brief biographies.
    • Short abstract of the project
    • The hackathon theme (See https://my-hack.devpost.com/) and sub-category if applicable
    • Answers to the following:
      1. What inspires you? 
      2. What does the product do?
      3. What development tools, libraries, assets did you use to build it?
      4. What challenges have you run into?
      5. A link to the application or recording of the working app on YouTube
      6. How does the product facilitate social good?
      7. What did you learn in the process?
  • All projects should be submitted to the devpost page before judging begins on the second day of the hackathon. Failure to submit will result in disqualification. should commit regularly throughout the hackathon to the team repository. 
  • All project 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.
  • When development ends, at least one member from each team will meet with the judging team for a brief review of their submission and to confirm that the team’s Devpost page has been correctly updated.
Scroll to Top