Good point, didn't account for that.
On Mar 16, 2010, at 8:05 PM, Adam Dershowitz wrote:
> That only helps make it clear if someone is violating a copyright. It
> doesn't help enforce it. If the license is changed, and then someone were to
> go and sell FG with those aircraft who would hire the lawyer bring the
> copyright violation law suit?
>
> --Adam
>
>
>
> On Mar 16, 2010, at 4:26 PM, kyle keevill wrote:
>
>> Last I heard, The GPL license was applied to all the planes hosted on the FG
>> website. I do believe however, that if we do take our own planes and put
>> them in a restrictive CC license and then give permission for FG and only FG
>> to use them, then we may be able to do some good.
>> On Mar 16, 2010, at 7:18 PM, Rob Oates wrote:
>>
>>> Hmm, why not change the license on some of the newer planes to a more
>>> restrictive creative commons license? This would give you more control over
>>> how these are used. For instance, you could apply the license so the planes
>>> could only be use for non-commercial/free projects, and if a commercial
>>> project wanted to use your planes then they would have to request
>>> permission to use them.
>>>
>>> I think that is a fair trade off. Besides commercial companies should be
>>> trying to improve the underlying Flight Dynamic Model and terrain system
>>> ... not trying to getting rich quick off of our pretty planes.
>>>
>>> The GPL license should apply some probably just a handful of planes.
>>>
>>> my 2 cents....
>>>
>>> -Rob
>>>
>>> On Mon, Mar 15, 2010 at 7:44 PM, Pete Morgan <ac...@daffodil.uk.com> wrote:
>>> Just sent an email to New Zealand open Source and got this reply,
>>> pete
>>>
>>> Hello Peter,
>>>
>>> Thanks for bringing this to our attention. Please recognise that the GPL
>>> does not in any way preclude people from packaging up and selling a
>>> software application *so long as they comply with the terms of the GPL
>>> with regard to making the source code available on request*.
>>>
>>> It may be that these guys are *not* in violation of the GPL so long as
>>> they can provide you with their source code if you request it. If they
>>> can't, then they should be given notice of a GPL violation.
>>>
>>> There is another issue here, however: if they are packaging up wiki
>>> content, aircraft designs, et al. for which *they do not hold copyright*
>>> and which aren't licensed under a Creative Commons license allowing
>>> commercial distribution, then they *are* guilty of copyright
>>> infringement, and you can take them to task on that, *if you are (or
>>> represent) the copyright holder*.
>>>
>>> As a representative of the NZOSS, I would fully encourage you to explore
>>> both issues (the distribution of source code, and the distribution of
>>> copyrighted materials constituting potential copyright infringement)
>>> with the FlightProSim.com people.
>>>
>>> One of our other members has noted that they're similarly distributing
>>> Free!Ship: http://www.3dboatdesign.com/indexg.php
>>> <http://www.3dboatdesign.com/indexg.php>
>>>
>>> We'll investigate that.
>>>
>>> Let me know if you have any further questions.
>>>
>>> Kind regards,
>>>
>>> Dave Lane
>>> NZOSS council member
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Flightgear-devel mailing list
>>> Flightgear-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
>>> Flightgear-devel mailing list
>>> Flightgear-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>
>> ----
>> Kyle Keevill
>> kyle...@gmail.com
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
----
Kyle Keevill
kyle...@gmail.com
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
