If you need to tag folks on an issue or PR, you will generally want to tag the owners (not the lead) for area to which the change or issue is closest to.
| Area | Lead | Owners | Notes |
|---|---|---|---|
| area-acquisition | @joperezr | @aspire/area-acquisition | Issues/PRs related to how Aspire is installed. (Workload or VS Install) |
| area-app-model | @adityamandaleeka | @aspire/area-app-model | Issues/PRs related to the Aspire app model and Aspire AppHost |
| area-app-testing | @ReubenBond | @aspire/area-app-testing | Issues/PRs related to the framework we provide for scenario testing of Aspire apps |
| area-components | @sebastienros | @aspire/area-components | Issues/PRs related to Aspire Components |
| area-dashboard | @kvenkatrajan | @aspire/area-dashboard | Issues/PRs related to the Dashboard UI |
| area-deployment | @davidfowl | @aspire/area-deployment | Issues/PRs related to deploying Aspire apps |
| area-docs | @IEvangelist | @aspire/area-docs | Issues/PRs related to documentation |
| area-engineering-systems | @joperezr | @aspire/area-engineering-systems | Issues/PRs related to how the repository is built and tested (build and test infrastructure) |
| area-meta | @danmoseley | @aspire/area-meta | Issues/PRs that don't really match any of the other areas |
| area-orchestrator | @dbreshears | @aspire/area-orchestrator | Issues/PRs related to DCP (Devex Control Plane) |
| area-samples | @DamianEdwards | @aspire/area-samples | Issues/PRs related to the Aspire samples. These are in the dotnet/aspire-samples repo. |
| area-service-discovery | @ReubenBond | @aspire/area-service-discovery | Issues/PRs related to Aspire's Service Discovery and communication between services |
| area-templates | @DamianEdwards | @aspire/area-templates | Issues/PRs related to the Aspire templates |
| area-telemetry | @samsp-msft | @aspire/area-telemetry | Issues/PRs related to telemetry (logs, metrics, tracing) |
| area-tooling | @vijayrkn | @aspire/area-tooling | Issues/PRs related to Visual Studio and Visual Studio Code tooling for Aspire |
While not necessarily associated with a specific area, these community members have the power to assist with routing and fixing labels of issues and pull requests, and are generally knowledgeable about how the repo works:
- @Kahbazi