Team A Policies

Team A is the autonomous software team. These policies come from the Team A repository (racerbot_a). Looking for the hardware team? See Tech Team Policies.

Research Documentation

Research notes must be filled with new information and discoveries, especially learnings from the nodes: what was tried, what worked, what failed and why, and how problems can be mitigated. This keeps the team from repeating mistakes and builds a map of what works.

• Every new feature or major change must have a corresponding edit to RESEARCH.md in the Team A repo

Active Contribution

Meaningful work is required to stay on the team. Tasks are assigned through GitHub Issues on the Team A project board, with a deadline agreed on in advance. If a task needs collaboration, start a Discord thread for it.

• Each task requires a genuine pull request and active communication before the deadline
• Extensions are granted for emergencies, or once per term for up to a week. Beyond that, extensions are only granted if you are stuck despite showing clear progress

Enforcement

Members are warned if they are at risk of falling short on these policies. Non-compliance is grounds for removal from the team.