GPLv2 vs Apache2 license about android HOT 7 CLOSED

I am no lawyer either and not an OSS license specialist, so @karlitschek or @jancborchardt or @LukasReschke can you answer this? Cc @jospoortvliet

from android.

Summoning @schiessle as well on this. Go GNU/Björn 😉

from android.

Any info on this @schiessle @karlitschek? If this is a problem, then it’s an issue with the original code too and the relicense to GPLv2 from the previous GPLv2+ might have been not proper.

from android.

I think Apache dependencies are not a problem. But @schiessle is the expert here!

from android.

Yes, the Apache license and GPLv2 are not compatible because of the patent grant in the Apache license.

I'm not a Android expert, if the "Google's Android support libraries" are system libraries this shouldn't be a problem, because of the "system library exception" https://www.gnu.org/licenses/gpl-faq.html#SystemLibraryException

from android.

We can't change the license from GPLv2 only to GPLv2+ because we don't own the copyright on the complete source code. But I would suggest to consider switching to GPLv2+ for every new code added to the android app. We do something similiar on the server (ownCloud code is AGPLv3 only but we add new code as AGPLv3+)

from android.

We are doing it the @schiessle proposed: every new code done by us is GPL3+

from android.