Update license for .NET Core NuGet packages

[richlander]

We are adopting a plan to change the license and copyright of .NET Core packages. We want to make this change for open source packages. If there are packages that are still closed source, in part of in full, they should not be affected by this change.

Is this the right change to make to achieve the stated goal, above?

I saw that there are nuspecs in this repo and know that Roslyn and other components have their own approach. I thought we should start here.

More context: https://github.com/dotnet/corefx/issues/12190

[terrajobst]

Love it!

@jaredpar how do you guys generate the Microsoft.CodeAnalysis.* packages? You're not using build tools, right? So we probably need to replicate this change there.

@richlander @DamianEdwards @Eilon who does packaging on the ASP.NET side? We probably want the same change there.

[Petermarcu]

@ellismg @ericstj to review the change.

[DamianEdwards]

Adding @Eilon for ASP.NET considerations

[Eilon]

I'd like to get an official message from LCA on this. They are rarely happy when I change a license without hearing from them first! 😄

[terrajobst]

We've already clarified this with LCA for .NET Core. I don't think we need to treat ASP.NET Core separately because you guys use the same EULA we do.

[Eilon]

@terrajobst we use different licenses in GitHub (Apache vs. MIT), though we do use the same license in NuGet.org. For that reason, I'm not certain the conclusion is the same, because ASP.NET Core would end up using a very different license.

[terrajobst]

Oh, I didn't know hat. I always assumed you were on MIT as well. In that case let me loop you in on the discussion we have.

[richlander]

/cc @ellismg

[stephentoub]

@richlander, should this PR from over a year ago be closed?