Washington University in St. Louis Student Technology Services is thrilled to host its first ever Hackathon! Our goal is to bring together students for a weekend of fun, and the only requirements are will and skill.
All Washington University in St. Louis undergrad, graduate and doctorate students from any school or discipline are welcome and encouraged to participate. Individuals and teams of up to four people are invited. No development or coding skills required; students with ideas only are welcome to get involved!
Participants will have 48 hours to complete a project, the parameters of which will be given at the start of the competition.
STS will provide meals and drinks during the competition period, as well as the workspace at the Gregg Technology Classroom.
A panel of judges, consisting of university students, faculty and staff, will spend a week determining the winning project. The winning person or team members will each receive an Oculus Rift Development Kit 2.
All registration entries must be received by midnight on Sept. 30, 2015.
Eligibility
STS Hack is open to all Washington University in St. Louis undergrad, graduate and doctoral students.
Individuals and teams of up to four are welcome to participate.
Student Technology Services will provide meals and snacks for the duration of the Hackathon.
Any individuals who are interested in finding a teammate can visit our Google Group at https://groups.google.com/forum/#!forum/sts-hack to find someone with whom to pair.
Requirements
The goal of the STS Hackathon is to develop a new application or feature set for the STS Virtual Reality Viewer (http://sts.wustl.edu/vrv).
More requirements to come.
Prizes
Amazon Echo
Oculus Rift Development Kit 2
Devpost Achievements
Submitting to this hackathon could earn you:
How to enter
Register at sts.wustl.edu/hackathon by midnight on Sept. 30, 2015.
Packets will be distributed at the beginning of the Hackathon.
Judges
Scott Allen
Judging Criteria
-
Is the application functional? (25%)
Does it accomplish its stated goal? · Does it work as is, or does it require additional resources (code or data?) -
Is it intuitive? (25%)
Is it easy to understand? Is it easy to use? Is it creative? -
Is it impactful? (25%)
Does the application solve a real problem? How many students does it impact (few/many)? -
Is it viable? (25%)
In your opinion, would undergrad and graduate students use this application?
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
