You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently preparing a Software Bill of Materials, and had some licensing issues with the MathNet.Numerics package. These issues are only slightly inconvenient because of our special tooling and rather arcane, but may be easy to resolve.
I have three suggestions for the Nuget package [edit: We use only MathNet.Numerics without MKL etc.] :
Remove the license URL. It contains only generic text that is not helpful here.
Ship the license file in your repository with the Nuget package.
Remove the copyright tag. The relevant copyright line is not what is in the license file.
The three changes are interrelated. If you read the license file carefully, it mandates that the copyright information from the license file must be supplied by your consumers. This copyright information is missing in https://licenses.nuget.org/MIT, and it does not match the one in the package metadata. Supplying the license file in the Nuget package would supply a single source of truth in this respect.
The text was updated successfully, but these errors were encountered:
I am currently preparing a Software Bill of Materials, and had some licensing issues with the MathNet.Numerics package. These issues are only slightly inconvenient because of our special tooling and rather arcane, but may be easy to resolve.
I have three suggestions for the Nuget package [edit: We use only MathNet.Numerics without MKL etc.] :
The three changes are interrelated. If you read the license file carefully, it mandates that the copyright information from the license file must be supplied by your consumers. This copyright information is missing in https://licenses.nuget.org/MIT, and it does not match the one in the package metadata. Supplying the license file in the Nuget package would supply a single source of truth in this respect.
The text was updated successfully, but these errors were encountered: