<div dir="ltr"><div>Hi Ben,<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 13, 2020 at 8:50 AM Ben Cotton <<a href="mailto:bcotton@funnelfiasco.com">bcotton@funnelfiasco.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">
<br>
I apologize if I've missed this in previous discussion, but wouldn't<br>
it make sense to bake that protection into the license, similar to<br>
what copyleft-next does:<br>
<a href="https://github.com/copyleft-next/copyleft-next/blob/master/Drafts/copyleft-next#L100-L108" rel="noreferrer" target="_blank">https://github.com/copyleft-next/copyleft-next/blob/master/Drafts/copyleft-next#L100-L108</a><br></blockquote><div><br></div><div>The elements of copyleft-next that you are referring to are fascinating - and it is through this process that I became aware of them. I have still not fully considered all of their ramifications, however, and I don't think it is a good idea to introduce changes to the CAL at this stage.</div><div><br></div><div>Thanks,<br>Van</div><div><br></div><div> </div></div></div>