Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A124B212 for ; Wed, 4 Jan 2012 14:38:32 +0000 (UTC) Received: (qmail 67549 invoked by uid 500); 4 Jan 2012 14:38:32 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 67494 invoked by uid 500); 4 Jan 2012 14:38:32 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 67486 invoked by uid 99); 4 Jan 2012 14:38:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 14:38:31 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [98.139.91.190] (HELO nm4-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.190) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 04 Jan 2012 14:38:22 +0000 Received: from [98.139.91.62] by nm4.bullet.mail.sp2.yahoo.com with NNFMP; 04 Jan 2012 14:38:00 -0000 Received: from [98.139.91.27] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 04 Jan 2012 14:38:00 -0000 Received: from [127.0.0.1] by omp1027.mail.sp2.yahoo.com with NNFMP; 04 Jan 2012 14:38:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 626213.34328.bm@omp1027.mail.sp2.yahoo.com Received: (qmail 35070 invoked by uid 60001); 4 Jan 2012 14:38:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1325687880; bh=c//L8ML7un8W/n2IuSzP7wmcIUTFyLrK7+LjNyNLDjQ=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=cwx7dhYNFg6WREAlUAnX7USlViVxzLYmnrJVohTZS0zCSD4HxAuE1Rn6t73Oogx3l0uJlGUFGKn186MOW4m9l8RsVABPOi4Xlj0ttwkaPHpG0ikRIR9vNopqNN0LipCwxRPERjjDY95cBRv3q37HmMl4VFZaB5SLoV2s362tp/U= X-YMail-OSG: a0JCkeIVM1n2FVnjfaQuiydpJ2FphTJCNN4KIMB53LuKvZM gci152CFVIoV95LVhDfaZWragGzV5TPyoVhH88QldDPIt5B7hSR8dApyAMJM HzaLgsU.pTp4Rz0noy9o77dNey.i12ZCK8k1LM9jr73v7oWQv1HrrNehDLTR B0hHoEB9ccsnO65yFtcvpMnPlFacXGxZJ1l.qu1lHBTlU4f8kOQwuRIeolB9 xFUmg9MV1xmq.oV_k8_NtvToGUQpeRHYCIJ7IONdMN6hjsKSAVO5SZh3cBcp mW0abGvRUG1kfDN6u_Oaa72gdB.gwjCb.xkNmznQXq6Qi612XXt6kDQXyFJD un2Rk6Jcq9xyuleRtOXl7yYCmLnbqq8HSol1SpKKhOVDK5DAcurQFgasJ4bY ovV8MlUG4TJu0NO0LVm90b9Z4QA6BEwNpXxrSPUtAs.PeaGbCP7Zkz_3hlzv s0WVE8ZU9LbMZXENjhsh8S8Kb Received: from [200.118.157.7] by web113514.mail.gq1.yahoo.com via HTTP; Wed, 04 Jan 2012 06:38:00 PST X-RocketYMMF: giffunip X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698 Message-ID: <1325687880.31665.YahooMailClassic@web113514.mail.gq1.yahoo.com> Date: Wed, 4 Jan 2012 06:38:00 -0800 (PST) From: Pedro Giffuni Reply-To: pfg@apache.org Subject: Re: Question related derivative code based on our Apache licensed code To: ooo-dev@incubator.apache.org In-Reply-To: <4F044D22.80303@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A--- Mer 4/1/12, J=FCrgen Schmidt ha scritto:=0A...=0A> >=0A> are you sur= e? For me this special situation seems to be a=0A> little bit different. Ei= ther you go forward with the old=0A> code and the old license header and ca= n't merge to the new=0A> code. Or you move forward with the new one and kee= p the new=0A> license headers and put your change on a different =0A> licen= se. Where you would make the difference which code is=0A> from which code b= ase. For me it sounds practical impossible=0A> because the many thousand fi= les with more or less the same=0A> code.=0A>=0A=0AThe problem is that TDF, = or whomever adopts the Apache OO=0Aheaders, doesn't own the modified (MPL/L= GPL3) code so even=0Aif they wanted they can not make it AL2. What will hap= pen=0Ais that the code will keep the MPL/LGPL3 restrictions in=0Aaddition t= o the AL2.=0A=0ANevertheless there will be two consequences:=0A- They can h= ave all their code uniformly under LGPL3/MPL2=0Adual license. The LGPL bein= g so commercially unfriendly,=0Athis practically means they will be MPL2, w= ith the LGPL3=0Abeing purely nominal.=0A- They will have to carry the AL2 l= icense among their code=0Aand headers, and the clause 5 is particularly nic= e to have.=0A=0AIf you add these two points, and this is all IMHO, the=0Agr= eat loser in all this is the FSF that lost the strong=0Acopyleft over the f= lag opensource Office suite.=0A=0A> =0A> It is really a special situation, = isn't it. It would be=0A> interesting to =0A> hear what a lawyer things abo= ut it.=0A> =0A=0AOh .. I am not a lawyer, so it was all meant IMHO :).=0A= =0Acheers,=0A=0APedro.