> If you contribute code to a project under Apache 2.0 terms Apache 2.0 is applied per source file, not per the whole project. This is unlike copyleft licenses

> If you contribute code to a project under Apache 2.0 terms Apache 2.0 is applied per source file, not per the whole project. This is unlike copyleft licenses like the GPL, which have a demand for the whole project to be licensed under GPL-compatible terms. In other words, for a repository that mixes Apache 2.0 with proprietary code, your contribution isn't necessarily licensed under Apache 2.0, unless you're explicit about it (e.g. the source file has the license header). That said, even if the license if liberal (like Apache 2.0 is), that doesn't mean anybody can change it without your approval. This is a common misconception with liberal licenses. Just because the license is very permissive, that doesn't mean you can copy / paste that code and re-license it in any way you want, without explicit permission from the author. So you're correct in that regard.