Overview

AiTWobo is a global robotics club built to connect passionate builders across countries to collaborate on real projects and compete annually. This guide helps you join the right way, understand how chapters work, and start contributing quickly.

How AiTWobo Works

1. Chapters: local communities by country/state/region. Chapters host meetings, workshops, and project teams.
2. Projects: teams build robotics systems (hardware + software) with clear milestones and documentation.
3. Programs: Build & Learn tracks (beginner → advanced) that help members gain skills with structured learning.
4. Annual Competition: teams present solutions to a shared challenge theme, evaluated by judges using official rules.

Membership & Chapters

When you join, you connect to a chapter and choose a role that matches your level:

• Member — learns, participates, builds, documents.
• Mentor — supports teams, reviews work, teaches workshops.
• Researcher — explores advanced topics, writes technical notes, supports innovation.
• Admin/Manager — organizes schedules, approvals, safety, partnerships.

Best practice: pick one chapter as your main home (for meetings) and collaborate globally online when needed.

First Project Checklist

Use this checklist to start strong in your first 7–14 days:

1. Profile ready: fill your name, location, skills, and links (GitHub/LinkedIn/portfolio).
2. Pick a track: beginner (Arduino), intermediate (sensors + control), advanced (ROS2/SLAM/AI).
3. Choose a project: pick one active project or propose a small starter project.
4. Set tools: install basics (Git, VS Code, Arduino IDE / PlatformIO). For advanced: Ubuntu + ROS2.
5. Confirm safety: read lab safety and power-handling basics before wiring motors or batteries.
6. Define a milestone: a tiny deliverable in 7 days (ex: motor driver test + documented results).
7. Document your work: post weekly progress notes (what you did, what failed, what’s next).

Communication & Culture

• Be respectful, practical, and solution-focused.
• Ask clear questions (context + what you tried + error + photos/video if possible).
• Share knowledge openly: if you learn something, document it for others.

Next Steps

After reading this doc, go to Programs & Learning and select your path, then review Safety & Ethics if you will build hardware.