incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <>
Subject Re: Question related derivative code based on our Apache licensed code
Date Wed, 04 Jan 2012 21:52:35 GMT
----- Original Message -----

> From: eric b <>
> To:
> Cc: 
> Sent: Wednesday, January 4, 2012 4:44 PM
> Subject: Re: Question related derivative code based on our Apache licensed code
> Hi,
> Le 4 janv. 12 à 22:32, Joe Schaefer a écrit :
>>  I'm having a hard time following your English prose, but I'll take 
> a stab at it...
> Apologies, I'm not a native speaker, and I do my best. Sometimes, I need 
> hours to write simple mails :/
>>  So the situation you find yourself in is that you are making use of 
> LGPL'd code (OOo 3.2.1), and in the interests of porting over OOo4Kids to 
> Apache OpenOffice you need to take portions of that 3.2.1 codebase and commit it 
> back to Apache's subversion repo?
> Not exactly  :
> I'd like to take files from Apache repo, and put them into the OOo4Kids 
> one.  This needs to adapt OOo4Kids to Apache tree (based on DEV300_m106).

In that case be our guest.  You may keep the LGPL licensing on the larger work
if you so choose, and you may alter the licensing on individual files by adding
LGPL headers to them (but NOT REMOVING Apache License/Copyright headers, just
insert a comment saying "portions originally licensed under the following...".

> About possible backports:  I'd like to keep OOo4Kids under LGPL v3, but 
> I'm ok to reverse features considered as enough interesting to be integrated 
> into Apache OOo (I hope I'm clear)
> At the begining, OOo4Kids (and OOoLight) are "toys" used as a lab, to 
> test Fun and new features with students, or simply to analyze performance 
> issues. The second idea was to reverse interesting code into OOo.

You are free to do whatever you like with your own creative work, but please
refrain from incorporating 3rd party contributions to OOo4Kids into Apache
Openoffice without explicit permission from the authors of those contributions.


View raw message