From: HB-GRAL <fli...@sa...> - 2011-04-05 15:57:13
|
Am 05.04.11 17:00, schrieb TDO_Brandano -: > > This does not supercede the original license, it effectively means a fork under a new licence. The GPL v2 on the original remains in effect, but changes on the GPLv3 versions would be covered by the GPLv3 terms. > Alessandro > Wiki and flightgear.org are linking to GPLv3 (because they link to GPL #undefined), some people might think they have to use the "updated" licence. Gitorious (original repo now, isn’t it?) says: GPLv2. There is also a COPYING file in the repo with GPLv2 text, (and 10 other raw licence texts btw). I do not care about the "or later", because we are talking from the same repo, and I think no one has the right to pull from origin and push it back with licence change. GPLv3 is not just an update of GPLv2, it is another licence, right ? This is from the readme of 767-300, which comes with GPLv3 licence: "Alot of the systems were used from the Flightgear Boeing 777-200ER model, by Syd Adams and Justin Smithies, which is also under the same GNU GPL." True? Main point is that it is GPL of course, but I think people should not pull GPLv2 code from the original repo and push back the same code with another licence version? Anyway, this needs only a small clean up for Mig15, Fokker100, 767-300, PC9-M, A340-600. And people should know, that all the stuff within fgdata is already covered by one licence and that there is no dual licencing and that they don’t have to distribute GPL licence text themself. Maybe I am wrong at all, sorry for the confusion. I am just a small and non-important contributor who wants to do licence things how it has to be done. Cheers, Yves |