Issue: New .NET Foundation Project Application - XAML Studio

[michael-hawker]

Project Name

XAML Studio

License

MIT

Contributor

Microsoft, Michael Hawker

Existing OSS Project?

No

Source Code URL

N/A - To be published upon acceptance

Project Homepage URL

https://aka.ms/xamlstudio

Project Transfer Signatories

Microsoft, Michael Hawker - FYI @ChrisSfanos Prior MS Legal Clearance for OSS release

Description

XAML Studio helps to rapidly prototype WinUI XAML that can be easily copied into your app in Visual Studio. XAML Studio lets you preview your XAML code in real-time and interact with the result just like it was running in your own app!

This instant response lets you quickly iterate on ideas visually, copy in examples from docs to explore, and test the final behavior all at the same time in one app that's easy to download and install quickly.

XAML Studio also includes a suite of debugging tools including:

• Providing Data Context to your UI to fill it with static test data or live data from a JSON REST API.
• Binding debugger to not only see how a back-end data source connects to the front-end UI, but spot where errors are occurring and what the most recent values were
• And more

What are you hoping from the foundation

Project started during Garage hackathons towards the original Windows Community Toolkit Sample App (part of the Foundation already), and on my own time; so looking to move forward with it more independently as part of the foundation where it'll be easier to manage and work with other developers in the open.

Name

Michael Hawker

Email

michael.hawker@outlook.com

GitHub Profile URL

https://github.com/michael-hawker

Committers

Michael Hawker, https://github.com/michael-hawker

Discord Ids

xamlllama

Governance Model

Use Discussions for Idea Proposals
Issues to track bugs and new active feature work
Issue and discussion required before PR

CLA

• If already an OSS project, was a Contribution License Agreement in place for contributions accepted?

How does the project check who has signed one?

No response

CLA Notification Alias

No response

Select the Project Transfer Agreement model

Assignment

Repository Layout

No response

Eligibility Criteria

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.
• The project produces source code for distribution to the public at no charge.
• The project's code is easily discoverable and publicly accessible (preferably on GitHub).
• The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
• When applicable, project must use reproducible build settings in its toolchain.
• The project uses Source Link.
• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
• The project code signs their artifacts as appropriate.
• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
• Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
• Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
• The copyright ownership of everything that the project produces is clearly defined and documented.
• The project has a public issue tracker where the status of any defect can be easily obtained.
• The project has a published Security Policy.
• The project has a home page which provides high level information about its status and purpose.
• The project has a public communication channel where community members can engage with maintainers.
• The project has a publicly available location where members can review and contribute to documentation.

Describe why you are applying for Project Membership.

Project has roots in the Windows Community Toolkit (another .NET Foundation project) and aligns with community interests and other .NET Foundation projects. Project will be easier to maintain and manage within the Foundation, in the open on GitHub.

Infrastructure Requirements Summary

No response

Additional Notes

As mentioned above, has already had clearance for OSS release from MS internal MS link here.

Can share that app has had 53k lifetime acquisitions (4k in last year), ~250k store page views in last year, conversions have fallen off, but that's because project has yet to be updated, been waiting for OSS transfer before doing significant work, though code has been moved forward from published version.

[glennawatson]

Thanks @michael-hawker

For the project committee did you want to give a intro next meeting and maybe sit out on the discussions otherwise?

Not sure the process when a project is introduced by a committee member.

[michael-hawker]

Thanks @glennawatson, I may have a conflict at the next meeting, but I think I've got it on the right time on my personal calendar so I'll try to be there. I've provided @ChrisSfanos with a lot of details, as I approached him first being this is coming from Microsoft still technically.

Happy to still give an intro and then just listen or what not, agree it is a bit odd. So let me know what works best. The project has been a bit in limbo as I've been trying to open source it for a while, but until recently wasn't sure how that would work with going to the Foundation, as that does seem like the better home for it.

I do have some minor prototyping and updates I've done to the product compared to what's released, so if approved and we move the code in the open, I do hope to give it a fresh coat of paint and release an update.

[glennawatson]

Yeah I think also I will send out this URL in the committee reminder email so they can get some feedback on they 'why' around this project and the anticipation of it speeding up.

In terms of internal MSFT politics does it require full membership or is seed an option as well? Maybe @ChrisSfanos can give some insights around this also.

[ChrisSfanos]

@glennawatson @michael-hawker Typically we've taken all Microsoft projects as full members. That said, I don't think it's a hard/fast requirement and wouldn't be unreasonable for the Foundation to help grow the project from Seed to full member

[glennawatson]

hi @michael-hawker As you know the project committee met the other week. At this stage its a bit of a split, some of the committee felt admission to full admission given the high impact the project has had on the community, others were just uncertain given it hasn't been opened source before so could be a issue in terms of knowing the true metrics of the project.

I am putting the project forward towards the board, noting the project committee was a bit split, for the board to do a final analysis of the project and determine if we want the project to go forward for seed or full membership recommendation.

[michael-hawker]

Thanks @glennawatson, I'm back now and will sync with @ChrisSfanos as well. Happy to move forward in steps with the initial open sourcing bit and more of a seed-level of support if that makes it easier, but let me know what the board says. I'll work with Chris on the Microsoft side about any other questions or bits we may need answered (if any).