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
feat: update to MIT license #3376
Conversation
All 353 screenshot tests passed for commit a973acf vs. |
Codecov Report
@@ Coverage Diff @@
## master #3376 +/- ##
=========================================
Coverage ? 98.45%
=========================================
Files ? 123
Lines ? 5181
Branches ? 639
=========================================
Hits ? 5101
Misses ? 80
Partials ? 0
Continue to review full report at Codecov.
|
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.
This should also update all instances of "license": "Apache-2.0"
across package.json
s to "MIT"
.
Also, I guess we need to update the license blurb in every single source file... (I'd suggest going one file type at a time since the comment syntax is different for each.)
I imagine doing this will cause every package to get a version bump by lerna on the next release; I'm not sure if there's a way to avoid that (but I probably shouldn't be worrying about it anyway).
All 353 screenshot tests passed for commit d8c6fb1 vs. |
55555f5
to
cb35cb6
Compare
All 353 screenshot tests passed for commit 55555f5 vs. |
All 353 screenshot tests passed for commit cb35cb6 vs. |
All 353 screenshot tests passed for commit 79b8e54 vs. |
All 353 screenshot tests passed for commit 2222a39 vs. |
1 similar comment
All 353 screenshot tests passed for commit 2222a39 vs. |
Hi, we're using MDC web and I was informed that a scan with ORT detected references to both MIT but also Apache in many components, despite the whole base was moved from Apache to MIT. For instance, in material base 15.0.0-canary.684e33d25.0 the scan detects The MIT License We are struggeling to understand which license applies, or both? |
We're moving MDC Web to the MIT license.
At Google we prefer to license new projects under the Apache 2 license because we feel it gives the most rights to developers and creates a strong legal scaffold for projects to grow and thrive. However, what we've heard from users in the MDC Web community is that you prefer the MIT license. It's more widely used within JavaScript projects, it's shorter, and it’s better understood.