-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Maui.Graphics into the main .NET MAUI repository #7901
Comments
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 So happy to see this happen! |
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: |
This will be awesome . |
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: |
I hope this will help resolving the From the README.md:
Is that still true? |
That information is out-of-date. |
@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. |
@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! |
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
The text was updated successfully, but these errors were encountered: