<div dir="auto">Henrik,<div dir="auto"><br></div><div dir="auto">Sure, you can't pull arbitrary stuff off of the internet without intellectual property complications. But the entire point of the Open Source brand is that it is SAFE to use from an intellectual property perspective, and with proper attention to your obligations, safe to modify, share, and redistribute.</div><div dir="auto"><br></div><div dir="auto">Open Source is not random code from the net with intellectual property submarines that attack the naive user. And that should remain the case.</div><div dir="auto"><br></div><div dir="auto">Thanks</div><div dir="auto"><br></div><div dir="auto">Bruce</div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 24, 2019, 8:49 AM Henrik Ingo <<a href="mailto:henrik.ingo@avoinelama.fi">henrik.ingo@avoinelama.fi</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Pam<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 23, 2019 at 2:10 AM Pamela Chestek <<a href="mailto:pamela@chesteklegal.com" target="_blank" rel="noreferrer">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">
<div bgcolor="#FFFFFF">
As a complete duffer in software, this provision is troublesome to
me. It goes well beyond offering a service. This is the same example
I used on the last review of this license, so forgive me for
repeating it. Suppose I put up my homemade website and want a widget
that displays my Twitter feed. I look at my options among the
various addons and extensions and pick one that looks like it's just
the ticket. Woe is me if I picked one under the CAL. Having the
widget on my website is not a private use and so I have to make the
source code available, plus provide notices and attribution on my
website for the widget. I suspect anyone would be surprised that
they had incurred such a burden.<br>
<br>
Still speaking entirely personally.<br>
<br></div></blockquote><div><br></div><div>It's already been pointed out that the exact same questions arise with the AGPL license. But I wanted to point out that your hypothetical really highlights how it's simply not a realistic goal to say that a user must be able to safely copy code from the internet without understanding licensing. That is not the case for software in general, nor open source. A lot of code on github is not under any open source license anyway, so just cavalierly copying some widget code to your website is a bad idea. And that's why at least in my university CS education we were trained not to do that.</div><div><br></div><div>That said, OSI should not approve licenses with unexpected or hazardous requirements on users. I should not be obligated to water your plants, for example.<br></div><div><br></div><div>(If your widget is client side JavaScript then also GPL and LGPL will require you to provide source.)<br></div><div><br></div><div> henrik</div></div>-- <br><div dir="ltr" class="m_3301381815731050859gmail_signature"><a href="mailto:henrik.ingo@avoinelama.fi" target="_blank" rel="noreferrer">henrik.ingo@avoinelama.fi</a><br>+358-40-5697354 skype: henrik.ingo irc: hingo<br><a href="http://www.openlife.cc" target="_blank" rel="noreferrer">www.openlife.cc</a><br><br>My LinkedIn profile: <a href="http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7" target="_blank" rel="noreferrer">http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7</a></div></div>
_______________________________________________<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank" rel="noreferrer">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
</blockquote></div>