I don't know what "MIT [doesn't let] you change the license" is supposed to mean.
The original project is licensed under MIT. The Google project said to incorporate that code is licensed under Apache 2.0. This is permitted by the terms of the MIT license.
If there is any wrongdoing here, it looks like a failure to `git add ./NOTICES.txt`, and that's as simple as the remedy to it would be, too.
I don't know what "MIT [doesn't let] you change the license" is supposed to mean.
You cannot take code licensed under MIT, delete the MIT license, and supply a different license instead.
This is permitted by the terms of the MIT license.
It is permitted to include MIT licensed code in a project that also contains Apache licensed code, but it is not permitted to change the MIT licensed code to be Apache licensed.
The result is a project where different code has different licensing.
The problem is not that the project is Apache licensed, it's that (according to TFA anyway) the project relicensed MIT files as Apache 2 and removed attribution, both of which are verboten.
You can have MIT-licensed files in an Apache-licensed project, you can not strip out their original licenses and put yours instead.
Licenses aren't per project, they are for any copyrightable piece of code, you can have multiple even inside a single file. MIT lets you mix with Apache licensed code, but you still have to indicate the original license.
Comments
It doesn't; while the MIT is a permissive license, that doesn't mean that it lets you change the license.
This is true, but you still have to follow its terms, just like any other license.
(I have not actually looked at the repo or investigated the details in this specific case.)
I don't know what "MIT [doesn't let] you change the license" is supposed to mean.
The original project is licensed under MIT. The Google project said to incorporate that code is licensed under Apache 2.0. This is permitted by the terms of the MIT license.
If there is any wrongdoing here, it looks like a failure to `git add ./NOTICES.txt`, and that's as simple as the remedy to it would be, too.
You cannot take code licensed under MIT, delete the MIT license, and supply a different license instead.
It is permitted to include MIT licensed code in a project that also contains Apache licensed code, but it is not permitted to change the MIT licensed code to be Apache licensed.
The result is a project where different code has different licensing.
The problem is not that the project is Apache licensed, it's that (according to TFA anyway) the project relicensed MIT files as Apache 2 and removed attribution, both of which are verboten.
You can have MIT-licensed files in an Apache-licensed project, you can not strip out their original licenses and put yours instead.
Licenses aren't per project, they are for any copyrightable piece of code, you can have multiple even inside a single file. MIT lets you mix with Apache licensed code, but you still have to indicate the original license.