Establish Design Process for WPF APIs and XAML

[richlander]

Establish Design Process for WPF APIs and XAML

WPF exposes a rich set of APIs and also the Xaml syntax. We need to establish an open design process, both for additions in general and to accept and shape community contributions. This is very similar to dotnet/apireviews and dotnet/csharplang. Those teams have established effective design processes that we can adopt for WPF. For APIs, we should just use the existing .NET API review process. For XAML, we'll need do something different. We need the WPF team to define these processes.

For folks filing issues that propose new API or Xaml syntax, please reference this issue as a way of upvoting its importance.

[dotMorten]

I love this idea, but could I suggest this would be done in collaboration with the UWP and Xamarin.Forms teams, so that we can avoid more divergence? That's not to say there can't be made platform-specific design choices, but decisions that could be made to be across the board should be agreed upon across, and would be helpful for those of us working on all the technologies.

[stevenbrix]

I love it @dotMorten!! That is exactly what we need to do.