Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

MichaelSimons
Copy link
Member

Per agreement reached in the past, the reference packages should have an MIT license.

Comment on lines +87 to +88
nuspecContent = nuspecContent.Replace("http://go.microsoft.com/fwlink/?LinkId=529443", MicrosoftMitLicenseUrl);
nuspecContent = nuspecContent.Replace("http://go.microsoft.com/fwlink/?LinkId=329770", MicrosoftMitLicenseUrl);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we don't just replace all of the content in<licenseUrl>*</licenseUrl> instead of just these specific fwlinks?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding of the agreement is that old FX packages that are Microsoft licensed can be updated to MIT. @leecow to confirm.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean "can't be updated"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean "can't be updated"?

No - They can be updated to MIT. That is what this change is doing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, got it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is true but would need @richlander to confirm.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to grasp the scope of this. There are a lot of packages here. I looked at Microsoft.Build.Framework. It is MIT, so changing to MIT seems like a correction rather than needing an agreement. Are there some packages that are not MIT?

It seems like getting issues created for packages that are not MIT is the correct path. Yes?

Also, we should move off of licenceUrl to licenseExpression.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a lot of packages here. I looked at Microsoft.Build.Framework. It is MIT, so changing to MIT seems like a correction rather than needing an agreement.

The following packages being updated in this PR fall into this category which is older versions are Microsoft licensed while the latest versions are MIT.

  • microsoft.build.framework/15.1.1012 -
  • microsoft.build.framework/16.0.461
  • microsoft.build.utilities.core/15.1.1012
  • microsoft.build.utilities.core/16.0.461
  • system.composition.attributedmodel/1.0.31
  • system.composition.convention/1.0.31
  • system.composition.hosting/1.0.31
  • system.composition.runtime/1.0.31
  • system.composition.typedparts/1.0.31
  • system.text.encoding.codepages/4.3.0
  • microsoft.codeanalysis.common/2.9.0
  • microsoft.codeanalysis.csharp/2.9.0

The following packages are older packages that aren't being produced anymore and do not have a newer version that is MIT licensed

  • system.diagnostics.stacktrace/4.3.0
  • system.runtime/4.3.1
  • system.runtime.extensions/4.3.1
  • system.text.regularexpressions/4.3.1
  • system.threading.tasks.parallel/4.3.0
  • system.valuetuple/4.3.0
  • system.xml.xpath/4.3.0
  • system.xml.xpath.xdocument/4.3.0
  • netstandard.library/1.6.1

It seems like getting issues created for packages that are not MIT is the correct path.

That would require republishing the packages which would have to be a new version though wouldn't it? This is the reason for this manual update.

Also, we should move off of licenceUrl to licenseExpression.

I generally agree but for the purpose of this repo, we would like to mirror how the original nuspec is defined as much as possible.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the detailed info.

@MichaelSimons MichaelSimons merged commit b34c643 into dotnet:main Jun 15, 2023
@MichaelSimons MichaelSimons deleted the update-licenses branch June 15, 2023 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants