Opened 11 years ago

Last modified 4 years ago

#1037 new enhancement/feature request

Apache License, Version 2.0 not compatible with GPLv2 (would only be with GPLv3)

Reported by: zoff99 Owned by: cp15
Priority: minor Milestone: version 0.6.0
Component: port/android Version: git master
Severity: Keywords: license, legal, gpl
Cc: cp15


Some files are licensed with Apache License, Version 2.0

(some) of those files are:

this website explains that this is not allowed to mix with GPLv2

was it on purpose by the original author(s) to license some files with that license? was it a mistake? what to do? (this also affects forks of the project!)

maybe the license of those files can be changed to GPLv2? all the authors should agree on some solution to be conform with license

Change History (4)

comment:1 Changed 11 years ago by tryagain

I'm unsure if we can violate something by distributing in one package code with different open licenses, having each piece clearly marked with corresponding license information.

I think term 'compatibility' in above faq discuss rather ability to relicense Apache-licensed code under GPLv2 or GPLv3. We don't do anything similar. We just (a) distribute both pieces of code in the same package and (b) distribute compiled version of both code in the same binary, having both licenses limitations conformed.

Legal disclaimer: I'm not the lawyer ;-)

comment:2 Changed 9 years ago by usul

  • Cc cp15 added
  • Keywords legal gpl added
  • Milestone set to version 0.5.1

Needs to be clearified esp. in the context of a (maybe) upcomming license change and dealing with license restrictions on several app stores.

comment:3 Changed 5 years ago by

  • Milestone changed from version 0.5.1 to version 0.5.2

This ticket was pushed back in order to bring 0.5.1 out soon.

comment:4 Changed 4 years ago by

  • Milestone changed from version 0.5.2 to version 0.6.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.