Re: [Flightgear-devel] Copyrights

2010-01-08 Thread Arnt Karlsen
On Fri, 08 Jan 2010 09:41:15 +0100, Erik wrote in message <4b46efab.4020...@ehofman.com>: > J. Holden wrote: > > LeeE: > > > > I appreciate your comments, but in that case, why is FlightGear > > licensed under the GPL at all if we're not willing to enforce it? ..you don't enforce the GPL like d

Re: [Flightgear-devel] Copyrights

2010-01-08 Thread Erik Hofman
J. Holden wrote: > LeeE: > > I appreciate your comments, but in that case, why is FlightGear licensed > under the GPL at all if we're not willing to enforce it? The GPL is designed > to be as open as possible, but still giving rights to the people who hold the > copyright on the product! Well

Re: [Flightgear-devel] Copyrights

2010-01-08 Thread J. Holden
LeeE: I appreciate your comments, but in that case, why is FlightGear licensed under the GPL at all if we're not willing to enforce it? The GPL is designed to be as open as possible, but still giving rights to the people who hold the copyright on the product! See section 1 of GPLv2: "1. You

Re: [Flightgear-devel] Copyrights

2010-01-07 Thread leee
On Wednesday 06 Jan 2010, J. Holden wrote: > With regards to what has been said, the GPLv2 gives the end user > the right to both modify the software and, if certain conditions > are met, distribute the software. It does NOT change the fact > that all the contributors actually own the copyright on

Re: [Flightgear-devel] Copyrights

2010-01-06 Thread J. Holden
With regards to what has been said, the GPLv2 gives the end user the right to both modify the software and, if certain conditions are met, distribute the software. It does NOT change the fact that all the contributors actually own the copyright on the software, or it appears in FlightGears' case

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread Bob Faulkner
> Date: Mon, 4 Jan 2010 16:10:33 -0800 (PST) > From: "J. Holden" > This software (C) 2001-2010 FlightGear > Licensed under the GPLv2. > Cheers > John >leee wrote: > > John, in referring to "our" software, I'm afraid that you're missing > > the point of the GPL. Once the software has been releas

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread leee
On Tuesday 05 Jan 2010, Martin Spott wrote: > leee wrote: > > John, in referring to "our" software, I'm afraid that you're > > missing the point of the GPL. Once the software has been > > released under the GPL it isn't 'ours' or anyone else's > > anymore; it is owned by no one. > > Incorrect, the

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread Stefan Seifert
On Tuesday 05 January 2010 01:10:33 J. Holden wrote: > unless the contributors agree to assign their copyright to an entity > (FlightGear). And who would this "FlightGear" be? Stefan -- This SF.Net email is sponsored by

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread Martin Spott
leee wrote: > John, in referring to "our" software, I'm afraid that you're missing > the point of the GPL. Once the software has been released under > the GPL it isn't 'ours' or anyone else's anymore; it is owned by no > one. Incorrect, the author is still holding the Copyright, as long as he

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread leee
On Tuesday 05 Jan 2010, J. Holden wrote: [snip...] > ...but this is important to help protect our software. > > Cheers > John John, in referring to "our" software, I'm afraid that you're missing the point of the GPL. Once the software has been released under the GPL it isn't 'ours' or anyone el

Re: [Flightgear-devel] Copyrights

2010-01-05 Thread Erik Hofman
J. Holden wrote: > I've been doing research into copyrights and am shocked to see there is no > (C) (years)-2010 FlightGear anywhere in FGRun or in the main flight > simulation program. Copyrights don't vanish at the beginning of a new year. They start at a given date and expire many years late

[Flightgear-devel] Copyrights

2010-01-04 Thread J. Holden
I've been doing research into copyrights and am shocked to see there is no (C) (years)-2010 FlightGear anywhere in FGRun or in the main flight simulation program. However, it appears looking through a sample of the source code the code is indeed (C) (year) by the authors who wrote it. This mak