> ## Documentation Index > Fetch the complete documentation index at: https://docs.internal.nscale.com/llms.txt > Use this file to discover all available pages before exploring further. # Onboarding > Fleet Manager onboarding checklist, ownership map, and links to core systems. Use this page as the team-level onboarding index for engineers joining Fleet Manager development and operations. Before anything else, read **[Ways of Working](./ways-of-working)** — it covers the operating context, what's expected of you on this team, and the four execution mechanisms we use day to day. That's the bar. Come back to it whenever you're weighing a tradeoff or unsure how to approach a problem. Then read **[Operating Rhythm](./operating-rhythm)** — how that bar shows up in the week: planning, standups, reviews, retros, and the Friday update. ## Onboarding Checklist 1. Read **[Ways of Working](./ways-of-working)** — operating context, expectations, and the four execution mechanisms. This is the bar we work to. 2. Read **[Operating Rhythm](./operating-rhythm)** — how that bar shows up in the week: planning, standups, reviews, retros, and the Friday update. 3. Read [Start Here Overview](../start-here/overview) and complete access prerequisites in [Getting Access](../start-here/getting-access). 4. Skim the [Glossary](../start-here/glossary) — it defines the hardware, OpenStack, scheduling, and validation vocabulary the rest of these docs assume. 5. Complete local setup from [Developer Guide Overview](./overview) and repository-specific setup in [docs/development-setup.md](https://github.com/nscaledev/fleet-manager/blob/main/docs/development-setup.md). 6. Read the [Architecture](./architecture) doc — it covers the hub/satellite topology, why [Temporal](../start-here/glossary#temporal) is used for workflows, the agent pattern, and the external systems Fleet Manager integrates with. This is the recommended mental model to build before reading code. 7. Confirm you can run: * `make dev` * `uv run fleetctl --help` * `make test` 8. Join Fleet Manager communication channels and project tracking tooling (see [Communication Channels](#communication-channels) below). 9. *Optional* Use [deep-dive](https://github.com/nscaledev/fleet-manager/tree/main/.context/deep-dive) skill to understand the codebase quickly. ## Repository Access Most Fleet Manager work spans more than just the main repo. Request access to the following GitHub repos as part of onboarding: * [nscaledev/fleet-manager](https://github.com/nscaledev/fleet-manager) — main API, agents, workflows, and published docs source. * [nscaledev/k8s-deploy-fleet-manager](https://github.com/nscaledev/k8s-deploy-fleet-manager) — dev image-tag rollout path. * [nscaledev/k8s-cluster-fleet-manager](https://github.com/nscaledev/k8s-cluster-fleet-manager) — cluster/environment configuration; required for the prod release flow. * [nscaledev/nscale-ui](https://github.com/nscaledev/nscale-ui) — UI consumer with the generated Fleet Manager TypeScript client. For access to `k8s-cluster-fleet-manager` and `k8s-deploy-fleet-manager`, ask Tom Matthews or Oscar Savolainen. ## Communication Channels | Channel | Purpose | | - | - | | **squad-fleet-manager** | Primary working channel for the team. Used for day-to-day discussion, decisions, and design conversations. Keep things public here where relevant to the wider team — prefer this channel over DMs. | | **fleet-manager-chat** | Broader channel including stakeholders and a wider audience. Used for publishing updates, announcements, and anything the wider group needs visibility on. | ## Stakeholders and Points of Contact Keep this table up to date as ownership changes. | Name | Role | | - | - | | Steven Relf | VP of Infrastructure Engineering (platform user and contributor) | | Josh Goldenhar | VP of Operational Engineering (US) | | John Garbutt | Infrastructure Engineer (Openstack) | | Tom Clark | Infrastructure Engineer (Openstack) | | Omer Khalid | Product lead | | Tom Matthews | Fleet Manager Tech Lead | | Oscar Savolainen | Engineer | | Matt Pryor | Fleet Manager & Cloud Native Architect | | Abigail Mackenzie-Armes | Engineer (FE) | | Graeme George | Engineer (FE) | | Nilabhra Chowdhury | Engineer | | Vinícius do Carmo | Engineer (Topology) | | Cameron Flanagan | Product Engineer | | Vasco Pereira | Product Engineer | | Liam Leighton | UX and Design | | Graeme Moss | Operational engineer (platform user / occasional contributor) | | Grant Delaney | Operational engineer (platform user / occasional contributor) | | Patrick Mcdaniel | US SRE Stakeholder | | Jeremy Thomas | US SRE Stakeholder | | Paul Pham | US SRE Stakeholder | | Matt Walsh | Observability Tech Lead | | Antony Cleave | HPC Specialist | | Paddy O'Neill | HPC Specialist | ## Linear: Board, Projects, and Labeling * Team board (Fleet Manager Squad): [https://linear.app/nscale-workspace/team/FLEET](https://linear.app/nscale-workspace/team/FLEET) * Main Fleet Manager + UI board: [https://linear.app/nscale-workspace/view/fleet-manager-and-ui-issues-2b8e8e76d621](https://linear.app/nscale-workspace/view/fleet-manager-and-ui-issues-2b8e8e76d621) * All Fleet Manager projects: [https://linear.app/nscale-workspace/team/FLEET/projects/all](https://linear.app/nscale-workspace/team/FLEET/projects/all) ### Tickets and Branch Naming When you create a ticket in Linear, use the **Copy git branch name** button on the issue (it produces something like `oscarsavolainen/fleet-714`) and use that as your git branch. Linear will then auto-link the ticket to your branch and move it through the workflow stages based on PR state (open PR moves it to In Review, merged moves it to Done). ### Issue Labeling Labels are used for issue type and scope metadata. For the current canonical label list, see Linear team labels: [https://linear.app/nscale-workspace/team/FLEET/settings/labels](https://linear.app/nscale-workspace/team/FLEET/settings/labels) ## Release and Deploy For deploying a branch to the shared dev environment, see [Testing in Dev](./testing-in-dev). For the full release flow — Release Please PRs, dev rollout, prod rollout, and [ArgoCD](../start-here/glossary#argo-cd) sync — see [Releasing to Production](./releasing-to-production). Branch names must contain the Linear ticket ID somewhere (for example `fleet-916`); anything before or after is fine. ## More information * \#squad-fleet-manager channel has a lot of onboarding information inside bookmarks `new-starter-onboarding` * [Technical Team Onboarding](https://app.notion.com/p/nscalecloud/Technical-Team-Onboarding-3b7577d8b80142f49137e85450274295?source=copy_link) For general company-wide technical onboarding doc This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.