On Thu, Jul 5, 2012 at 10:36 AM, Stefan Seifert wrote:
> On Thursday 05 July 2012 07:50:20 Michael wrote:
>
> > Everything on GPL only means:
> > - less scenery and airplanes included ( wasn't there recently some
> > photoscenery rejected because of the GPL?)
>
> There are already 565 airplanes to choose from in git (all licensed GPL).
> More
> than enough for me, if you ask.
>
> > - authors lose copyrights
>
> You obviously don't know anything about copyright law.
>
> > - only to find their work rebranded and sold for ex. as flightprosim etc.
>
> So instead, you want to have countless unusable models because their
> authors
> lost interest and they are no more compatible with the current FlightGear
> version and nobody being able to fix this because the license doens't
> permit?
>
> How exactly would this be better than having 565 airplanes already with
> more
> coming all the time?
>
> > Having only the code on GPL and everything else as freeware...seems less
> > narrow minded to me.
>
> All advanced airplane models contain code (Nasal). So you're arguing for
> using
> GPL for models as well. Ok.
We !!!STRONGLY!!! encourage authors to use the GPL so that we can
incorporate their work into the overall project and distribute the work
from the flightgear.org web site. We believe this gives an author's work
the maximum exposure and benefits the most users. (And this isn't so much
due to the intrinsic nature of the GPL, but because of the consistency of
everything licensed the same way and being inter-compatible from a copying
and redistribution perspective.) The content authors also get a big
benefit because they can incorporate or copy any other GPL components
(cockpit instruments, effects, nasal code, textures/graphics, etc.) into
their own work without having to worry about violating other people's
license terms. We believe and embrace the open-source development model as
a good way to bring the most value to the most people.
I think the reality is that if content author's are 100% honest, we'd find
that a lot of the people here that are arguing for a more
restrictive/protective license probably haven't created a full 100% of the
content they are concerned about restricting/protecting.
The beautiful (and sometimes painful) truth of the GPL is that it tends to
force everyone to extend the same rights and privileges they received to
everyone else down stream. This is freedom. We can't always prevent
mean/evil people from doing unethical or immoral things. But we can try
really hard to protect our own freedom to do positive and constructive
things and not let the mean/evil people take that away from us -- in order
to have "freedom", we have to accept a certain degree of "evil" -- "ye
cannot change the laws of physics." :-)
But after having said all this, don't forget that an author's "original"
work is their own to do with as they please. They can pick which ever
license they want. They can distribute their work to different
destinations under different licenses. The GPL only applies if you have
included other GPL work into your own content and only if you then wish to
distribute (or give/sell copies) of your work to others. The GPL is
unconcerned with what you do for your own private use.
Disclaimer #1: I have not had my lawyers review the content of this email
for correctness, exactness, and clarity of my interpretation of the GPL.
Disclaimer #2: I do not have any lawyers anyway.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
