Return-Path: X-Original-To: apmail-legal-discuss-archive@www.apache.org Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DF39B183A0 for ; Wed, 16 Sep 2015 18:53:01 +0000 (UTC) Received: (qmail 79134 invoked by uid 500); 16 Sep 2015 18:52:55 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 78969 invoked by uid 500); 16 Sep 2015 18:52:55 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 78939 invoked by uid 99); 16 Sep 2015 18:52:55 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 18:52:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B0EEBF3411 for ; Wed, 16 Sep 2015 18:52:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.046 X-Spam-Level: *** X-Spam-Status: No, score=3.046 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.046, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id vQAZ_FPISddd for ; Wed, 16 Sep 2015 18:52:44 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id B9BC844569 for ; Wed, 16 Sep 2015 18:52:43 +0000 (UTC) Received: by padhy16 with SMTP id hy16so216615144pad.1 for ; Wed, 16 Sep 2015 11:52:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=x6lYzUFqsp0DzGu0G2a9kEYbd6DP43MlEXv/7cDISgM=; b=jjmy39jF0scFQcm+J2Gr0jzm1Atn4a4v2xFWD5w4tGhQlY8TxxsbbgyNhL+qTdhMxQ Y9J/r59/YwnFg6dryOfj4NEmLDZuNTzY1Mfgb2ClsbXljtlhrFTIq8Gk6/hPxQMS7pGG 6MNlGYZ+i2nwMkNbvsVz9w8VaSzcIiJX+jNcPJFNa9pUB1yYQQDKYf+g7qyZ7On4mNpx RVZhGlJA5CSOsJa1J5olDQQbavVNjt80b5nXYmMaU+P+g98I3UToPwb4DYEH6jSwpmCM L2vYg5f0MqS/TFz7PWBQ7V0/lWgPYMKAlel3a4xDoSSY7Aa5ji9khlJVL+QPywHAFiHt KymA== X-Received: by 10.69.3.228 with SMTP id bz4mr63368714pbd.79.1442429563053; Wed, 16 Sep 2015 11:52:43 -0700 (PDT) MIME-Version: 1.0 References: <55F9B856.8080401@cloudera.com> In-Reply-To: <55F9B856.8080401@cloudera.com> From: Luis Villa Date: Wed, 16 Sep 2015 18:52:33 +0000 Message-ID: Subject: Re: LEGAL-224: Are Doxygen config files GPL? To: legal-discuss@apache.org Content-Type: multipart/alternative; boundary=047d7b5d4b9eb82c9a051fe1cd35 --047d7b5d4b9eb82c9a051fe1cd35 Content-Type: text/plain; charset=UTF-8 I might suggest that in this case the best solution is to contact the author and ask them to relicense the file or otherwise grant explicit blessing. I seem to recall doxygen has been pretty reasonable about this stuff in the (admittedly distant) past. Luis On Wed, Sep 16, 2015 at 11:43 AM Ryan Blue wrote: > Hi everyone, > > I opened an issue, LEGAL-224 [1], but I wanted to raise the question > here also. Avro currently contains Doxygen config files, like many other > projects. Those are generated by Doxygen and then updated for the > project. The problem, however, is that they are based on a GPL source > file [2]. > > Doxygen states that "Documents produced by Doxygen are derivative works > derived from the input used in their production; they are not affected > by this license". But, the input file used to derive the output in this > case is a GPL-licensed file in Doxygen itself, not a source file from > the project. > > Can we ship a source release with these files? Should we recreate the > files from scratch? > > I don't think it is the intent of the Doxygen license for this file to > be GPL, but it appears to me that it is anyway. Should we ask for the > license to be updated with an exclusion for the configuration files? > > rb > > [1]: https://issues.apache.org/jira/browse/LEGAL-224 > [2]: https://github.com/doxygen/doxygen/blob/master/src/config.xml > > -- > Ryan Blue > Software Engineer > Cloudera, Inc. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org > For additional commands, e-mail: legal-discuss-help@apache.org > > --047d7b5d4b9eb82c9a051fe1cd35 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I might suggest that in this case the best solution i= s to contact the author and ask them to relicense the file or otherwise gra= nt explicit blessing. I seem to recall doxygen has been pretty reasonable a= bout this stuff in the (admittedly distant) past.

Luis

On Wed, Sep 16, 2015 at 1= 1:43 AM Ryan Blue <blue@cloudera.co= m> wrote:
Hi everyone,

I opened an issue, LEGAL-224 [1], but I wanted to raise the question
here also. Avro currently contains Doxygen config files, like many other projects. Those are generated by Doxygen and then updated for the
project. The problem, however, is that they are based on a GPL source
file [2].

Doxygen states that "Documents produced by Doxygen are derivative work= s
derived from the input used in their production; they are not affected
by this license". But, the input file used to derive the output in thi= s
case is a GPL-licensed file in Doxygen itself, not a source file from
the project.

Can we ship a source release with these files? Should we recreate the
files from scratch?

I don't think it is the intent of the Doxygen license for this file to<= br> be GPL, but it appears to me that it is anyway. Should we ask for the
license to be updated with an exclusion for the configuration files?

rb

[1]: https://issues.apache.org/jira/browse/LEGAL-224<= /a>
[2]:
https://github.com/doxygen/doxygen= /blob/master/src/config.xml

--
Ryan Blue
Software Engineer
Cloudera, Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

--047d7b5d4b9eb82c9a051fe1cd35--