From: Ray Cote <rgacote@...>
Date: 2003-07-09T20:52:34+09:00
Subject: Re: My brief and torrid affair with Ruby.

--============_-1154370945==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I appreciate all the comments I've received on my earlier email.
Also nice to see the complete lack of flaming. What a nice list!

>The problem with the term *virus* is that it implies malevolence: Jim Cain
I will remove the term 'viral' from my vocabulary in regards to the GPL.
Was not meant in a derogatory way.
Was meant simply that a GPL component used within your own program 
spreads that GPL license to your own code.
This happens with your permission because you decide to use the GPL 
component in the first place. Therefore, there are no 'surprises' 
here. It is pretty clear by using a GPL (not LGPL) component you are 
agreeing to GPL the rest of your code as well.

Jim Cain and Stephyn Butcher pointed out that the GPL applies to code 
that is linked to or interprets GPL-licensed modules. Perl and Java 
modules in particular are referenced as examples.

>..the tradition of Perl modules...same license as interpreter is 
>just that: a tradition. Tim Hammerquist
Agreed. However, I believe the vast majority of modules are released 
with a license that is friendly to the commercial and proprietary use 
of the code.

After posting my email, I discovered that one of the ruby modules 
installed by rubyinstaller.sourceforge.net had been updated by the 
author who had changed the license from GPL to BSD. According to the 
web site, "This is the BSD license which is less restrictive than 
GNU's GPL (General Public License)."  Thank you Michael Neumann.

I would like to conclude by getting back to my original reason for 
posting and that was the recent "How to make Ruby more popular" 
thread.

In my opinion, one way to ensure the growing popularity of Ruby is to 
promote the tradition of releasing Ruby modules under licenses 
friendly to commercial and proprietary use.

Thanks again for all the thoughtful comments.

Let's now return to our regularly-scheduled coding.
--Ray

-- 
--============_-1154370945==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: My brief and torrid affair with
Ruby.</title></head><body>
<div>I appreciate all the comments I've received on my earlier
email.</div>
<div>Also nice to see the complete lack of flaming. What a nice
list!</div>
<div><br></div>
<blockquote type="cite" cite>The problem with the term *virus* is that
it implies malevolence: Jim Cain</blockquote>
<div>I will remove the term 'viral' from my vocabulary in regards to
the GPL.</div>
<div>Was not meant in a derogatory way.</div>
<div>Was meant simply that a GPL component used within your own
program spreads that GPL license to your own code.</div>
<div>This happens with your permission because you decide to use the
GPL component in the first place. Therefore, there are no 'surprises'
here. It is pretty clear by using a GPL (not LGPL) component you are
agreeing to GPL the rest of your code as well.</div>
<div><br></div>
<div>Jim Cain and Stephyn Butcher pointed out that the GPL applies to
code that is linked to or interprets GPL-licensed modules. Perl and
Java modules in particular are referenced as examples.</div>
<div><br></div>
<blockquote type="cite" cite>..the tradition of Perl modules...same
license as interpreter is just that: a tradition. Tim
Hammerquist</blockquote>
<div>Agreed. However, I believe the vast majority of modules are
released with a license that is friendly to the commercial and
proprietary use of the code.</div>
<div><br></div>
<div>After posting my email, I discovered that one of the ruby modules
installed by rubyinstaller.sourceforge.net had been updated by the
author who had changed the license from GPL to BSD. According to the
web site, &quot;This is the BSD license which is less restrictive than
GNU's GPL (General Public License).&quot;&nbsp; Thank you Michael
Neumann.</div>
<div><br></div>
<div>I would like to conclude by getting back to my original reason
for posting and that was the recent &quot;How to make Ruby more
popular&quot; thread.</div>
<div><br></div>
<div>In my opinion, one way to ensure the growing popularity of Ruby
is to promote the tradition of releasing Ruby modules under licenses
friendly to commercial and proprietary use.</div>
<div><br></div>
<div>Thanks again for all the thoughtful comments.</div>
<div><br></div>
<div>Let's now return to our regularly-scheduled coding.</div>
<div>--Ray</div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
</body>
</html>
--============_-1154370945==_ma============--