Official Rules

Please review all rules. These rules are subject to change. Final rules for the hackathon will be distributed at the hackathon.

Teams. Teams shall consist of two or more people. Participants must be onsite (remote participation is not allowed). Participants may form teams in advance of the hackathon or at the hackathon. Teams are not permitted to begin coding or work on their submission until 6:01 pm on February 5, 2016. Teams may discuss ideas and concepts before the hackathon officially begins. Teams are encouraged, but not required, to include a lawyer or current law student on their team.

Access to Wireless Network. Every participant who plans to hack will need guest access to the UALR wireless network. Participants must register through Devpost for guest access. Any laptop or other device used to hack cannot have peer-to-peer software installed. The UALR network will automatically disconnect any guest user with such software and new guest access cannot be granted after the hackathon begins.

Alcohol, Tobacco, and Code of Conduct. No alcohol will be served or allowed at the event. UALR Bowen School of Law is a smoke-free campus. Smoking is only allowed in the designated area just outside the law school parking lot. Participants shall conduct themselves in a professional and inclusive manner. 

Submissions. All submissions and the work product must be produced within the time span of the hackathon. Judges may, in their sole discretion, disqualify any submission that they have reason to believe was substantially created before the start time of the hackathon. Submissions are due by 10:00 a.m. (CST) on February 6, 2016, and must be submitted through Devpost. There will be no extensions of the deadline.

Project Presentations. On Saturday, February 6, beginning at 10:00 a.m. (CST), at least one member of each registered team must appear in person at UALR Bowen School of Law, Friday Courtroom, Room 114, 1201 McMath Avenue, Little Rock, AR 72202, to present and explain their team’s submission. The presentations should explain the issue or problem and how the submission helps to solve the issue. The order of presentations will be determined by lottery. Presentations may not last more than 5 (five) minutes.

Prizes. Teams will divide cash prizes equally among that team’s members. Participants must have a valid social security number to be eligible for a prize. Participants are responsible for all taxes associated with winning a prize. Winners will be required to complete tax forms prior to receiving a prize. All decisions of the judges are final.

Media Release. As a condition of participation in the hackathon, participants grant organizers, sponsors, and members of the media rights to publicly disclose competition and event information, explain and review entries and ideas developed and presented during the event, identify the names and current cities of residence of members of the winning and second place teams, and to display any event related photos, screen shots, and links to publicly available demonstrations of event entries and materials.

Intellectual Property. All code developed at the hackathon will be open source code. Any intellectual property developed during the hackathon will belong to the team that developed it. Each team should have an agreement among the team members regarding the ownership of the team members of the intellectual property, but such an agreement is not required as a condition of participating in the hackathon.

 

Judging Criteria

15% Execution
To what degree does the final product work as of the end of the event?

15% User-Friendly
How user-friendly is the product for the end user?

35% Innovation
How unique is the product from everything else out there?

35% Impact
How critical is the need addressed by the product? What problem does the product? Does it have the ability to grow and change over time?