2
2
3
3
| Version | Status | Last Updated |
4
4
| ---------- | ---------- | ---------------------- |
5
- | 2017-rc.02 | ACTIVE | 9 April 2017 |
5
+ | 2017-rc.03 | ACTIVE | 6 May 2017 |
6
6
7
7
### Introduction
8
8
9
9
All UNIHACK competitors must follow the following rules when participating in
10
- any UNIHACK event.
10
+ any UNIHACK event. Unless specified for a particular location, all rules apply to
11
+ both Melbourne and Sydney.
11
12
12
13
Not all UNIHACK Mini events will use these rules as organisers can choose to use
13
14
these or make their own rules. UNIHACK Mini organisers making alterations to these
@@ -18,16 +19,18 @@ rules, please submit an issue here.
18
19
19
20
### Section 1: Eligibility
20
21
21
- 1 . Teams can have up to six people; but must have a minimum number of four people.
22
- Teams with two or three will be asked to merge. The Organisers can relax this
23
- restriction at their discretion.
22
+ 1 . Teams can have up to six people.
24
23
25
24
2 . Each member of a team must be a student studying at an undergraduate, honours,
26
25
or postgraduate course at an accredited university or TAFE college in Australia
27
26
or New Zealand.
28
27
29
28
3 . Teams cannot have remote participants.
30
29
30
+ 4 . Melbourne only: teams must have a minimum number of four people. Teams with two
31
+ or three people will be asked to merge. The Organisers reserve the right to
32
+ relax this restriction at their discretion.
33
+
31
34
### Section 2: Projects
32
35
33
36
1 . Teams have 24 hours to build a prototype. There are no restrictions on what
0 commit comments