jakarta-bcel-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Morgan <pmor...@jcoverage.com>
Subject Re: jcoverage/gpl
Date Thu, 29 May 2003 20:41:36 GMT
[I didn't mean to hijack this list for a licensing discussion. Sorry]


On Thu, 2003-05-29 at 21:16, David Hovemeyer wrote:
> On Thu, May 29, 2003 at 08:49:47PM +0100, Peter Morgan wrote:
> > As the copyright holder we specifically make exceptions to the GPL where
> > the instrumented application is either licensed under the GPL or
> > licensed under an OSI license. Our licensing policy is described here:
> > http://jcoverage.com/license.html.
> 
> According to the GPL:
> 
>   "The act of running the Program is not restricted"
>    (item 0 in "Terms and Conditions")
> 
>   "You may not impose any further restrictions on the recipients'
>    exercise of the rights granted herein."
>    (item 6 in "Terms and Conditions")
> 
> Therefore, it seems to me that you cannot license your application
> under the GPL *and* impose restrictions on the use of your program.
> 
> > The principle reason for choosing the GPL is for revenue protection.
> > While we are happy for any OSI licensed application to be instrumented
> > with jcoverage, we do not want commercial licensed applications to be
> > instrumented without having purchased the commercially licensed version
> > of jcoverage.
> 
> I don't think the GPL will allow you to do this.  You should probably
> write your own license.

The model that we are basically trying to follow is that of MySQL. Could
you please explain why
http://www.mysql.com/products/licensing.html is any different to our
model.

Thanks,
Peter.

-- 
Peter Morgan
jcoverage ltd
+44 1423 526 426


---------------------------------------------------------------------
To unsubscribe, e-mail: bcel-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bcel-user-help@jakarta.apache.org


Mime
View raw message