Publishing an extension named Hangfire.Something on NuGet

[0xced]

I plan to publish an extension for Hangfire on nuget.org but I see on https://www.nuget.org/packages/Hangfire/ that the prefix is reserved.

I also see many packages named Hangfire.* which are published on NuGet, many are even mentioned on https://www.hangfire.io/extensions.html

If I try to publish Hangfire.Something on nuget.org tomorrow, will it succeed or will it fail because of the prefix reservation? If it fails, what's the recommended approach?

The Serilog project is handling community contributions through the Serilog Contrib organization, which is pretty nice.

[odinserj]

Yes, the "Hangfire*" ID prefix is reserved to official packages only, so any new packages can't be submitted under this name, to have a better distinction between official packages and community ones. Previously, it wasn't possible to have such a reservation, so there are also some older community-based packages that start with this prefix. But for new packages, there are two options:

1. Use Hangfire.Community prefix that's whitelisted, e.g. Hangfire.Community.Something
2. Start with your own prefix, like MyCompany.Hangfire.Something, which is also a popular practice