<div dir="ltr"><div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default">I read this article a while back. It does seem that GS overstepped their bounds, and did a bit of a "cry wolf" - but the timing of NSA leaks, cybercrime, and all that, and mix in an Eastern European guy uploading something to Germany, and -- well, people are going to overreact.</div>
<div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default"> </div><div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default">The license was not cited, but in my knowledge of OSS, you have different variations. Some are more flexibble than others in requiring anything you "make" using the source to be made available again. </div>
<div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default"> </div><div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default">The gray area becomes the case where you use an Open Source codebase and then create a derivitave proprietary work based upon it, with no intention of ever distributing or releasing that code. It's simply for "your own" use ("your own" here refers to GS)... and that's typically OK, except when the original license forbids such use. Short answer: we can't really know without knowing the package/source programs involved and what their licenses are/were.</div>
<div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default"> </div><div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default">-Angelo</div>
<div style="color:rgb(51,0,51);font-family:verdana,sans-serif;font-size:small" class="gmail_default"> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 28, 2013 at 9:21 AM, tom <span dir="ltr"><<a href="mailto:thomas.w.cranston@gmail.com" target="_blank">thomas.w.cranston@gmail.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="#FFFFFF" text="#000000"><div><div class="h5">
<div>On 10/27/2013 06:25 PM, Jeff Frontz
wrote:<br>
</div>
<blockquote type="cite">
<div>Depending on who owns the software, something like this may
transpire: <span style="line-height:19px;font-family:".HelveticaNeueUI";font-size:15px;white-space:nowrap"><a href="http://en.m.wikipedia.org/wiki/Free_Software_Foundation_v._Cisco_Systems" target="_blank">http://en.m.wikipedia.org/wiki/Free_Software_Foundation_v._Cisco_Systems</a></span></div>
<div><span style="line-height:19px;font-family:".HelveticaNeueUI";font-size:15px;white-space:nowrap"><br>
</span></div>
<div><br>
On Oct 27, 2013, at 18:43, tom <<a href="mailto:thomas.w.cranston@gmail.com" target="_blank">thomas.w.cranston@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Let's assume I take open source code after reading
it's license and </span><br>
<span>agreeing that any changes to it must be released as open
source. I then </span><br>
<span>modify the code, but then tack my own private license to
it. How would I </span><br>
<span>be punished for doing so?</span><br>
<span></span><br>
<span>Tom</span><br>
<span>_______________________________________________</span><br>
<span>colug-432 mailing list</span><br>
<span><a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a></span><br>
<span><a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a></span><br>
</div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
colug-432 mailing list
<a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a>
</pre>
</blockquote></div></div>
What prompted this question was the Vanity Fair article about
charges from Goldman Sachs against Sergey Aleynikov for him stealing
open source code that Goldman Sachs tacked their own ownership onto.<br>
<br>
<a href="http://www.vanityfair.com/business/2013/09/michael-lewis-goldman-sachs-programmer" target="_blank">http://www.vanityfair.com/business/2013/09/michael-lewis-goldman-sachs-programmer</a><br>
<br>
The author did not site which license applied.<br>
<br>
Maybe an injunction could be applied to Goldman Sachs. Who's the
real thief here anyway?<br>
<br>
Please let me know if the VF link does not work.<span class="HOEnZb"><font color="#888888"><br>
<br>
Tom<br>
</font></span></div>
<br>_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
<br></blockquote></div><br></div>