On Wed, Mar 17, 2010 at 1:21 AM, Rob Oates <carrotr...@gmail.com> wrote:
> Hmm ... the planes in Flightgear are just models, they don't require
> simgear and terragear to function. Furthermore I would find it extremely
> bizarre for an airplane model to be a dependency in order for Flightgear to
> work.
>
> I'm not worried about introducing our own violations of the GPL by putting
planes under a second license. I strongly believe that modelers should use
whatever license they want. There may be issues with calling GPL'ed Nasal
code, borrowing, etc., but that's beside the point. I have been making
contributions to Flightgear for the last 3 years in the belief that it will
remain under the GPL. The GPL assures me that future users of the code will
want to share their contributions as well. This rewards my time spent by
encouraging a growing community and code base. If Flightgear starts
retreating from the GPL out of misplaced worries about mooching, I'd have to
reexamine how I spend my hacking time.
I know that every developer and modeler sees this differently. One could
point out that most of my contributions are to SimGear, which is under the
weaker LGPL. Whatever; for all practical purposes it's tied closely to the
GPL'ed FlightGear. I view the "mooching" with the attitude of "there's no
such thing as bad publicity."
I think it's reasonable to say there should be a clear separation between
> content and code. Clearly you folks are bothered by the this Pro-sim guy's
> constant mooching ... but the license allows him to do what he does. I have
> no qualms about him distributing the core flightgear simulation program in
> another form (hey let him be responsible for his own support), but I do
> think it's unethical for people to make money off of our highly detailed
> models and our artwork.
>
> Pro-sim is no more than an annoyance. The whole thing is quite pathetic,
especially http://www.flightsimgamereviews.com/. I assure you that that is a
stock image in the header :)
Our models and our code should be seen as two separate entities, that is all
> that I'm suggesting.
>
I'm having trouble seeing the difference between "highly detailed models and
artwork" and significant code contributions in terms of the ethics of making
money off them.
Tim
>
> Thanks,
>
> -Rob
>
>
> On Tue, Mar 16, 2010 at 7:24 PM, Tim Moore <timoor...@gmail.com> wrote:
>
>>
>>
>> On Wed, Mar 17, 2010 at 12:18 AM, Rob Oates <carrotr...@gmail.com> 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....
>>>
>>> I'm not so keen on mixing my GPled code contributions with non-GPLed
>> content.
>>
>> Tim
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
------------------------------------------------------------------------------
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
