REVA - SPECIAL RULES

Special Rules for the Students of REVA University:

● The participants are requested to follow the COVID protocols.
● Please make sure to fill the Check-In form before beginning with
the Hackathon: https://bit.ly/rh21-checkin
● The participants are required to be present on the campus for the
hackathon.
● The participants have to assemble near the 1st floor, Swami
Vivekananda Block. They will further be guided to an available
classroom or lab(s).
● You need to bring your own laptops and other necessary
hardware components.
● Do bring an extension/jumper box for accessing the charging port.
● Keep the required files, documents, applications, etc downloaded
and ready beforehand, so that you need not rely on WiFi
extensively.
● Any queries, feel free to contact us on discord.
● Participants who prefer working from home, please inform
respective higher-ups. Unless you attend the hackathon offline
initially, Attendance cannot be guaranteed.
(If you really prefer to work from home due to any limitation, please get the
necessary approval beforehand so that it does not affect your Attendance/credit)

Hackathon Spirit
 Hackathon, a tech-fest wherein individuals compete to showcase
their skills, while many join just for the thrill of it. The participants
uphold the spirit of hackathon through teamwork,
competitiveness, synergy, and an unmatched joy of learning.

The rules of the Hackathon:

● On 10th November:
The Hackathon will begin at 12:00 a.m. On the same day at 9 a.m.,
the inauguration will be streamed live. You can join the same with
the following link: https://bit.ly/3F40A81

● On 11th November:
The In-hackathon judging session will take place on the evening of
11th November for some of the teams. You have to showcase your
progress in the project. You can either show your working code or
give a presentation for about 3 minutes. A working model, if
hardware-based, can also be demonstrated.

● On 12th November:
The rest of the teams will have the In-hackathon judging session
taking place in the first half of 12th November. The participants will
have to showcase their progress on their project. They can either
show their working code or give a presentation for about 3
minutes. A working model can also be demonstrated.

REVA HACK</> 2021 concludes at 3 p.m. IST, 12 Nov, 21.

The project along with the video and the elevator pitch must be
submitted on the Devfolio portal.
 Need help for making an Elevator Pitch? Watch: https://youtu.be/QGCidXJslIs
Emily Perry from QuillBot conducted a session during REVA HACK </> 2020 for the same.

We understand most of you are beginners. We have attached a template for

Elevator Pitch soon so that you know what should be present in it and can
use the same to make yours too.

https://bit.ly/rh21-epdoc

● You must treat all team members, competitors, judges, mentors,

and organizers, with respect and courtesy, abiding by the Code of
Conduct.

● It is essential to have a GitHub repository. Please make sure that

you create a repository with your team members, and regularly have
your code updated on the same.

● Since this is an online hackathon, one easy way for us to determine

if your team has been working hard is by checking the Github
repo. All the teams are required to make a GitHub repository
for this Hackathon once the Hackathon begins and add
reva-hack a contributor for the same. Doing the same will
allow us to view your commit interval & team’s contribution and
increase your chance of winning the Hackathon.
GitHub details (to add as a contributor):
Username: revahack
E-mail ID: revahack@gmail.com

● Hackathon teams will be a maximum of 4 people. ●

All team members should be present at the event. ●
All team members must contribute.
● Teams can seek advice and support from organizers and mentors.
In case of technical issues, you can take help from the organizing
team. For the same, you should join our discord server. If you still
haven’t, please use the following link to do so
 https://discord.gg/PXgP3WPaQY
● All project work should be started and completed only during the
hackathon.
● Teams may use libraries, frameworks, or open-source code in their
projects. However, PLAGIARISM WILL NOT BE TOLERATED.
Working on a project before the event and open-sourcing it for
the sole purpose of using the code during the event is against the
spirit of the rules and is not permitted.
● Teams must stop hacking once the time is up. However, teams are
allowed to debug, make minor fixes and add new commits on
GitHub to their programs after time is up. e.g. If during
debugging on your hack you find a bug that breaks your
application and the patch is only a few lines of code, it’s okay to fix
that. It is not permitted to make significant changes or introduce
new features.
● Teams can be excluded from the competition at the discretion of
the organizers. Reasons which involve, but are not limited to, a
violation of the rules of the hackathon by acting in a manner that
breaches the Code of Conduct or other unsporting behavior.
● It is recommended that all participants add the REVA HACK GitHub
account to the repository that you are working on as a
collaborator. This is because we will be able to understand that the
participants are working on the day of the hackathon and you
haven’t worked on the project before the hackathon began. The
commitments will be periodically monitored, as it will allow us to
get more clarity about the project on which the participants are
working and also enable us to take it to the next stage.
● Projects submitted under Tezos track need to meet their
mandated criteria in order to qualify for the Track Prize.
SUBMISSIONS:

● On 12th November 3 P.M, participants need to submit their work on

Devfolio

● Additionally, teams can also provide a video along with the

other project documents during submission, for a
competitive edge.
● The video can be a presentation/demonstration of their final code or
project in action. It is recommended to upload the same on
youtube and share the link while submitting the project on Devfolio.
Please make sure that the video does not exceed 3 minutes.
● On the 13th and 14th of November selected participants will have a
live meeting with the panel of Judges, for their final presentation
(Grand Finale).

JUDGING
● Eligible Submissions will be evaluated by a panel of judges selected
by the Administrator. Judges may be employees of the
administrator or external, may or may not be listed individually on
the Hackathon Website, and may change before or during the
Judging Period. Judging may take place in one or more rounds
with one or more panels of Judges, at the discretion of the
Administrator.
● There will be an in-hackathon judging session either on the
evening of 11th November or the morning of 12th November,
depending upon your slot. The participants will have to showcase
their progress on their project. They can either show their working
code or give a presentation for about 3 minutes. A working model
 can also be demonstrated.
● ● Judges may or may not test the application and may prefer to
judge solely based on the project synopsis and video included in
the submission. It completely depends on them.
● The top teams will be invited to the live-streamed Grand Finale.

Remember!

Taking part in the competition is only a small component of the overall

hackathon. Attending an event is a great opportunity to try something new,
teach something new, and meet some new people!

Good Luck to all !!! 😇✨