Open mletterle opened 7 years ago
Excellent.
@mletterle I fully agree with you, if it is an open standard, it has to happen in this way that you quoted, and I would say more, Microsoft and the team involved, should make a formal invitation to companies that hold much of the market as: Adobe who developed the Adobe XD is a software that should embrace XAML Standard, among others such as Bohemian who developed Sketchapp, among many other companies that develope designer tools and prototyping tools and companies that develop presentation frameworks like Qt Company, Embarcadero, Google, Apple and etc.
It might be worth looking at what .NET Standard does: https://github.com/dotnet/standard/tree/master/docs/review-board
Basically only implementers of the standard are part of the review board, as they are the ones committing to it with a directly vested interest.
We shouldn't confuse "Open Standard" with "Democracy". A standard does need some key stakeholders to keep things consistent, maintainable and extensible. Since the only parties currently needing to implement this is UWP and XF, it makes sense they are the review board - at least until other vendors - like noesis - comes along and want to join the party. Too many players aren't always a good thing. OAuth 2.0 is a good example of what we don't want to happen.
An alternative might be an Advisory Board that works with the Review Board and push community and key industry agendas.
I'd argue that there should be at least someone from .NET Core/.NET Standard team on the board. In the past the .NET team was in full control of the Full Framework, and all the related stacks...and so there was a holistic approach. You then had the reorg where some of the XAML team moved to UWP, some didn't. It's just with the new ideas in .NET Core/.NET Standard...some of those could be injected into the XAML Standard - it's not about them regaining control again.....they've got enough on their plate.
this should get a "meta" tag
The Review Board Document currently states:
If there is truly to be a
XAML Standard
it should include non-Microsoft/Xamarin representatives from the start, even if it just happens to be a "community representative" rather than a vendor of some sort (though I believe there are appropriate vendors already out there, noesisengine comes to the top of my mind, as does Ammy)These third parties should be involved from the start rather than attempted to be bolted on later.
Pull Request #111 might be related to some extent.