Team size
3-5
Every member must be individually registered.
Rules
Official rules for a fair hackathon.
Participant eligibility, team limits, build integrity, public materials, checkpoint attendance, final submission, responsible AI, and conduct requirements.
Event flow
Use the dashboard for every team milestone
Project scope
1 track
One EdTech track and one project per team.
Final lock
May 24, 14:00
Dashboard submissions lock sharply.
Teams
Participant and team eligibility
- All participants must be registered individually on the GDG portal before the hackathon starts.
- Team registration opens after the event starts at ai.gdgtashkent.uz.
- Only one team lead submits the team registration form, and each team may have only one submitted team registration.
- Teams must have 3-5 participants. One participant can be a member of only one team.
- Organizers, mentors, judges, and official event staff cannot participate as team members.
- Each team must select exactly one track and submit exactly one project.
Project work
Build integrity and allowed resources
- All projects must start at the hackathon. Pre-built solutions are not allowed.
- Projects must address an EdTech use case in Corporate Education, Public and Higher Education, or General Education.
- Open-source libraries, public APIs, SDKs, templates, public datasets, and pre-trained models are allowed if properly disclosed.
- Teams must disclose what was built during the hackathon and what external assets, libraries, APIs, templates, or open-source components were used.
Operations
Dashboard and checkpoints
- After team registration, the team lead must have dashboard access for final submission and status visibility.
- Checkpoints are organizer-led. Teams do not self-submit checkpoints.
- Teams must be available at their working area during each checkpoint window.
- A team must have a majority of registered members physically present during checkpoint verification unless organizers approve an exception.
- Teams must pass Checkpoints 1, 2, and 3 before final submission unlocks.
- Repeated absence, refusal to follow verification, or serious rule issues may affect loyalty points, final judging eligibility, or hackathon eligibility.
14:00 deadline
Final submission
- Final submission requires all 3 organizer checkpoints to be marked passed.
- Final submissions must be completed through the team dashboard by 14:00 sharp on May 24.
- Each team must submit a Google Slides presentation link and a GitHub/GitLab repository link.
- Slides must be Google Slides only and must use the official presentation template.
- The Google Slides link must be view-only and configured as Anyone with the link - Viewer.
- The repository must be public, accessible by link, and include a README with setup/run instructions and enough context for organizers.
- Late submissions are accepted only for platform or organizer-caused issues that are reported before the deadline.
Public access
Public materials, IP, and sponsor review
- By registering and submitting a final project, teams agree that submitted solution materials, repository/code, and slides may remain publicly accessible after the hackathon.
- Organizers and event sponsors may view, reference, demonstrate, share, and use submitted public materials for judging, post-event review, communications, educational/event recap purposes, and hackathon-related sponsor follow-up.
- Teams must not include confidential company information, private datasets, personal data, secrets, API keys, or unauthorized materials in repositories or slides.
- Organizers may request that final submission links remain accessible after the event for transparent review.
Safety
Responsible AI and conduct
- AI must support the core value of the EdTech solution, not appear only as a superficial chatbot layer.
- Teams must not upload sensitive, private, or unauthorized personal data to AI tools or third-party APIs.
- Teams should avoid unsupported claims about learning outcomes, grading accuracy, medical or psychological assessment, or child safety.
- Teams must be able to explain what the AI component does, what tools were used, and what limitations exist.
- All participants must follow venue rules, code of conduct, and organizer instructions.
Disqualification and exceptions
Organizer decisions protect fairness
- Fake registration or duplicate team membership.
- Submitting pre-built solutions as hackathon work.
- Plagiarism, cheating, harassment, unauthorized data use, or major rule violations.
- Broken or inaccessible final submission links, private/restricted repositories, missing Google Slides submission, missing official template, or missing README.
- Removing or restricting public access to final materials after the deadline.
- Repeated checkpoint absence or refusal to follow checkpoint verification.
Deadline exceptions must be caused by platform or organizer issues and recorded by organizers. Unsafe behavior, discrimination, property damage, or refusal to follow organizer instructions may result in removal from the event.