<div>Neil, </div><div><br></div><div>It's not rocket science. Try to work with one, or the other, but not both.</div><div><br></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>OpenSIM core can't include GPL'd code into the </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>> BSD licensed core</i></b></span></div><div><br></div><div>That's the gist of it all.</div>
<div><br></div><div>If you're going to do any viewer work, then maybe look at Naali. It's a BSD-licensed viewer, and you can work on both the viewer and server without any fear.</div><div><br></div><div><a href="http://wiki.realxtend.org/index.php/Getting_Started_with_Naali">http://wiki.realxtend.org/index.php/Getting_Started_with_Naali</a></div>
<div><br></div><div><span class="Apple-style-span" style="font-family: sans-serif; line-height: 19px; "><b><i>> Maybe that needs to be broadened and the reasons added?</i></b></span></div><div><br></div><div>We're not legal counsel. </div>
<div><br></div><a href="http://opendevice.blogspot.com/2007/06/best-gnu-gpl-vs-bsd-comparison-ever.html">http://opendevice.blogspot.com/2007/06/best-gnu-gpl-vs-bsd-comparison-ever.html</a><div><br></div><div>BSD license retains the freedom to incorporate the code into proprietary products (without making the products open source), and that's a freedom which the GPL does not allow.</div>
<div><br></div><div><a href="http://slashdot.org/articles/99/06/23/1313224.shtml">http://slashdot.org/articles/99/06/23/1313224.shtml</a></div><div><br></div><div>You can't sell GPL'd software. You can charge for distribution, support, or documentation, but can't charge for the software itself. BSD license allows developers much more flexibility in how they plan on using the software (commercial, non-commercial, etc.)</div>
<div><br></div><div><a href="http://opendevice.blogspot.com/2007/06/best-gnu-gpl-vs-bsd-comparison-ever.html"></a><a href="http://www.freebsd.org/doc/en/articles/bsdl-gpl/article.html">http://www.freebsd.org/doc/en/articles/bsdl-gpl/article.html</a><br>
<br></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; font-size: medium; line-height: 19px; "><p><i>The BSD license places minimal restrictions on future behavior. This allows BSD code to remain Open Source or become integrated into commercial solutions, as a project's or company's needs change. In other words, the BSD license does not become a legal time-bomb at any point in the development process.</i></p>
<p><i>In addition, since the BSD license does not come with the legal complexity of the GPL or LGPL licenses, it allows developers and companies to spend their time creating and promoting good code rather than worrying if that code violates licensing.</i></p>
</span></div><div>Read this:</div><div><br></div><div><a href="http://en.wikipedia.org/wiki/GNU_General_Public_License">http://en.wikipedia.org/wiki/GNU_General_Public_License</a></div><div><br></div><div>As a developer, you should KNOW whether you are copying someone else's work. Just don't do it.</div>
<div><br></div><div>As far as keeping things "simple", that is why we try to draw a line in the sand, and say that OS core server developers (BSD license) should avoid looking at any LL viewer code.</div><div><br>
</div><div>If you're going to be working with LL viewer code, then you can write your own modules, but just stay away from core. If you want to work on BOTH core and viewer, then work on Naali. Naali has been written from the ground up, with a BSD license to overcome all the problems various groups were facing/having when it comes to licensing issues.</div>
<div><br></div><div>So if you really want to work on both a viewer and server, then just work on Naali.</div><div><br></div><div><a href="http://wiki.realxtend.org/index.php/Getting_Started_with_Naali">http://wiki.realxtend.org/index.php/Getting_Started_with_Naali</a></div>
<div><br></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>If I misread I apologize, again its why I asked for </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>> clarification. </i></b></span></div><div><b><i><br></i></b></div>
<div>No problem.</div><div><b><i><br></i></b></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>Thanks for the reference.</i></b></span></div>
<div><br></div><div>No problem. If you're going to develop, just be responsible. Please understand that Diva (and all the core dev's) are simply just protecting the project from any "tainting". We can't offer you any legal advice, but that's why it's quite common for the dev's to ask that you work on one or the other (but not both). </div>
<div><br></div><div>The best solution is to just work on the Naali viewer. If you want to work on both a viewer, and the server core, then look at Naali. They're both BSD-license based, and it solves any problems with licensing "issues".</div>
<div><br></div><div>If you're going to write your own modules, then you may do as you wish (because you'll be responsible for what you do on your own). </div><div><br></div><div><b><i>> </i></b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>I asked for clarification because honestly I'd like </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>> to be able to contribute and can't with the current </i></b></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><b><i>> restrictions. It is what it is. </i></b></span></div><div><br>
</div><div>It "is what it is" for a reason. </div><div><br></div><div><b>> </b><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><i><b>I'd like </b></i></span><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><i><b>to be able to contribute and can't with the current </b></i></span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 15px; border-collapse: collapse; color: rgb(31, 73, 125); "><i><b>> restrictions. </b></i></span></div><div><br></div><div>The core dev's are simply just protecting the project (from a legal standpoint), and that's the problem we face with two incompatible licenses (GPL vs BSD). So if you want to work on both a viewer and the server, then it would be best to begin looking at the Naali Viewer (BSD license based). You can work on both the server and Naali viewer code (both are BSD licensed) without any fear of "contaminating" either project.</div>
<div><br></div><div><br></div><div><div class="gmail_quote">On Wed, Jun 30, 2010 at 10:29 AM, Neil Canham <span dir="ltr"><<a href="mailto:neil@knowsense.co.uk">neil@knowsense.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
OK, suitably chastened, I've read the wiki now :-) The closest it comes to what seems to be the consensus here is:<div><br></div><div><span style="font-family:sans-serif;font-size:13px;line-height:19px">"You have not studied source code from the GPL Second Life viewer or its derivatives within the last 6 months."</span></div>
<div><font face="sans-serif"><span style="line-height:19px"><br></span></font></div><div><font face="sans-serif"><span style="line-height:19px">Maybe that needs to be broadened and the reasons added? I'm happy to do it but given that I'm getting everything from you guys it might suffer for being second hand.</span></font></div>
<div><font face="sans-serif"><span style="line-height:19px"><br></span></font></div><font color="#888888"><div><font face="sans-serif"><span style="line-height:19px">Neil<br>
</span></font><br><div class="gmail_quote"><br></div>
</div>
</font><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>