Adapt to Open-Source Library Guidance from Microsoft

[angularsen]

Open-source library guidance

https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/

This guidance provides recommendations for developers to create high-quality .NET libraries. This documentation focuses on the what and the why when building a .NET library, not the how.

Aspects of high-quality open-source .NET libraries:

• Inclusive - Good .NET libraries strive to support many platforms and applications.
• Stable - Good .NET libraries coexist in the .NET ecosystem, running in applications built with many libraries.
• Designed to evolve - .NET libraries should improve and evolve over time, while supporting existing users.
• Debuggable - .NET libraries should use the latest tools to create a great debugging experience for users.
• Trusted - .NET libraries have developers' trust by publishing to NuGet using security best practices.

• First step: Create a checklist of work items for what UnitsNet needs to do be compliant
• Create issues with milestone Open source library guidance compliance

Tentative work list (not complete)

• Provide debugging sources with SourceLink Provide source with nuget using SourceLink #439
• Use strong name signing and deprecate UnitsNet.Signed packages

[angularsen]

I think the main points are solved now. Closing this.