Adding new document for contribution handling

CONTRIBUTING.md

@@ -1,18 +1,14 @@
 # Contributing to the Windows UI Library
 
-We welcome your input and contributions to all aspects of WinUI, including bug reports, doc updates, feature proposals, code contributions and API spec discussions.
+We welcome your input and contributions to all aspects of WinUI, including bug reports, doc updates, feature proposals, and API spec discussions.
 
 This document contains general guidance. More specific guidance is included in the documents linked below.
 
 Note that all community interactions must abide by the [Code of Conduct](CODE_OF_CONDUCT.md).
 
-## Issues
+## How we work with contributions
 
-We use GitHub issues to track bugs and features.
-
-For reporting security issues please see the [Security Policy](docs/SECURITY.md).
-
-For all other bugs and general issues please [file a new issue](https://github.com/Microsoft/microsoft-ui-xaml/issues/new/choose) using the Bug Report template.
+Contributions from the community in the form of feature requests and bugs are handled according to our [contribution handling](docs/contribution_handling.md) guidelines.
 
 ## New contributors
 

README.md

@@ -59,9 +59,11 @@ To view the WinUI controls in an interactive format, check out the Xaml Controls
 [WinUI](https://microsoft.github.io/microsoft-ui-xaml/) also has its own website where you can learn more about it.
 
 ## Contributing to WinUI
-The WinUI team welcomes feedback and contributions!
+The WinUI team welcomes your feedback!
 
-For information on how to contribute please see [Contributing to the Windows UI Library](CONTRIBUTING.md).
+To understand how we handle incoming feature requests and bugs, please see our [contribution handling](docs/contribution_handling.md) guidelines.
+
+For information on how to contribute, please see [Contributing to the Windows UI Library](CONTRIBUTING.md).
 
 For guidelines on making an impact on WinUI through non-code contributions, please see [Contributing ideas, feedback, and requests](CONTRIBUTING_feedback_and_requests.md).
 

docs/contribution_handling.md

@@ -0,0 +1,55 @@
+# WinUI Repo Contribution Handling
+
+The WinUI repo is intended as a place for the WinUI team to gather community feedback, discuss issues with the community, and provide insight into bug fixes that the team is working on before updates are released. Here, we'll outline how we handle feature requests and bugs that the community opens.
+
+## Issues
+
+Feature requests and bugs are tracked as GitHub issues.
+
+For reporting security issues please see the [Security Policy](SECURITY.md).
+
+For all other bugs and general issues please [file a new issue](https://github.com/Microsoft/microsoft-ui-xaml/issues/new/choose) using the Bug Report template.
+
+Please file questions and discussions as discussions, not issues.
+
+## Feature Proposals
+
+Feature proposals for WinUI 3 are categorized based on the likely timeframe in which the feature team can consider them.
+
+1. 	Short-term, less than a year
+2.	Long-term, not likely in the next year
+
+All feature proposals are automatically categorized as long-term and unlikely to be considered, although the WinUI team might change the priority based on customer and business needs. If the WinUI team does close a feature proposal, we will indicate the reason why and how it fits into our plans. Closing a proposal does not mean that the team will never consider it. We encourage the community to add comments or interact with a proposal at any time, even a closed one, to signal its importance to the team.
+
+### Feature Planning
+
+Our long term vision for WinUI is to be the best UX/UI native framework for Windows PCs that provides premium visuals, motion, accessibility, usability, and support for all input modalities.
+
+The current details of what we plan long-term are shaped by evolving priorities that are subject to frequent change and are often confidential based on business and customer needs. However, we are happy to share our immediate plans for what's coming next in the next major release once the feature list is ready. Additionally, preview and experimental releases provide opportunities for the community to see what's new and what's changing on a more frequent basis.
+
+For more info about our longer-term planning, see the [Windows App SDK feature roadmap](https://github.com/microsoft/WindowsAppSDK/blob/main/docs/roadmap.md). This page will be updated generally right after a major release, when the features for the next release are solidified enough to share.
+
+## Bugs
+
+### WinUI 2
+
+The WinUI team is currently spending its time on WinUI 3. To help with this focus, new bugs filed against WinUI 2 are closed in this repo unless they're a security issue or are business critical.
+
+### WinUI 3
+
+WinUI 3 bugs are triaged and prioritized based on how much the bug impacts one or more of the following criteria. If a bug has lower impact, it is less likely to be considered for fixing.
+
+- Reliability
+- Data corruption or loss
+- Functionality (such as a major regression)
+- Security
+- Compatibility with applications
+- User experience/usability
+- Performance
+- Compliance (such as legal compliance)
+- Accessibility
+- Build and deployment
+
+Bugs filed in relation to preview and experimental releases are triaged with the same criteria as stable releases and are intended to assist in identifying and fixing those bugs before they make their way to a stable release.
+
+Bugs filed on GitHub will be automatically mirrored to our internal bug tracking system and updates to them are automatically mirrored back to GitHub with appropriate tags. This way, the bugs we're working on and their progress are transparent. The only information we will reflect from our system externally is the state and release of the bug, not all the fine details; if a bug is resolved or closed, that's reflected on GitHub, and as bugs are worked on, the release for that fix will be reflected with a milestone on GitHub.

docs/roadmap.md

@@ -52,48 +52,9 @@ We also ship experimental features as we develop them. You can read more about t
 
 [Experimental release channel for the Windows App SDK](https://docs.microsoft.com/windows/apps/windows-app-sdk/experimental-channel).
 
-### Features by release
-Legend:
-
-🟢 - Available as supported feature
-
-🔷 - Available as experimental feature  
-
-Blank -  Not available
-
-**WinUI 3 - Windows App SDK 1.3** is our latest release.
-
-| Customer Capability | Project Reunion 0.5 <br/>(March 2021) | Windows App SDK 0.8 <br/>(June 2021) | Windows App SDK 1.0 <br/> (November 2021) | Windows App SDK 1.1 <br/> (June 2022) | Windows App SDK 1.2 <br/> (November 2022) | Windows App SDK 1.3 <br/> (April 2023)
-| ------------------- | --------------------------------                | ------------------------------- | ----------------------------- | -----| ----- | ----- |
-| Supported in any app using the Windows App SDK                        | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Contains new Windows 11 controls/styles from WinUI 2.6                |                    |                    | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Supports MSIX Deployment                                              | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Supports Unpackaged (non-MSIX) Deployment                             |                    |                    | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Works downlevel to Windows 10 version 1809 and above                  | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Supports the latest .NET                                              | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| ARM64 support                                                         | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| `<SwapChainPanel> `                                                   | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Intellisense, Hot Reload, Live Visual Tree                            | &#128311;          | &#128311;          | &#128994;[^1]  | &#128994;[^1] | &#128994;[^1] | &#128994;[^1]
-| Chromium-based WebView2                                               | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Title bar customization                                               | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Fluent Shadows                                                        | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Input validation for data fields                                      | &#128311;          | &#128311;          | &#128311;      | &#128311;     | &#128311; | &#128311;
-| Supports multiple top-level windows on the same thread                | &#128311;          | &#128311;          | &#128994;[^2]  | &#128994;     | &#128994; | &#128994;
-| Supports multiple top-level windows on separate threads               | &#128311;          | &#128311;          | &#128311;      | &#128311;     | &#128311; | &#128311;
-| Drag and drop                                                         | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| RenderTargetBitmap                                                    | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Mouse cursor customization                                            | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| Animated Gif support                                                  | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| VirtualSurfaceImageSource (VSIS) support                              | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| In-app acrylic                                                        | &#128994;          | &#128994;          | &#128994;      | &#128994;     | &#128994; | &#128994;
-| XAML Islands                                                          |                    | &#128311;          | &#128311;      | &#128311;     | &#128311; | &#128311;
-| Mica                                                                  |                    |                    |                | &#128994;     | &#128994; | &#128994;
-| Widgets                                                               |                    |                    |                |               | &#128994; | &#128994;
-| Media playback controls                                               |                    |                    |                |               | &#128994;  | &#128994;
-| InfoBadge and other updates from WinUI 2.8                            |                    |                    |                |               | &#128994; | &#128994;
-
-[^1]: Supported on Visual Studio 2022 Preview 5 and above for packaged apps only 
-[^2]: Supported in 1.0.1 and above
+### Roadmap
+
+For more info about upcoming features in the next release of WinUI 3, see the [Windows App SDK feature roadmap](https://github.com/microsoft/WindowsAppSDK/blob/main/docs/roadmap.md).
 
 ## WinUI 2 Controls Library
 

docs/triage.md

@@ -5,6 +5,8 @@
 The WinUI team manages issues and PRs in the repo using a process we call "triage". It helps us keep issues
 organized and focuses the attention of the different groups that work in our project.
 
+For more info about our strategy for triaging bugs, see how we [handle contributions](contribution_handling.md).
+
 ### Triage labels
 
 1. New and re-opened issues are marked with `needs-triage`.
@@ -34,8 +36,7 @@ The temporary `needs-assignee-attention` label is intended for issues which need
 
 ### Backlog
 
-[Assigned issues](https://github.com/microsoft/microsoft-ui-xaml/issues/assigned/*) are being investigated or worked on. This doesn't mean they *will* be fixed soon, just that they are on the
-short list for that person to investigate, and possibly fix. They may get unassigned.
+[Assigned issues](https://github.com/microsoft/microsoft-ui-xaml/issues/assigned/*) are being investigated or worked on. This doesn't mean they *will* be fixed soon, just that they are on the short list for that person to investigate, and possibly fix. They may get unassigned.
 
 [Unassigned issues](https://github.com/microsoft/microsoft-ui-xaml/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+no%3Aassignee) are the backlog.