[Feature request]: Minute license metadata issues

[ulfllorenz]

Is your feature request related to a specific problem? Or an existing feature?

I have been preparing a Software Bill of Materials for a Polly-consuming product, and I have a smaller issues with the current state of the Nuget packages (Polly and Polly.Core). While I would not consider them critical, they are as easy to fix as they are arcane, so I thought I'd raise this.

Right now, the Nuget package provides a license expression (good), a licenseUrl (not so useful) and a copyright (misleading). My quibble is that the license in the repository is pretty clear: Consumers of Polly must provide the copyright as found in the license file. And this copyright differs from the one in the Nuget package.

Describe the solution you'd like

One solution would be to provide the license file as it is in the repository in the Nuget file, that would make the package self-contained; the copyright in the Nuget metadata could be scrapped for the sake of having a single source of truth.

Additional context

No response

[martincostello]

The copyright also flows into the compiled assemblies as well, not just the NuGet package.

I don't have a problem with them being consistent. I'm less sure on what specifically The One Copyright™ text should be.

When there's an answer to that, we can make them match.