[Kea-users] License and

[Ilya Kruglik]

Hi Marcin,


Thanks for the clarification. I should have find read it myself perhaps.


Apologize for not being clear from the beginning, but I'm afraid that we might fall under the "distribution" restriction in what you quoted below. The thing is that our usage of the Kea DHCP is not to be a DHCP server per se inside organisation, but rather be a part of our product/solution. it might mean that we are going to distribute it to our customers since dhcp server is a part of our system.


With all that said, am I interpreting it correctly that our use case can violate MPL and we cannot do local modifications to the code?

Are build system files treated as source code in this scenario even if modifications done only to get it built? What is actually considered as "source code" - any file in the tarball/repo? I'm not really good in that legal questions.


Thanks,

 Ilya.

________________________________
From: Marcin Siodelski <marcin at isc.org>
Sent: Thursday, October 20, 2016 2:43:31 PM
To: Ilya Kruglik; kea-users at lists.isc.org
Subject: Re: [Kea-users] License and

Hello Ilya,

No. It doesn't violate the license. Please see the following:

https://www.mozilla.org/en-US/MPL/2.0/FAQ/

Specifically:

"The MPL only creates obligations for you if you want to distribute the
software outside your organization."

Marcin Siodelski
ISC

On 20.10.2016 09:35, Ilya Kruglik wrote:
> Hello,
>
>
> There's a known issue with cross build which even a ticket exists for, e.g.:
>
> http://kea.isc.org/ticket/3745
>
>
> I have a question in this regard: Would it be a license violation if we
> patch automake files (Makefile.am) locally to make it compiled in our
> environment (Poky)?
>
>
> Best regards,
>
>  Ilya.
>
>
>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20161020/6bfec9e6/attachment.htm>