Since there hasn't been any changes made due to most of the project source being moved to https://github.com/CommunityToolkit/Windows (and almost everything here is now not supported), I suppose the repo itself can also be archived as well.

Since there hasn't been any changes made due to most of the project source being moved to https://github.com/CommunityToolkit/Windows (and almost everything here is now not supported), I suppose the repo itself can also be archived as well.

We prefer to keep it open so we can redirect folks who still aren't aware of the move. Even with all the signage, people still miss it.

It might help to unlist the 7.x packages on NuGet and archive that 7.x documentation.

It might help to unlist the 7.x packages on NuGet and archive that 7.x documentation.

@Lamparter back in Aug we redirected the old packages, as we called out here: https://devblogs.microsoft.com/ifdef-windows/announcing-windows-community-toolkit-v8-1/#older-package-nuget-redirects

We're working on redirecting the docs (that's been a very complex process), but we're getting closer there. We should have new API ref docs up soonTM️ and hopefully redirecting the old /windows docs to the /dotnet ones.

I think once that happens and we have the full mapping of what's missing between versions, then we'll use the GitHub archive feature for this. There's just been a couple of these things that have just left us to leave things open vs. archiving, unarchiving, and rearchiving.