[Feature Request] Publish docfx packages in the name of .NET foundation

[yufeih]

Today docfx NuGet packages are published in the name of Microsoft. With the transition to .NET foundation, future versions of docfx will be published in the name of .NET foundation.

This will introduce a breaking change to all packages starting with Microsoft.*, as those packages can only be published with a Microsoft signing cert. The candidate new package and namespace naming conventions are: Microsoft.DocAsCode.* -> Docfx.* or Microsoft.DocAsCode.* -> DocAsCode.*

---

• Change copyright in code to .NET foundation and contributors chore: update copyright to .NET Foundation and Contributors #8867
• Getting the .NET foundation code signing certificate (Code Signing Certificate Request: docfx dotnet-foundation/projects#293)
• Change copyright of NuGet packages to .NET foundation and contributors
• Reserve package prefix on NuGet.org: DocFx.* prefix is now owned by the docfx account leaving DocFx.Plugins.* public
• Update docfx NuGet package names and namespaces
• Fix source link signing [Bug] SourceLink is not enabled on NuGet packages #8900
• Transition the docfx nuget account
• Investigate publishing .NET Foundation signed packages to NuGet
• Investigate docfx publish failure
• Publish new packages using the .NET foundation signing cert on GitHub actions
• Deprecate old NuGet packages
• Remove the existing private publish pipeline and associated signing cert and secrets
• Re-enable package validation for Docfx.App.

[KalleOlaviNiemitalo]

There are already third-party packages prefixed with "DocAsCode.":

• https://www.nuget.org/packages/DocAsCode.Dfm
• https://www.nuget.org/packages/DocAsCode.Dfm1
• https://www.nuget.org/packages/DocAsCode.Dfm2

Microsoft.DocAsCode.Dfm is fortunately already dead and won't have to be renamed to DocAsCode.Dfm, which would conflict with the third-party package.

There are also third-party packages prefixed with "DocFX.":

• https://www.nuget.org/packages/DocFx.Plugins.Kroki
• https://www.nuget.org/packages/DocFX.Plugins.Roadmap
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml12
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml13
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml15
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml16
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml17
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml19
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml20
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml22
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml23
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml24
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml25
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml26
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml27
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml28
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml29
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml30
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml32
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml33
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml34
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml36
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml37
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml38
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml39
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml40
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml41
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml42
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml44
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml45
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml46
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml47
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml48
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml49
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml50
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml51
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml52
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml53
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml55
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml56
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml57
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml58
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml59
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml60
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml61
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml62
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml63
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml64
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml66
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml67
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml68
• https://www.nuget.org/packages/DocFx.Plugins.PlantUml69
• https://www.nuget.org/packages/Docfx.ResultSnippets

and some prefixed with just "DocFX" without a dot:

• https://www.nuget.org/packages/DocFxChapterNumbers
• https://www.nuget.org/packages/DocFxTocGenerator
• https://www.nuget.org/packages/DocFxOpenApi
• https://www.nuget.org/packages/DocFxMarkdownGen
• https://www.nuget.org/packages/docfx_project
• https://www.nuget.org/packages/Docfx2xml

I don't know why there are so many DocFx.Plugins.PlantUmldigits packages, or why they were published in September 2022 even though the latest commit in the https://github.com/KevReed/DocFx.Plugins.PlantUml repository is from May 2020.

Will users be confused if official DocFX packages and third-party packages have the same prefix?
Do the third-party packages affect whether you can reserve the prefix in NuGet Gallery?

[yufeih]

It appears we could reserve Docfx.* and leave Docfx.Plugins.* as public, which make sense to me as a naming convention for 3rd party plugins.

[KalleOlaviNiemitalo]

Reserve package prefix on NuGet.org: DocFx.* prefix is now owned by the docfx account leaving DocFx.Plugins.* public

Why does https://www.nuget.org/packages/docfx show "Prefix Reserved" even though the "docfx" name does not include the dot that is in the "DocFX.*" prefix?

[yufeih]

I don't have exact details on how NuGet name reserve works. It seems reserving the Docfx.* prefix did make docfx prefix reserved but does not reserve package names starting with docfx such as docfxabc.

[Lulalaby]

Why does https://www.nuget.org/packages/docfx show "Prefix Reserved" even though the "docfx" name does not include the dot that is in the "DocFX.*" prefix?

If someone requests a namespace reservation for namespace.* the NuGet team reserves namespace. as wildcard and additionally namespace as single package name.

i.e.:

[yufeih]

Newer versions of Docfx.* packages have been published to NuGet.org successfully. The docfx package is pushed to NuGet but failed package validation due to signing cert change. Need to work with NuGet team together to get it fixed.

[yufeih]

The v2.70.0 release is out and fully on .NET foundation 🚀

[Lulalaby]

Congrats! Happy that this is finally done ❤️🚀