We had the same issue last year when we audited Avro's license documentation. This is tracked at LEGAL-224 [1] and we did reach out to doxygen [2]. The doxygen developer, Dimitri clarified that he doesn't intend for the doxy config files to be GPL, but hasn't clarified the license to my knowledge. In the end, we created a new config file with all of the non-default settings and none of the nice descriptions you get with the generated file.
rb [1]: https://issues.apache.org/jira/browse/LEGAL-224 [2]: https://bugzilla.gnome.org/show_bug.cgi?id=755135 On Mon, Sep 12, 2016 at 10:52 AM, Todd Lipcon <[email protected]> wrote: > Maybe it's worth reaching out to the doxygen authors and ask them to add a > header on that file saying that the prose in the documentation may be > licensed under a different more permissive license? (e.g MIT/BSD?) > > -Todd > > On Mon, Sep 12, 2016 at 9:38 AM, Jim Apple <[email protected]> wrote: > >> Apache Impala (incubating) includes a file that includes substantial >> portions containing prose that is only licensed, as far as I can tell, in >> a >> GPL way: >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.g >> it;a=blob;f=be/.impala.doxy;h=4b81af4bab3c04ab60f84e29b70790 >> 26e9959bf2;hb=fcb5c6821d1a0b2d49212dd791c4556dd5ac6c9e >> >> https://github.com/doxygen/doxygen/blob/b38efd15eb69b2b61e05 >> ee09fc9ed6474cc8b1da/src/config.xml >> >> Can we keep that config file in our project as-is, or do we need to remove >> the prose, or perhaps some third thing? >> >> Thanks for your help, >> Jim >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera > -- Ryan Blue Software Engineer Netflix
