Core-setup uses the [CoreFx policies](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/issue-guide.md), so use that for general information on how to create an issue, etc.
### Areas
Areas are tracked by labels area-* (e.g. area-Host).
| [area-Host](https://github.com/dotnet/core-setup/labels/area-Host) | [@vitek-karas](https://github.com/vitek-karas), [@swaroop-sridhar](https://github.com/swaroop-sridhar) | Issues with dotnet.exe including bootstrapping, framework detection, hostfxr.dll and hostpolicy.dll |
| [area-Infrastructure](https://github.com/dotnet/core-setup/labels/area-Infrastructure) | [@wtgodbe](https://github.com/wtgodbe), [@dagood](https://github.com/dagood) | Build and Publish |
| [area-SDK](https://github.com/dotnet/core-setup/labels/area-SDK) | **[@livarcocc](https://github.com/livarcocc)**, [@nguerrera](https://github.com/nguerrera), [@leecow](https://github.com/leecow) | General development issues and overlap with the SDK and CLI |
| [area-Setup](https://github.com/dotnet/core-setup/labels/area-Setup) | [@dagood](https://github.com/dagood) | Distro-specific (Linux, Mac and Windows) setup packages and msi files |
| [area-UWP](https://github.com/dotnet/core-setup/labels/area-UWP) | [@nattress](https://github.com/nattress) | UWP-specific issues including Microsoft.NETCore.UniversalWindowsPlatform and Microsoft.Net.UWPCoreRuntimeSdk |
Areas are tracked by labels area-* (e.g. area-Host). To view owners for each area in this repository check out the [area-owners.md](https://github.com/dotnet/runtime/blob/master/docs/area-owners.md) page.
@@ -38,77 +38,7 @@ We use [milestones](https://github.com/dotnet/corefx/milestones) to prioritize w
We assign each issue to assignee, when the assignee is ready to pick up the work and start working on it. If the issue is not assigned to anyone and you want to pick it up, please say so - we will assign the issue to you. If the issue is already assigned to someone, please coordinate with the assignee before you start working on it.
### Areas
Areas are tracked by labels area-* (e.g. area-System.Collections). Each area typically corresponds to one or more contract assemblies.
| [area-Infrastructure](https://github.com/dotnet/corefx/labels/area-Infrastructure) | [@ViktorHofer](https://github.com/ViktorHofer), [@ericstj](https://github.com/ericstj), [@wtgodbe](https://github.com/wtgodbe), [@safern](https://github.com/safern), [@Anipik](https://github.com/Anipik) | Covers:<ul><li>Packaging</li><li>Build and test infra for CoreFX repo</li><li>VS integration</li></ul><br/> |
| [area-Meta](https://github.com/dotnet/corefx/labels/area-Meta) | [@joperezr](https://github.com/joperezr) | Issues without clear association to any specific API/contract, e.g. <ul><li>new contract proposals</li><li>cross-cutting code/test pattern changes (e.g. FxCop failures)</li><li>project-wide docs</li></ul><br/> |
Areas are tracked by labels area-* (e.g. area-System.Collections). Each area typically corresponds to one or more contract assemblies. To view owners for each area in this repository check out the [area-owners.md](https://github.com/dotnet/runtime/blob/master/docs/area-owners.md) page.
Note: Area triage will apply the new scheme (issue types and assignee) throughout 2016.
