-
Notifications
You must be signed in to change notification settings - Fork 0
/
hackathonsp14.html
executable file
·186 lines (186 loc) · 7.9 KB
/
hackathonsp14.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
<html>
<head>
<title>Hackathon | CSUA</title>
<link href="http://fonts.googleapis.com/css?family=Open+Sans:400,300,700,600" rel="stylesheet" type="text/css"/>
<link rel="stylesheet" type="text/css" href="assets/css/hackathonsp14.css"/>
</head>
<body>
<div id="header">
<div id="header-content">
<div id="title">Spring 2014 Hackathon</div>
<div id="nav">
<div class="nav-item">
<a href="http://csua.berkeley.edu/about.html">About CSUA</a>
</div>
<div class="nav-item">
<a href="http://csua.berkeley.edu/join.html">Join CSUA</a>
</div>
<div class="nav-item">
<a href="http://csua.berkeley.edu/events.html">More Events</a>
</div>
<div class="nav-item">
<a href="http://csua.berkeley.edu/industry.html">Become Our Sponsor</a>
</div>
<div class="clear"></div>
</div>
<div class="clear"></div>
<div id="slogan">The Hackathon is Coming.... with Microsoft, Meraki, and EA</div>
</div>
</div>
<div id="flyer">
<img src="assets/images/events/spring2014/hackathon.jpg"/>
</div>
<div id="information">
<div class="linkbutton">
<a href="https://www.facebook.com/events/632303930176860/">RSVP on Facebook!</a>
</div>
<div class="headers">
Time:
<div class="text">
Hacking starts at 7:00 PM on Friday, May 2nd.
You will have 18 hours to hack whatever you want.
</div>
</div>
<div class="headers">
Judges:
<div class="text">
<div class="judge">Meraki:</div>
<div class="judge">Rackspace: Mary Stufflebeam</div>
<div class="judge">EA:</div>
</div>
</div>
<div class="headers">
Schedule:
<div class="text">
<div class="day">Friday, May 2nd
<div class="schedule-item">6:30 PM - Introduction</div>
<div class="schedule-item">7:00 PM - Dinner</div>
</div>
<div class="day">Saturday, May 3rd
<div class="schedule-item">12:00 PM - Midnight Sushi</div>
<div class="schedule-item">3:00 AM - 3 AM Snack</div>
<div class="schedule-item">7:00 AM - Breakfast</div>
<div class="schedule-item">11:00 AM - Lunch</div>
<div class="schedule-item">12:00 PM - Presentations</div>
<div class="schedule-item">2:00 PM - Judging</div>
<div class="schedule-item">3:00 PM - Prizes/Closing</div>
</div>
</div>
</div>
</div>
<div class="clear"></div>
<div id="rules1">
<div class="headers">
Registration:
<div class="text">
Registration for the Hackathon is day-of.
</div>
</div>
<div class="headers">
Submission Requirements:
<div class="text">
Set up a GitHub repository for your team.
You will use this repo to submit your project.
Though your repo may be private during development, it must be
public after submission and accessible to the judges.
</div>
<div class="text">
GitHub has excellent tutorials on how to use git and how to set up a
repository on GitHub.
This type of technology can be life-saving for group projects.
For those who know svn, you can use svn with GitHub via git+svn.
</div>
<div class="space"></div>
<div class="linkbutton">
<a href="http://help.github.com/">GitHub Help</a>
</div>
</div>
<div class="headers">
Judging Criteria:
<div class="text">
Completion will be a factor in judging, but incomplete submissions will
not be disqualified.
Bugs are okay! You are building a quick hack, not production-quality
software!
</div>
<div class="text">
If you make any special claims about the capabilities of your software,
please present proof of your claims in your presentation.
The presentation itself doesn't need to be super high quality, but
don't forget to substantiate claims.
The description is not graded, but it will be used to help the judges
refer to teams' projects while judging.
</div>
</div>
<div class="headers">
Prize Pool:
<div class="prize-item">Two 27" Monitors</div>
<div class="prize-item">Four Mechanical Keyboards</div>
<div class="prize-item">Four External Hard Drives</div>
</div>
</div>
<div id="rules2">
<div class="headers">
Prize Rules:
<div class="text">
You can code alone or in pairs or in a group of five, but we will only
but giving one prize to a lone star, two prizes to a pair, and up to 4
prizes for a team of 4+ people. You'll have to distribute the prizes amongst
your group.
</div>
<div class="text">
To be eligible for prizes, you team must consist entirely of CAL
undergraduates, with teams of 4 or lower receiving preference.
</div>
<div class="text">
There are three large prize groups. 1st place winners get first pick at
the prize groups, then 2nd place group gets second pick, and 3rd place
gets the final pick. This means that the 1st place winner may choose
the 2nd place price if they so desire.
</div>
</div>
<div class="headers">
Pre-Hackathon Rules:
<div class="text">
All code written must be written in the 18-hour period, or explicitly
flagged as written beforehand. Making significant use of pre-written
non-framework/non-library code is strongly discouraged.
</div>
<div class="text">
Libraries are fine, and anything reasonably called a "framework" should
also be fine.
Improvements to a library may not be considered in the main body of
a work if they are merely incidental to the project, rather than a major
component.
Non-coding design pre-work and product development is acceptable.
Fleshing out and preparation work, in general, should be no big deal.
</div>
<div class="text">
If a project does not pass a "smell test," judges may, at their
discretion, take this into consideration when evaluating the project.
It is recommended that a README file be included which summarizes the work
done and explains the necessary disclaimers for pre-work, libraries, etc.
However, this is neither required nor scored.
</div>
</div>
</div>
<div class="clear"></div>
<div id="submission">
<div class="headers">
Submission:
<div id="submitbox">
<div id="submittext" class="text">
Congrats on finishing your hack! You can now submit your GitHub repo
here! The judges look forward to reviewing your work!
</div>
<div id="submitbutton" class="linkbutton">
<a href="https://docs.google.com/forms/d/1qZZKxXE8UNoUj6KO8-5yvOydqKjX-ZLMUZxh7NGgVFA/viewform">Submit Your Hack!</a>
</div>
</div>
</div>
</div>
<div id="copyright">
Copyright © 2014 CSUA
</div>
</body>
</html>