<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I believe that I wrote <i>exactly </i>that. <br>
<pre wrap="">You must make your source code <i><b>available to users</b></i> under the terms of the GPL
which means, <i><b>the users to whom you have distributed binaries. </b></i>If these users are in-house, then you have already done it.<i><b>
</b></i></pre>
JB<br>
<blockquote
cite="mid:45d654b0811050737h6984e3f6xd339451417d9ba91@mail.gmail.com"
type="cite">
<pre wrap="">One comment:
</pre>
<blockquote type="cite">
<pre wrap="">2) You do not have a Qt license and you have modified/derived Qt based code:
You must make your source code available to users under the terms of the GPL
(including ParaView source, which they do anyway).
</pre>
</blockquote>
<pre wrap=""><!---->
The GPL license says that you have to provide the source under GPL to
those you distribute binaries. If you are developing a
plugin/extension for in-house use using GPL'ed Qt, you do _not_ have
to distribute your source to the outside world. Trolltech has never
been clear on this issue. They say that if you are developing
commercial tools, you have to have the commercial license. This is
only true when it comes to distribution. It does not apply to in-house
tools.
-berk
On Wed, Nov 5, 2008 at 8:35 AM, John Biddiscombe <a class="moz-txt-link-rfc2396E" href="mailto:biddisco@cscs.ch"><biddisco@cscs.ch></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">To summarize, within the framework of paraview plugin development
1) You do not modify/derive from or create any Qt based code :
You can distribute your software under your own terms, GPL or other. Users
must have access to the ParaView source, which they do anyway, your software
does not have to be open source.
2) You do not have a Qt license and you have modified/derived Qt based code
:
You must make your source code available to users under the terms of the GPL
(including ParaView source, which they do anyway).
3) You have a Qt license:
You can keep the source code closed and distribute anything (Qt based or
otherwise) you want under your own terms.
4) You may separate plugins which make use of Qt based code from others
which do not, and distribute them on different terms, according to the first
3 statements.
I welcome corrections to the above 4 statements, preferably in as simple a
form as possible.
JB
--
John Biddiscombe, email:biddisco @ cscs.ch
<a class="moz-txt-link-freetext" href="http://www.cscs.ch/">http://www.cscs.ch/</a>
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
_______________________________________________
ParaView mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ParaView@paraview.org">ParaView@paraview.org</a>
<a class="moz-txt-link-freetext" href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a>
</pre>
</blockquote>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="78">--
John Biddiscombe, email:biddisco @ cscs.ch
<a class="moz-txt-link-freetext" href="http://www.cscs.ch/">http://www.cscs.ch/</a>
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82</pre>
</body>
</html>