[Paraview] legal summary

[Michael Jackson]

You are distributing the code to yourself. Make sure you distribute  
the source code to yourself to be in compliance with GPL.  ;-)

Mike

On Nov 5, 2008, at 10:59 AM, Dominik Szczerba wrote:

> Actually that was never clear to me in GPL in general. If I develop  
> something for in-house use only then there is nobody to give my code  
> to. But the code is potentially employed for commercial purposes  
> (including generation of income) so it IS being used as a commercial  
> tool, only not distributed.
>
> <sigh/>
>
> Dominik
>
> Berk Geveci wrote:
>> One comment:
>>> 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).
>> 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 <biddisco at cscs.ch>  
>> wrote:
>>> 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
>>> http://www.cscs.ch/
>>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91)  
>>> 610.82.07
>>> Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91)  
>>> 610.82.82
>>>
>>>
>
> -- 
> Dominik Szczerba, PhD
> Computational Physics Group
> IT'IS Foundation for Research
> http://www.itis.ethz.ch