<div>Mike,</div><div><br></div><div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); "><i>> Diva, your message as worded sounds to me like you </i></span></div><div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); "><i>> would accept contributions so long as there were no </i></span></div>
<div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); "><i>> GPL licensed code in the submission. </i></span></div><div><br></div><div>Not sure what you read (or misunderstood), or where you would have derived that conclusion from, but from what I just read from Diva's previous post, it seems to be that you're completely wrong in your assumption. Where did you draw that conclusion from? I don't think Diva said ANYTHING like that in her post.</div>
<div><br></div><div>Diva simply stated:</div><div><br></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>Hence, the "no risks" rule. We do not take patches from anyone </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>> who is actively involved in the development of viewers from the </i></b></span></div><div>
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>> LL viewer family.</i></b></span></div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i><div>
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i><br></i></b></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; font-style: normal; font-weight: normal; font-size: small; "><div>
I'm not sure what you "misunderstood" but it seems that Diva is simply just saying/repeating the same exact thing, and the way that it's always been. No contributions from those working on the LL viewer.</div>
<div><br></div></span></i></b></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i><br></i></b></span></div>>If, however, you are talking about your own modules that aren't part </i></b></span><div>
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>>of the official OpenSim distribution, then OpenSim has no say </i></b></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>>about it -- do whatever you want. No one here is in a position to </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>> give legal advice.</i></b></span><div><br></div><div>Diva is strictly referring to OpenSim core, not any individual's personal modules. This is just core. As for a person's individual modules, that is up to the individual. </div>
<div><br></div><div>> <span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); ">Modules external to core of course don't carry any prohibition. </span></div><div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); ">> In doing that I'm simply using API's the project has provided </span></div>
<div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); ">> and how I conform to licenses involved is my business.</span></div><div><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); "><br>
</span></div><div>I believe that is exactly what Diva has said (in her own words). Modules external to core don't carry any prohibition (they are beyond the scope of OS core) and it's up to the individual writing their own personal module to comply with any licensing compatibility "issues", but from what I just read - the stand as far as core is concerned still stays the same.</div>
<div><br></div><div><div>No patches from those involved in the development of viewers from the LL viewer family.</div></div><div><br></div><div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>Hence, the "no risks" rule. We do not take patches from anyone </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>> who is actively involved in the development of viewers from the </i></b></span></div><div>
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i>> LL viewer family.</i></b></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i><br>
</i></b></span></div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><b><i></i></b></span><b><i></i></b><b><i></i></b></div></div><div>Seems pretty clear. I believe it might not hurt to say that "development" would be considered anyone that looks at or reads the LL viewer code. So choose one or the other (viewer development side, or server development side) but we've always tried to draw a line in the sand and keep the two sides divided (just to protect the project from any IP/copying issues). </div>
<div><br></div><div>If you're looking for a BSD compatible viewer, and don't want to deal with any "GPL" issues at all, then look at Naali. You can work on both Naali and OpenSim at the same time, as they are both BSD license based, and you don't have the license compatibility issues that were faced with the old LL-based viewers.</div>
<div><br></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-size: 15px; color: rgb(31, 73, 125); "><b><i>OpenSIM core can't include GPL'd code into the BSD licensed core</i></b></span></div><div>
<br></div><div>There is no GPL'd code in the BSD licensed core. It's the same as it's always been.</div><div><br></div><div><a href="http://opensimulator.org/wiki/Contributions_Policy">http://opensimulator.org/wiki/Contributions_Policy</a></div>
<div><br></div><div><br><div class="gmail_quote">On Wed, Jun 30, 2010 at 8:25 AM, Dickson, Mike (ISS Software) <span dir="ltr"><<a href="mailto:mike.dickson@hp.com">mike.dickson@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Ok, this is a slightly different position than I've heard
before...</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">The issue of simple code inclusion is well defined IMO, OpenSIM
core can't include GPL'd code into the BSD licensed core without running afoul
of the GPL. That's a simple license compatibility issue. But in the
past what I've heard is that you don't want contributions from people who have
read or worked on viewer code because of concerns of copying IP (that is...
knowing something about the client implementation might taint the server code
because I'd use that info when implementing a server change).
Is that not the case? Diva, your message as worded sounds to me like you
would accept contributions so long as there were no GPL licensed code in the
submission. I.E. Your issue is no direct code copying, not intellectual
property related.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Modules external to core of course don't carry any
prohibition. In doing that I'm simply using API's the project has
provided and how I conform to licenses involved is my business.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Mike</span></p>
<p class="MsoNormal"><a name="129890f4fbdd8b51__MailEndCompose"><span style="font-size:11.0pt;color:#1F497D"> </span></a></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt;color:windowtext">From:</span></b><span style="font-size:10.0pt;color:windowtext">
<a href="mailto:opensim-dev-bounces@lists.berlios.de" target="_blank">opensim-dev-bounces@lists.berlios.de</a>
[mailto:<a href="mailto:opensim-dev-bounces@lists.berlios.de" target="_blank">opensim-dev-bounces@lists.berlios.de</a>] <b>On Behalf Of </b>Diva Canto<br>
<b>Sent:</b> Wednesday, June 30, 2010 8:03 AM<br>
<b>To:</b> <a href="mailto:opensim-dev@lists.berlios.de" target="_blank">opensim-dev@lists.berlios.de</a><br>
<b>Subject:</b> Re: [Opensim-dev] GPL / BSD licensing dangers</span></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal" style="margin-left:.5in"> </p>
<p class="MsoNormal" style="margin-left:.5in">The issue here is not BSD+GPL
licenses in general, although that's also an issue to worry about; the issue we
most vocally warn people about is very specific to OpenSim and Second Life.
OpenSim has been made legally possible due to the generosity of Linden Lab's
publishing their protocols by means of some public documentation and, yes, open
sourcing the client [under GPL]. So far, we have had the passive and, at
points, active support of Linden Lab in developing OpenSim. But, as we all
know, Linden Lab is a relatively unpredictable company; at any point, it could
be acquired by another company who is less enthusiastic about a free BSD open
source server side to their client. In the absolute worst case scenario, that
other company could cause us a lot of grief if OpenSim includes code directly
derived from GPL'ed viewer code. (I don't want to start a rhetorical discussion
about this; that's just the worst case scenario, period.)<br>
<br>
Hence, the "no risks" rule. We do not take patches from anyone who is
actively involved in the development of viewers from the LL viewer family.<br>
<br>
If, however, you are talking about your own modules that aren't part of the
official OpenSim distribution, then OpenSim has no say about it -- do whatever
you want. No one here is in a position to give legal advice.<br>
<br>
On 6/30/2010 4:18 AM, Neil Canham wrote: </p>
<p class="MsoNormal" style="margin-left:.5in">Would anyone be able to tell me
about the warning for any one person not to work on both the OpenSim source and
a viewer such as Hippo? I understand that there are licensing differences
(BSD vs GPL respectively) and that direct inclusion of GPL code in a BSD
project breaks the GPL license. Surely you could guard against such
direct inclusion? Does this extend to region modules and mini-region
modules? I'm in the position of wanting to make changes to the viewer and
also to write MRMs or other modules.<br clear="all">
<br>
-- <br>
Neil Canham<br>
-- <br>
<br>
<br>
</p>
<pre style="margin-left:.5in"> </pre><pre style="margin-left:.5in"> </pre><pre style="margin-left:.5in">_______________________________________________</pre><pre style="margin-left:.5in">Opensim-dev mailing list</pre><pre style="margin-left:.5in">
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a></pre><pre style="margin-left:.5in"><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a></pre>
<pre style="margin-left:.5in"> </pre>
<p class="MsoNormal" style="margin-left:.5in"> </p>
</div></div></div>
</div>
<br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br></div>