NuGet package names

[pepone]

There is an existing Slice package in NuGet.org https://www.nuget.org/packages/slice

We will not be able to publish our Slice package to NuGet.org:

• We can ask the owner to give the package to us, and then ask NuGet admins to remove the existing versions and reserve the prefix for ZeroC.
• Or, We can add ZeroC prefix to all our packages, we already own this NuGet prefix.

[bernardnormier]

Per the Microsoft guidelines, it seems extremely unlikely we can get the Slice package/prefix, even if the current owner agreed: https://learn.microsoft.com/en-us/nuget/nuget-org/policies/deleting-packages

We don't own the Slice trademark, and it would take a while to get it (if we're successful).

So I think the best option is to do like Google with Protobuf and gRPC: ZeroC.Slice and IceRpc + IceRpc.*. Note that we own both trademarks (ZeroC and IceRPC).

With package/assembly ZeroC.Slice, it makes sense to use namespace ZeroC.Slice too.

Naturally "Slice" remains Slice. It's still the Slice language, the slicec compiler, the .slice extension, and the IceRpc.Slice namespace that provides the IceRPC-Slice integration.

[pepone]

• ZeroC.Slice package/namespace
• IceRpc.Xxx package/namespace including (IceRpc.Slice)

What about (IceRpc.Slice.Tools) we keep this as is?

[bernardnormier]

Yes, I would keep IceRpc.Slice.Tools as is. See my blog.