WesHack_24/rules.html at main · DefinetlyNotAI/WesHack_24 · GitHub

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
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
<!DOCTYPE html>
<html lang="en">

<head>
    <!-- Basic Meta -->
    <meta charset="utf-8"/>
    <meta content="IE=edge" http-equiv="X-UA-Compatible"/>
    <!-- Mobile Metas -->
    <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport"/>
    <!-- Site Metas -->
    <link href="Website/images/Favicons/SafeLocked.Document.Favicon.png" rel="icon" type="image/png">
    <link href="Website/css/favicon.css" rel="stylesheet" type="text/css"/>
    <script src="Website/js/favicon+urlpretty.js"></script>
    <meta content="Team for the Wesgreen 2024 Hackathon" name="description"/>
    <meta content="Wesgreen Hackathon, Student-led Hackathon, Coding Competition, Hackathon 2024" name="keywords"/>

    <title>WES:HACK - Rules</title>

    <!-- Bootstrap core CSS -->
    <link href="Website/css/bootstrap.css" rel="stylesheet" type="text/css"/>

    <!-- Fonts style -->
    <link href="https://fonts.googleapis.com/css2?family=Poppins:wght@400;500;600;700&display=swap" rel="stylesheet"/>

    <!-- Font awesome style -->
    <link href="Website/css/font-awesome.min.css" rel="stylesheet"/>

    <!-- Custom styles for this template -->
    <link href="Website/css/style.css" rel="stylesheet"/>
    <!-- Responsive style -->
    <link href="Website/css/responsive.css" rel="stylesheet"/>
    <!-- Colors and more Custom styles -->
    <link href="Website/css/rules.css" rel="stylesheet"/>
</head>

<body class="sub_page">

<div class="hero_area">
    <div class="hero_bg_box">
        <div class="bg_img_box">
            <img alt="Hero background image" src="Website/images/Background.png">
        </div>
    </div>

    <!-- Header Section -->
    <header class="header_section">
        <div class="container-fluid">
            <nav class="navbar navbar-expand-lg custom_nav-container ">
                <a class="navbar-brand" href="index.html">
                    <span>WES:HACK 24</span>
                </a>

                <button aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation"
                        class="navbar-toggler" data-target="#navbarSupportedContent"
                        data-toggle="collapse" type="button">
                    <span class="navbar-toggler-icon"></span>
                </button>

                <div class="collapse navbar-collapse" id="navbarSupportedContent">
                    <ul class="navbar-nav">
                        <!-- Preserved Navbar Items -->
                        <li class="nav-item">
                            <a class="nav-link" href="index.html">Home</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="prizes.html">Prizes</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="venue.html">Venue</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="schedule.html">Schedule</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="sponsors.html">Sponsors</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="faq.html">FAQ</a>
                        </li>
                        <li class="nav-item">
                            <a class="nav-link" href="volunteers.html">Volunteers</a>
                        </li>
                        <li class="nav-item active">
                            <a class="nav-link" href="rules.html">Rules <span class="sr-only">(current)</span></a>
                        </li>
                    </ul>
                </div>
            </nav>
        </div>
    </header>
    <!-- End Header Section -->
</div>

