The response from JBoss (a RedHat employee who is not a lawyer) is that
the configuration files are not LGPL [1]. I think we're good to remove
it from NOTICE, unless any more comments?
IANAL
Haha, so this would essentially mean that everyone who starts with
standalone.xml file and reconfigures it would have to make it
available to the public since he made modifications?
That's certainly not the case and not the point of licensing, as far
as I understand it, LGPL doesn't cover configuration files (this is
probably made clear by the 0th section talking about definitions).
Aled
[1] https://developer.jboss.org/message/909912
On 11/11/2014 23:30, Aled Sage wrote:
The file did start life as a copy of the default config file within
the JBoss AS 7 install artifact. We then modified it. We would have
reached pretty much the same final config file if we had approached it
by taking the examples / code snippets from docs + blogs.
For MariaDB, I believe it was more written from doc snippets. It's a
much smaller file that doesn't closely match the my.cnf in the default
install.
Aled
On 11/11/2014 22:58, Joe Brockmeier wrote:
On 11/11/2014 04:47 PM, Aled Sage wrote:
Having reviewed those config files and the MariaDB / JBoss docs, I
believe there is a strong case for this being config that just matches
snippets from the docs, and examples that are readily available on a
myriad of blogs. Our template config files are similar to the default
files, but unsurprisingly the defaults match docs and thus match what
one would write for a basic deployment.
I therefore conclude that our version of the files are not (L)GPL
licensed, and that we should remove them from the NOTICE file.
*Mentors:* any comments?
Sorry - are your files taken from the templates and slightly modified,
or are they config files that simply happen to have similar sections to
the defaults / documentation examples?
We went through all these things with a fine-toothed comb for Apache
CloudStack - possibly with even more caution than absolutely necessary -
and we did wind up contacting several upstream maintainers to get a
sign-off on their config files not being licensed under LGPL/GPL, etc.
Best,
jzb
