Uploading a package to a reserved namespace should tell the user who in fact owns it and how to contact them.

[AraHaan]

In appveyor I expericenced this issue with my System.Runtime.InteropServices.GitInformation package (I plan to donate or give the package away to the .net foundation sometime anyway for .net standard or .net core usage) The package is for embedding the git repository information including if it was a "clean" or "dirty" tree in the assembly for the end user could obtain and decide if they want to test any local (possibly with unstable changes) if they so desired. However I do not know who the owner is to request access just to post the package.

I also plan to give away the GitBuildInfo msbuild task package as well with it as it works in .net core as well.

https://ci.appveyor.com/project/AraHaan/system-runtime-interopservices-gitinformation/builds/23758130

[skofman1]

@AraHaan , thanks for reaching out! System.* domain is reserved for official Microsoft packages. Uploading unofficial packages under this prefix is confusing to users and we have had multiple complaints about this. You will be able to upload under a different name.

[AraHaan]

hmm @skofman1 perhaps on generation of the *.nupkg warn if one of the owners / authors is not Microsoft on those then?

like for example:

warning ????????: Having a package with the System.* prefix is reserved for Microsoft packages and may not be uploaded.

Maybe I should log a bug for this on the nuget pack command.

[skofman1]

@AraHaan , if I undersand your suggestion correctly - When you upload a package and get an error that the package id is in a reserved namespace, you would like the error message to contain the username that owns the namespace. Correct? I think the correct command for this error message is push and not pack since pack doesn't perform any network calls.

[AraHaan]

yes, that is exactly what I would like to happen.

[gep13]

@skofman1 To elaborate further on this...

As an owner of a reserved package prefix on NuGet.org, I would like the ability to provide a custom message for when an attempt to push a package to an exclusive prefix is attempted. Different teams have different ways of communicating. Email, Slack, Gitter, Teams, Discord, etc. It would be good to be able to provide a custom message that exactly explains what to do when this occurs.

Just my thoughts...