We are pleased to report that the Final Draft makes the Apache License, version 2.0, fully compatible with GPLv3. We are grateful to the Apache Software Foundation for working with us to achieve this long-sought goal, stated the FSF.
Developers have always been able to deploy Apache-licensed code such as the Apache web server and Geronimo application server alongside GPLv2-licensed code such as the Linux operating system or MySQL database.
Assuming those projects move to the new GPLv3 developers will now have the ability to merge the two code bases without running foul of either license.
Integration with version 2.0 of the Apache License has been one of the aims of the GPLv3 draft process but looked unlikely after the FSF admitted defeat in March with the publication of draft three of GPLv3.
The major stumbling block was a clause in the Apache license requiring downstream redistributors to indemnify upstream licensors. According to the FSF, its discussions with the Apache Software Foundation revealed that perhaps it was not such a major issue after all.
The concerns we stated in the Draft 3 Rationale were based on varying literal readings of section 9 of the Apache license that differed from the interpretation of section 9 held by the ASF itself, stated the FSF, adding that discussions enabled the two to come to agreement over the interpretation of certain clauses.
That, along with other changes related to indemnification, trademarks and patent termination completed the job.
It is not guaranteed that all GPLv2-licensed projects will migrate to the new GPLv3 when it is completed at the end of the month. Linux kernel creator, Linus Torvalds, has previously stated his intention to keep Linux on GPLv2, although the publication of draft three of GPLv3 in March he said that improvements meant that it was now a possibility that it would move to version 3.
In January open source database vendor MySQL changed the license for its product from GPLv2 or later to GPLv2 only in order to avoid moving to the GPLv3 by default, although it maintained that it was just hedging its bets until the GPLv3 was completed and it could gauge acceptance levels.
