Maximally Hack is not just code — it’s a community of builders, designers, and thinkers shaping the future of hackathons. We believe in collaboration, clarity, and creativity. This document defines how we work together, how we support each other, and what it means to be a contributor.
✨ Core Values
- Open Collaboration – No silos. Everyone can ask questions, share ideas, and jump into discussions.
- Clarity Over Cleverness – Write code, docs, and designs that are easy to understand for future contributors.
- Bias for Action – Ship small, test fast, improve continuously.
- Respect & Empathy – Treat contributors, users, and organizers with patience and kindness.
- Learning First – Every task is a chance to grow skills. Mentorship and pairing are encouraged.
đź§© How We Work
- Async First → We default to async updates (issues, PRs, docs) so contributors in all time zones stay in the loop.
- Small Commits, Frequent PRs → Easier to review, test, and merge.
- PR Reviews = Knowledge Sharing → Reviews are not gatekeeping; they’re learning opportunities for both sides.
- Design Docs for Big Features → Before major changes, contributors write a short design doc (1–2 pages).
- Weekly Syncs (Optional) → Each team may host short sync calls, but attendance is not mandatory.
👥 Teams & Crews
Maximally Hack is built by contributors organized into focused crews, each owning part of the platform but working closely with others.
1) 🎨 Frontend Team (Painters)
- Build participant, judge, and organizer interfaces (React + TypeScript).