NuGet package links to outdated license

[jnm2]

nunit/nuget/framework/nunit.nuspec

Line 9 in a8e3688

<licenseUrl>http://nunit.org/nuget/nunit3-license.txt</licenseUrl>

nunit/nuget/nunitlite/nunitlite.nuspec

Line 9 in a8e3688

<licenseUrl>http://nunit.org/nuget/nunit3-license.txt</licenseUrl>

http://nunit.org/nuget/nunit3-license.txt:

Copyright (c) 2015 Charlie Poole

Is this URL a good place to maintain the license into the future or should we use https://github.com/nunit/nunit/blob/master/LICENSE.txt?

[ChrisMaddock]

I agree project specific makes more sense, now different projects are copyrighted in different ways.

[rprouse]

Also agree, nuspecs should probably point to the raw files in GitHub for each project.

[jnm2]

I don't really know what the pros and cons are, but what do you think of linking the GUI version instead of the raw version? https://github.com/nunit/nunit/blob/master/LICENSE.txt

Mostly for this:

Though it also gives you this:

[rprouse]

Interesting question. The raw version is our license, whereas the GUI version is GitHub's interpretation of our license. Their interpretation is correct and I think it adds value, but does linking to that imply acceptance of GitHub's interpretation? Anyone have opinions or experience? The lawyer in me would say that we should link to the raw version, the dev to the GUI version.

Please note, I am not a lawyer, I only play one in issue comments 😄

[ChrisMaddock]

The lawyer in me would say that we should link to the raw version

I am also not a lawyer, and accordingly would keep a licence as simple as possible. 😄

[jnm2]

Good point. Raw sounds safest.

[ChrisMaddock]

This needs to be done in many projects. 😞

Cloning it to just the console for now, so we can get it in the next release.