[tahoe-dev] Is TGPPL compatible with Apache license?

[Daira Hopwood (formerly David-Sarah)]

On 14/05/13 17:41, Daira Hopwood (formerly David-Sarah) wrote:
> On 13/05/13 16:19, Zhou, Yuan wrote:
>> Hi lists,
>>
>> I've got some updates here, after a sync up with our legal, here is the new question:
>>
>> 1. If we combine TGPPL code with Apache code to create one work derived from both TGPPL
>> code and Apache code, can we redistribute such work under Apache license only and
>> permanently?
> 
> No. The TGPPL obligates you to release the part of the work that was derived from the
> TGPPL code under GPL after one year (if you distribute it at all), and that would cause
> a conflict with the Apache license. That is, in the absence of any license exceptions
> you would not be able to redistribute the work at all after one year, under any license,
> as far as I understand.
> 
> Note that Tahoe-LAFS has the Apache license exception (in both its GPL and TGPPL
> licensing options), so you *can* create a work derived from both Tahoe-LAFS and an
> Apache-licensed work, and redistribute it after one year. However, you cannot do so
> under a pure Apache license; you must keep the Tahoe-LAFS-derived parts licensed under
> the GPL.

If I understand correctly it's also possible to relicense the whole thing under the GPL,
for simplicity, since the Apache license allows you to do that.

-- 
Daira Hopwood ⚥  (formerly David-Sarah)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130514/76d38f3e/attachment.pgp>