<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/26/19 5:58 PM, VanL wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFQvZEMkyu2hRhYaK-zdLCbzs+A2h7s6LnJNNDWxamNJL4XmTg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hi Pam,</div>
<div><br>
</div>
<div>Sorry for the late reply.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Dec 24, 2019 at 8:05
AM Pamela Chestek <<a
href="mailto:pamela@chesteklegal.com"
moz-do-not-send="true">pamela@chesteklegal.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
The Holochain website talks about doing things like running
a social <br>
network client. Would that social network software have to
be under an <br>
open source license?<br>
</blockquote>
<div><br>
</div>
<div>This comes down to the licensor's choice. If the licensor
used the CAL without the Combined Works Exception, then this
would have the effect of ensuring that the software stayed
open source - modulo standard copyright rules that would
tend to allow different licenses as the link between the
CAL-licensed framework and other software became more
attenuated.</div>
<div><br>
</div>
<div>In the case of Holochain, Holo intends to use the
Combined Works exception to allow differently-licensed
software "on top" of the CAL-licensed framework. As an
analogy, think of the external vs. internal interfaces split
already used in the Linux kernel.</div>
</div>
</div>
</blockquote>
<p>Isn't it more similar to the outcome if the Linux kernel hadn't
clarified that what is in user space didn't need to be under the
GPL? If the Linux kernel was under the CAL, wouldn't all the
applications that run on it also have to be under open source
licenses, unless the licensor had the Combined Works exception?<br>
</p>
<p>Pam</p>
Pamela S. Chestek <br>
Chestek Legal <br>
PO Box 2492 <br>
Raleigh, NC 27602 <br>
<a class="moz-txt-link-abbreviated" href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a> <br>
919-800-8033 <br>
<a class="moz-txt-link-abbreviated" href="http://www.chesteklegal.com">www.chesteklegal.com</a><br>
<blockquote type="cite"
cite="mid:CAFQvZEMkyu2hRhYaK-zdLCbzs+A2h7s6LnJNNDWxamNJL4XmTg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>Thanks,<br>
</div>
<div>Van<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<br>
</div>
</body>
</html>