Hack 2 Ignite

1. Problem Statement Release

The official problem statements will be released on the Hack 2 Ignite website and sent to registered teams via email.
The online round will officially begin at 9:00 AM sharp on 16 September.
The 48-hour development period will begin immediately at 9:00 AM on 16 September.

Teams must develop their solution within the official 48-hour online development window.
The development window will end at 9:00 AM on 18 September.
All major development work on the submitted prototype must be completed within this 48-hour period.
Teams are responsible for managing their time and ensuring that their solution is submitted before the deadline.

Teams must use GitHub for development and maintain a clear commit history throughout the hackathon.
GitHub repositories and commit history may be reviewed by the organizers or judging panel to verify that the project was developed within the allotted time.
Projects or significant portions of projects developed before the official start of the hackathon may be disqualified.
Exceeding the allotted 48-hour development period for substantial development work may result in disqualification.
Teams should ensure that their GitHub repository accurately reflects their development process during the hackathon.

Every team must submit its completed prototype within the specified submission deadline.
Each team must submit a presentation (PPT) explaining their solution, approach, implementation, and key features.
A demo video is optional but strongly recommended.
Teams must ensure that all submitted links, files, repositories, and supporting materials are accessible to the organizers.
Incomplete or late submissions may be considered ineligible for evaluation.

All submitted work must be the original work of the participating team.
Plagiarism, direct copying, or submission of another person's or team's work is strictly prohibited.
Teams may use publicly available libraries, APIs, frameworks, and development tools, provided their actual solution and implementation comply with the hackathon rules.
Any attempt to misrepresent previously developed work as work completed during the hackathon may result in disqualification.

The top 30 teams from the online round will qualify for the on-campus offline round.
Selected teams must report to the campus at the time and location communicated by the organizers.
Teams qualifying for the offline round must be physically present on campus as instructed.
A Rs.500 per-team participation fee will be applicable to teams shortlisted for the offline round.

Shortlisted teams must continue working on their existing prototype during the offline round.
Teams will receive a new feature, requirement, or challenge that must be integrated into their existing prototype.
Integration of the assigned new feature is mandatory.
Teams must complete the assigned enhancement within the time limit specified by the organizers.
The updated prototype should demonstrate meaningful improvement over the version submitted during the online round.

After the offline development session, teams must present their updated solution to the judging panel.
The pitch must explain the problem, proposed solution, implementation, key features, and improvements made during the offline round.
Teams should be prepared to demonstrate their working prototype to the judges.
The judging panel may ask questions regarding the technical implementation, decisions, impact, and future scope of the solution.
Teams must follow the presentation time limits and instructions provided by the organizers.

Each team must consist of 2-4 members.
Each participant may be a member of only one team.
Inter-college and inter-specialization teams are permitted.
Teams must ensure that all registered members actively participate in the hackathon.

Teams must follow the problem statement, submission requirements, deadlines, and instructions provided by the organizers.
Any attempt to manipulate GitHub history, submission timestamps, or other verification mechanisms may result in disqualification.
Violation of hackathon rules may result in immediate disqualification.
The organizers reserve the right to verify submissions and request additional information regarding a team's development process.
The decision of the judging panel and organizers regarding eligibility, rule violations, and final results will be final and binding.