I want to publish one of my libraries as a nuget package for the first time, because I’ll reuse it quite often, and I find nuget packaging to be more convenient (and stable) than adding a remote .csproj every time, especially for people who might git clone my repositories on GitHub.
I never published a nuget package before so I didn’t have to deal with this issue before. But the problem is fairly simple: According to the best-practices of C# library development, each library should be prefixed with a namespace indicating an organization where it came from.
However, this enterprise-minded guideline completely ignores that I’m not part of any organization. So, how am I supposed to stay conventional and prefix my libraries with an appropriate namespace then? How do other single developers deal with this?
The only two options I thought of so far were:
- Choosing a permanent long-term namespace to prefix all of my libraries. The problem is that I don’t have any idea after what to name it, also that it doesn’t indicate “where it came from”.
- Prefixing my libraries with my surname or full name, but ins’t it just weird to see your name appears as an identifier to a package and library namespace?