Hackatra Challenge (the “Hackathon”) Official Rules

NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR WIN. 

SUBMISSION OF ANY ENTRY CONSTITUTES AGREEMENT TO THESE OFFICIAL RULES AS A CONTRACT BETWEEN ENTRANT (AND EACH INDIVIDUAL MEMBER OF ENTRANT), THE HACKATHON SPONSOR, AND DEVPOST.

1. Dates and Timing

  • Submission Period: March 18th, 2022 (6:30 pm IST) – March 25th, 2022 (10:00 am IST) (“Submission Period”).
  • Judging Period: March 26th, 2022 (3:00 pm - 5:00 pm IST) (“Judging Period”).
  • Winners Announced: On or around March 26th, 2022 (7:00 pm IST).

2. Sponsor and Administrator

  • Sponsor: ekatra learning inc
  • Administrator: Devpost, Inc. (“Devpost”), 222 Broadway, Floor 19, New York, NY 10038

3. Eligibility

A. The Hackathon IS open to: 

  • Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”);
  • Guardians of students under the age of 18 (or under the age of majority in their jurisdiction of residence at the time of entry);
  • Teams of Eligible Individuals (“Teams”); and
  • Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry.
  • Employees of companies designated as a Hackathon Partner and listed on the Hackathon Website (“Partner Employees”).

(the above are collectively, “Entrants”).

An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis. If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.

B. The Hackathon IS NOT open to: 

  • Individuals who are residents of, or Organizations domiciled in, a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, Brazil, Quebec, Cuba, Iran, Russia, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control). 
  • Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotion Entities”).
  • Employees, representatives and agents** of such Promotion Entities, and all members of their immediate family or household* excluding Partner Employees.
  • Any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*.
  • Any Judge (defined below), or company or individual that employs a Judge.
  • Any parent company, subsidiary, or other affiliate*** of any organization described above.
  • Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Sponsor and/or Administrator, a real or apparent conflict of interest. 

*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year. 

**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.

***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.

4. How To Enter 

Entrants may enter by visiting hackatra.devpost.com (“Hackathon Website”) and following the below steps:

  • Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to make your Submission.
  • Entrants will obtain access to the required developer tools and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the license agreement related thereto. Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon.
  • Create a video that includes footage that explains your project’s features and functionality through a comprehensive demonstration.
  • Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Submission Period and follow the requirements below.

5. Project Requirements

  • What to Create: Entrants must select a problem statement from the provided list found here: [Hackatra GitHub Repo] (each a “Problem Statement”).
  • Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.
  • Platforms: A submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements. 
  • New & Existing: Projects must be either newly created by the Entrant or, if the Entrant’s Project existed prior to the Hackathon Submission Period, must have been significantly updated after the start of the Hackathon Submission Period.
  • Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them.
  • Testing: The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. 

Entrants must:

  • Provide access to the Project by making it public or share access to  vruksheco GitHub account.
  • Include all your relevant Project code, and a README with getting started instructions that allow viewers to test your submission. 

6. Submission Requirements.

Submissions to the Hackathon must meet the following requirements:

  • Include a Project built with the required developer tools and that meets the above Project Requirements.
  • Include a text description that explains the features and functionality of your Project.
  • Declare the Problem Statement of your Project. 
  • Declare if Entrant is a Partner Employee (if an individual) or that any team member is a Partner Employee (if a Team or Organization). If declared, the Submission will not be included in the list of Finalists defined in Section 6 and will only be eligible for the Partner Employee Prizes.
  • Provide a written defense of your project, explaining its strength in each of the four judging criteria (see Judging and Criteria below). Provide supporting facts and statistics as appropriate.  The response for each criterion may be up to 250 words.

7. Language Requirements

All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. 

8. Prizes: The winning teams get cash prizes of INR 20,000 (~USD 260), INR 10,000 (~USD 130), INR 5,000 (~USD 65) for top three positions, upon successful implementation of the solution with the ekatra project. This entails merging the solution with the existing ekatra project within 90 days from the closure of the hackathon. The team can pursue this under an internship or consulting position with the organization, and the member(s) of the team will get an opportunity to interview for a full time position or act as a consultant for the company. The prize will go to the team with a fully functional solution to the problem statement, and clean documentation, the organizers reserve right to deny any prize monies in case the solution is not implemented by the team. 

9. Intellectual Property: Your Submission must: (a) be your (or your Team, or Organization’s) original work product; (b) be solely owned by you, your Team, your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. An Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software, provided the Entrant complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source software. By entering the Hackathon, you represent, warrant, and agree that your Submission meets these requirements.

10. Financial or Preferential Support: A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.