<div class="hackathon-rules">
    <h1>Rules and Code of Conduct</h1>

    <br>
    <p>Remember that hackathons are like marathons.
        Some people go to compete but most people take part to better themselves and have fun.
        Whatever the reason is you're at a hackathon,
        make sure you're upholding the hacker spirit by collaborating with other teams,
        helping beginners, and having fun.</p>
    <br>

    <!-- General Information Section -->
    <h2>1. General Information</h2>
    <div class="content">
        <ul>
            <li>All participants must act respectfully.</li>
            <li>Professional conduct is mandatory; violations result in disqualification or removal.</li>
            <li>Open to all backgrounds and skill levels; exclusionary behaviour results in immediate
                disqualification.
            </li>
            <li>Violations can be reported anonymously; organizers will investigate all reports.</li>
            <li>By participating, you agree to follow the hackathon’s rules and guidelines. Failure to comply may lead
                to disqualification.
            </li>
            <li>Contact the organizers with any questions or concerns.</li>
        </ul>
    </div>

    <!-- Participation Rules Section -->
    <h2>2. Participation Rules</h2>
    <div class="content">
        <h3>a) Team Formation</h3>
        <div class="content show">
            <ul>
                <li>Maximum of 3 members per team.</li>
                <li>All team members must confirm their participation before the start date.</li>
                <li>Ensure all teammates understand rules and expectations.</li>
            </ul>
        </div>
        <h3>b) Attendance</h3>
        <div class="content show">
            <ul>
                <li>All team members must attend both competition days; absence may result in disqualification from
                    prizes.
                </li>
                <li>Leaving the venue for some time to hack elsewhere is fine as long as it is within campus and under
                    supervision - You must gain permission first from Shahm Najeeb.
                </li>
            </ul>
        </div>
        <h3>c) Work Rules</h3>
        <div class="content show">
            <ul>
                <li>Teams can gain advice and support from organizers, volunteers, sponsors, and others.</li>
                <li>Teams can work on ideas that have already been done. Hacks do not have to be “innovative”.</li>
                <li>Teams must stop hacking once the time is up. However, teams are allowed to debug and make small
                    fixes to their programs after time is up.
                </li>
                <li>All code must be written during the hackathon; pre-existing libraries can be used unless
                    prohibited.
                </li>
                <li>Reusing up to 60% of prior work is permitted with clear documentation.</li>
                <li>Required deliverables: Source code with documentation, README file, and presentation slides (if
                    applicable).
                </li>
            </ul>
        </div>
        <h3>d) Conduct</h3>
        <div class="content show">
            <ul>
                <li>Respectful behavior towards all participants.</li>
                <li>No exclusionary behavior.</li>
                <li>Teams can be disqualified from the competition at the organizers’ discretion.</li>
            </ul>
        </div>
    </div>

    <!-- Tools and Technology Section -->
    <h2>3. Tools and Technology</h2>
    <div class="content">
        <ul>
            <li>Any language, framework, or tool is allowed unless prohibited; organizers may restrict certain tools for
                security reasons.
            </li>
            <li>Must declare hardware before the event, Declare first day when signing in with the volunteers. Do download the hardware rules and read them if necessary.</li>
            <li>Internet allowed for research, not external assistance; no communication with people outside the
                competition.
            </li>
            <li>AI may assist but cannot dominate the project; teams must state AI usage in the README.</li>
            <li>
                Block-Based coding or Hybrid-Based coding is not allowed; only pure scripting languages are allowed.
                ( Exception to this rule for Junior Programmers )
            </li>
        </ul>
    </div>

    <!-- Intellectual Property Section -->
    <h2>4. Intellectual Property</h2>
    <div class="content">
        <ul>
            <li>All the Prizes and the Prize categories are decided at the sole discretion of Wes:Hack and can be
                modified at any time under requisite circumstances.
            </li>
            <li>After hacking finishes, teams will show their projects to each other and to the judges.</li>
            <li>You are encouraged to present what you have done even if your hack is broken, or if you weren’t able to
                finish.
            </li>
            <li>Photography is encouraged, Participants must give a reasonable chance to opt out from being
                photographed.
            </li>
        </ul>
    </div>

    <!-- Judging Criterion Section -->
    <h2>5. Judging Criterion</h2>
    <div class="content">
        <h3>a) Innovation</h3>
        <div class="content show">
            <ul>
                <li>Novelty and originality of the idea; differentiation from existing solutions.</li>
                <li>Creativity in problem-solving and approach.</li>
                <li>Uniqueness of the concept compared to other submissions.</li>
            </ul>
        </div>
        <h3>b) Functionality</h3>
        <div class="content show">
            <ul>
                <li>Does the project meet its objectives? Are there bugs or limitations?</li>
                <li>Reliability and stability of the application.</li>
                <li>Completeness of the features and functionalities.</li>
            </ul>
        </div>
        <h3>c) Design</h3>
        <div class="content show">
            <ul>
                <li>User interface design and usability; accessibility for users of all skill levels.</li>
                <li>Aesthetic appeal and visual design.</li>
                <li>Consistency in design elements and user experience.</li>
            </ul>
        </div>
        <h3>d) Impact</h3>
        <div class="content show">
            <ul>
                <li>Addressing real-world problems; potential reach and influence.</li>
                <li>Social, economic, or environmental benefits.</li>
                <li>Potential for scalability and future development.</li>
            </ul>
        </div>
        <h3>e) Technical Merit</h3>
        <div class="content show">
            <ul>
                <li>Quality of the project’s architecture; technical innovation or achievements.</li>
                <li>Efficient use of resources and optimization.</li>
                <li>Complexity and sophistication of the technical implementation.</li>
            </ul>
        </div>
        <h3>f) Documentation</h3>
        <div class="content show">
            <ul>
                <li>Thoroughness of the documentation; ease of understanding for external users.</li>
                <li>Clarity and completeness of the README file.</li>
                <li>Availability of usage instructions and examples.</li>
            </ul>
        </div>
        <h3>g) Additional Criteria</h3>
        <div class="content show">
            <ul>
                <li>Judges may apply extra criteria at their discretion.</li>
                <li>Consideration of teamwork and collaboration.</li>
                <li>Presentation and demonstration quality.</li>
            </ul>
        </div>
    </div>

    <!-- Code of Conduct Section -->
    <h2>6. Code of Conduct</h2>
    <div class="content">
        <ul>
            <li>Respectful behavior towards all participants.</li>
            <li>No exclusionary behavior.</li>
            <li>Violations can be reported anonymously.</li>
            <li>Teams must be present on both competition days.</li>
            <li>All team members must follow the rules.</li>
            <li>Runner-ups may receive recognition in the closing ceremony.</li>
            <li>Winners may be asked to participate in promotional activities, including but not limited to video's and
                afterword.
            </li>
            <li>Only students who are enrolled in school may join, even without being under the name of their school,
                you must be 18 or under – College students are not allowed.
            </li>
        </ul>
    </div>

    <!-- Sanctions Section -->
    <h2>7. Sanctions</h2>
    <div class="content">
        <h3>a) General Information</h3>
        <div class="content show">
            <p>Violations of hackathon rules and guidelines will result in sanctions. The nature of the sanction will
                depend on the severity and frequency of the violation.</p>
        </div>

        <h3>b) Types of Sanctions</h3>
        <div class="content show">
            <ul>
                <li><strong>Warning</strong>:
                    <ul>
                        <li>Issued for minor infractions.</li>
                        <li>Participants will be notified and expected to correct their behavior.</li>
                    </ul>
                </li>
                <li><strong>Disqualification</strong>:
                    <ul>
                        <li>For serious violations or repeated minor infractions.</li>
                        <li>The team will be removed from the competition and ineligible for prizes.</li>
                    </ul>
                </li>
                <li><strong>Removal from Venue</strong>:
                    <ul>
                        <li>For extreme cases of misconduct.</li>
                        <li>Participants will be required to leave the event premises immediately.</li>
                    </ul>
                </li>
            </ul>
        </div>

        <h3>c) Reporting Violations</h3>
        <div class="content show">
            <ul>
                <li>Violations can be reported anonymously.</li>
                <li>The organizing team will investigate all reports and take appropriate action based on the
                    findings.
                </li>
            </ul>
        </div>

        <h3>d) Appeal Process</h3>
        <div class="content show">
            <ul>
                <li>Participants may appeal sanctions at the time of report, Appeal to the Founder ONLY.</li>
                <li>The organizing team will review the appeal and make a final decision within 1 hour.</li>
            </ul>
        </div>

    </div>

    <br>
    <p>Good luck and happy programming!</p>
    <a class="btn btn-primary" download href="Website/downloadable/Hackathon%20Rules.pdf">Download Local Hackathon Rules as a PDF</a>
    <a class="btn btn-primary" download href="Website/downloadable/Hardware%20Rules.pdf">Download Hackathon Hardware Rules as a PDF</a>
</div>

<!-- JavaScript Files -->
<script src="https://code.jquery.com/jquery-3.6.0.min.js"></script>
<!-- Popper.js -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/2.11.6/umd/popper.min.js"></script>
<!-- Bootstrap JavaScript -->
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/js/bootstrap.min.js"></script>
<!-- Custom JavaScript -->
<script src="Website/js/rules.js"></script>

</body>

</html>