Move Maui.Graphics into the main .NET MAUI repository

[hartez]

To make issue tracking, maintenance, and integration easier, we will move Maui.Graphics from it's current home (https://github.com/dotnet/Microsoft.Maui.Graphics) into this repository.

Maui.Graphics will continue to be built/distributed as a separate NuGet package, and will retain it's own solution and build process; using and contributing to Maui.Graphics won't change. We will continue to ship updates to Maui.Graphics independently from .NET MAUI.

Rationale

Because .NET MAUI depends on Maui.Graphics so heavily, a lot of users aren't clear on where to report graphics-related issues with .NET MAUI. And because the graphics issues are in another repo, the .NET MAUI team is spending a lot of maintenance effort watching two repos, making sure issues are in the correct repo, de-duplicating issues between the repos, making sure fixed issues are closed, etc. By putting this all in one place, we can reduce the overhead and confusion.

Issues

Part of this task will be transferring all of the open issues from Maui.Graphics to this repository.

Projects Merged

• Microsoft.Maui.Graphics (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Move Microsoft.Maui.Graphics.Blazor.* into the Maui repo #8691
• What is the support for Microsoft.Maui.Graphics.Forms #8699
• Move Microsoft.Maui.Graphics.GDI.Winforms into the Maui repo #8692
• Move Microsoft.Maui.Graphics.Gtk into the Maui repo #8694
• Move Microsoft.Maui.Graphics.SharpDX.* into the Maui repo #8693
• Microsoft.Maui.Graphics.Skia (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Microsoft.Maui.Graphics.Skia.Forms (What is the support for Microsoft.Maui.Graphics.Forms #8699)
• Microsoft.Maui.Graphics.Skia.GtkSharp (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Microsoft.Maui.Graphics.Skia.WPF (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Microsoft.Maui.Graphics.Text.Markdig (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Move Microsoft.Maui.Graphics.Text.WPF into the Maui repo #8695
• Move Microsoft.Maui.Graphics.Win2D.UWP into the Maui repo #8696
• Microsoft.Maui.Graphics.Win2D.WinUI.Desktop (Merge Maui.Graphics into Maui! (net6.0) #8147)
• Move Microsoft.Maui.Graphics.Xaml.UWP into the Maui repo #8697
• Move Microsoft.Maui.Graphics.Xaml.WPF into the Maui repo #8698

[adegeo]

Man, I just was sitting here hunting around for 20 minutes trying to find the classes and types and where the code was. Funny thing is that the source peek in Visual Studio didn't give me the header text telling me the Color type is in a different DLL so I was really hunting around the main source for the type. I was using powershell select-string trying to find the code etc. Finally I realized it was in a different repo...

So happy to see this happen!

[Eilon]

Part of this task will be transferring all of the open issues from Maui.Graphics to this repository.

There is no REST API for this, but it appears that the GitHub CLI can do transfers: https://cli.github.com/manual/gh_issue_transfer. Or, if you're into GraphQL, there is a GraphQL mutation API for it https://docs.github.com/en/graphql/reference/mutations#transferissue

After moving the code and open issues, please add a note to the README saying where to find the code/issues, and then Archive the repo, which is what we've done to other repos that had their code moved to somewhere else. Example:

[manishbisen]

This will be awesome .

[Eilon]

Of course I forgot to actually put an example. Here's an example archived repo whose code moved: https://github.com/aspnet/RazorTooling

And GitHub shows a nice info bar at the top:

And we updated the readme to tell folks where to go:

[janseris]

I hope this will help resolving the Maui.Graphics issues quicker.

From the README.md:

Status

This is an experimental library;

Disclaimer

There is no official support

Is that still true?

[hartez]

Is that still true?

That information is out-of-date.

[adegeo]

@Eilon I would ping the .NET SDK team, they swapped repos 1 or 2 years ago and had quite a number of open issues to contend with, they may have a tool or something ready to go.

[Eilon]

@adegeo I was one of the ones who did this for the AspNetCore repo several years ago, moving thousands of issues 😄 But back that I used Selenium (I think?) to automate the GitHub UI using FireFox because there was no API for moving issues!

These days with the GitHub CLI or GraphQL it should take like 10 minutes to move everything 😄 There aren't even that many issues, so it would take longer to fully automate it than it would to just run the GitHub CLI a few dozen times!