-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Update license from Apache to MIT #34573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I suggest reviewing commit by commit, and skipping the second and |
@@ -10,7 +10,7 @@ | |||
"sauce": "ts-node ./scripts/sauce.ts" | |||
}, | |||
"author": "", | |||
"license": "Apache-2.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a bunch of package.json
files with author of empty or Microsoft, should those be updated?
@@ -22,10 +22,10 @@ | |||
"architecture":"any" | |||
}, | |||
|
|||
"copyright": "Microsoft", | |||
"copyright": ".NET Foundation and Contributors", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the right thing to do? @dleeapho ?
src/Mvc/Settings.StyleCop
Outdated
<Analyzer AnalyzerId="StyleCop.KRules.FileHeaderRule"> | ||
<Rules /> | ||
<AnalyzerSettings> | ||
<StringProperty Name="FileHeaderText"> Copyright (c) Microsoft Open Technologies, Inc. All rights reserved. Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information.</StringProperty> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Figured this was no longer relevant
Are we going to handle non cs files later? |
The Find and Replace step got them. I did a |
Oh, probably the second commit, which we can't really look at :D |
Yes, that's my expectation. |
|
Looks like this wasn't done properly: |
#yolo approval. I can't quite review all the files, but the general gist of it seems right. @Pilchie I would recommend starting starting the editorconfig rule as a suggestion and doing a second pass that turns in to warnings and clearing up the build warnings. Less chances that you run in to perpetual file conflicts that way. |
@dotnet/aspnet-build Looks like some provisioning failures here. What's the best way to re-run? |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
It's green - going to merge! |
Fixes #18873.
Most work done by either Find and Replace or the Visual Studio fix to add missing headers.