I wonder how viable this is for existing packages! It will be a brand new package with no good way to tell existing NuGet consumers that there is a new version of the package in a completely new namespace..