All that you need to know about Eclipse 7.0

ECLIPSE 7.0 is the flagship event of the ACM Student Chapter, TIET, and a premier 24-hour hackathon that draws participation from across the nation. As the chapter’s most distinguished and celebrated initiative, it serves as a dynamic platform for developers, designers, and innovators to collaborate and compete.
With expert-led workshops, dedicated mentorship, and an intense build environment, ECLIPSE 7.0 is designed to cultivate innovation, enhance technical excellence, and transform ambitious ideas into impactful, real-world solutions.

Eligibility:

• The hackathon is open to students from all Colleges and Universities.

• Students from all academic years are eligible to participate. Teams may include members from different colleges.

• Participants from diverse specializations are welcome to form teams together.

Team Format:

Teams must consist of 2–5 members.
Participants are advised to form teams with complementary expertise, including design, frontend development, backend development, and database management.

Problem Statements:

Each team must choose only ONE problem statement.
The detailed problem statements will be published in the PDF below and simultaneously made accessible on the ECLIPSE 7.0 website and ACM’s official social media platforms.

Rounds & Duration:

Round 1: Pre-Screening Round (Online): Teams will be shortlisted based on their idea presentation.

Round 2: Offline Hackathon Round: Shortlisted teams will participate in the on-site hackathon.

During the offline round, teams will be assessed at regular checkpoints to ensure consistent progress.
All rounds must be completed within the officially communicated timelines.

Attendance:

Physical attendance at the venue is mandatory for all qualifying participants.

Required submissions for the offline round include:

A code repository link and/or deployed project link and a project proposal document

Rules:

• Teams must register exclusively through Devfolio and provide accurate team and member details.

• Teams will be evaluated only on the problem statement they have selected. Working on multiple problem statements is strictly prohibited.

• The prototype must be developed strictly during the offline round. Pre-built solutions will result in disqualification.

• Plagiarism is strictly prohibited and will result in immediate disqualification.

• All submissions must be original.

• All participants are required to join the official event application and community platform. Failure to comply may result in disqualification.

• Participants must strictly follow the Code of Conduct throughout the event.

• Any form of misconduct or rule violation may result in disqualification at the discretion of the organizing committee.

• Projects will be evaluated by a panel of judges. The decision of the judges will be final and binding.