fleet/docs/Contributing
Jahziel Villasana-Espinoza b4092cc625
add note about multiple teams to testing section (#31873)
Added a callout about using multiple teams during testing to the backend
patterns doc.
2025-08-13 12:52:44 -04:00
..
adr ADR-0004: Third-party library vendoring (#31406) 2025-07-31 22:31:16 +02:00
architecture add some g-software docs (#31270) 2025-07-30 10:27:22 -04:00
assets SCIM Entra ID support (#28832) 2025-05-08 13:02:49 -05:00
getting-started Running Fleet locally: Building MDM features (#31829) 2025-08-13 09:27:27 -05:00
guides Update design-qa-considerations.md (#31837) 2025-08-13 09:31:53 -05:00
product-groups Add support for last opened time for DEB and RPM packages (#31638) 2025-08-12 15:46:04 -07:00
reference add note about multiple teams to testing section (#31873) 2025-08-13 12:52:44 -04:00
research Lightweight push notification simulator (SSE-based) (#31310) 2025-07-29 07:29:56 +02:00
responsibilities Organize contributor docs and establish ADR process and template (#29101) 2025-05-17 15:03:52 -05:00
workflows Update release notes template (#31014) 2025-07-23 12:05:10 -06:00
README.md Update contrib docs headers to sentence case (#29276) 2025-05-20 11:26:35 -05:00

Fleet Contributor Documentation

Welcome to the Fleet contributor documentation! This documentation is designed to help you contribute to the Fleet project.

Documentation structure

The documentation is organized into the following sections:

Product groups

Fleet is organized into three main product groups:

  • MDM - Mobile Device Management
  • Orchestration - Device orchestration using osquery
  • Software - Software inventory, vulnerability management, and software installation

Contributing

If you're new to Fleet, we recommend starting with the Getting Started section to set up your development environment.

Once you're set up, you can explore the Guides section to learn how to contribute to specific areas of the project.

Architectural Decision Records (ADRs)

We use Architectural Decision Records to document significant architectural decisions. If you're making a significant architectural change, please create an ADR to document your decision.