**Hackathon Rules:**
1. **Event Duration:**
- The hackathon will commence on December 27th at 12:00 PM and conclude on December 29th at 11:59 PM. All project submissions must be completed within this timeframe.
2. **GitHub Initialization:**
- Participants are required to create their GitHub repositories precisely at 12:00 PM on December 27th. This timestamp will be used to verify project start times.
3. **Project Theme:**
- Projects must revolve around automation or the creation of tools that enhance and simplify aspects of daily life.
4. **Code Generation:**
- While participants can utilize code generators, it is essential that not all aspects of the project are code generated. The judging panel will closely examine the commit history to ensure meaningful and diverse contributions.
6. **Project Originality:**
- Teams are not allowed to reuse entire projects from previous hackathons. However, leveraging code snippets or concepts is acceptable, as long as the majority of the project is newly developed for this hackathon.
7. **Team Composition:**
- Teams must consist of a minimum of 1 participant and a maximum of 4 participants. While individual submissions are allowed, collaboration in teams is encouraged to foster productivity and creativity.
8. **Collaboration Preference:**
- Teamwork is encouraged, as it enhances productivity and creativity. Collaborative efforts often result in more comprehensive projects. Each team member should actively contribute to the project.
9. **Submission Guidelines:**
- Submissions must include a link to the GitHub repository and a brief README.md file providing an overview of the project, its functionalities, and any necessary setup instructions.
10. **Presentation Requirements:**
- Teams must be prepared to present their projects to the judging panel. Presentations should cover project objectives, features, implementation details, and any challenges faced.
11. **Judging Criteria:**
- Projects will be evaluated based on creativity, functionality, usability, code quality, innovation, and adherence to the theme. The commit history and individual contributions will play a crucial role in the judging process.
12. **Code of Conduct:**
- Participants are expected to adhere to a code of conduct promoting a positive and inclusive environment. Any form of cheating, plagiarism, or disrespectful behavior will result in disqualification.
13. **Have Fun:**
- While the hackathon is a competitive event, participants are encouraged to have fun, learn new skills, and collaborate with fellow hackers.
