bomber wrote:So I've completed this flight model, I hand it over and I'm told it has to be GPL..... my reply is which part of my work is derived from the existing fdm, not even the file name is the same ?
Non of it is...and as such no one can demand which licence I choose for my copyrighted work..... all rights reserved to the author... ie me.
They might say, we're not linking to it in the - set file as it's not GPL and that's their right to have rules which say their repository uses only 100% GPL content.... but it's my right to do just that with an alternative version using files derived from the original (which remain GPL) and my fdm.
It's not illegal or immoral.... it's just a mixed licenced plane..
And if a person wants to take it and sell it, they can't unless they remove my CC content.
Hi Simon
1.
You are correct.
You can license the FDM you have written as Creative Commons, (or GPL, or any other license of your choice)
So that solves problem #1. Can you license differently than GPL. Yes. You definitely can.
2 . You are not legally allowed to take the FGADDon Beagle, or the FGMEMBERS (GPL) Beagle, and modify it such as it now contains your CC FDM, and it flies better. And it is a mixed license.
Why? (Copyleft clauses prevents you too).
So, basically you can
2.a. Release the FDM for the beagle as an addon. Do not include any content previously licensed as GPL by R. Senior, but offer the FDM in a way that a user can copy it on the Beagle, and get it installed. Your content being only yours, and CC, Richard's content being only his and being GPL. So, an addon without his content allows you to have full copyright ownership, and the ability to license it as you may want/need.
Such FDM (even stand alone) we can place in FGMEMBERS-NONGPL
2.b. Get on a negotiation table with Richard Senior (Sanhozay) about the licenses.
2.b.1: Richard could agree to have a mixed license. He could, per example keep his GPL FDM, in FGADDon and FGMEMBERS; and the plane with both FDMs the GPL and the CC bundled together in an additional Beagle release, more complete and with content from both of you. Such plane can be hosted in FGMEMBERS-NONGPL, and there is nothing preventing you two to reach such agreement. Except R. Senior wanting to maintain his work purely GPL, which he could.
So basically, all authors (both you and he), could agree upon re-releasing additional versions of the Beagle on more complex licenses, and this is perfectly acceptable.
The fact that FGADDon only distributes GPL content clarifies which of the beagles will go there.
But FGMEMBER offers the distribution of GPL only content (FGMEMBERS) and planes with other licenses or mixed licenses (FGMEMBERS-NONGPL)
***
Bottom line, if you want to license the FDM as CC, I advise you
1. do it, and add the license note promptly
2. Talk to R. Senior directly and ask him if he would be ok with re-releasing an alternative Beagle version carrying your FDM (or both FDM), in this case with mixed CC/GPL licenses. If you both agree, then nothing prevents such situation. This is the time to go ahead for bundling contents.
3. If he does not agree, and he says all derivatives of his work must be GPL under copyleft provisions, (this is he does not agree on re-release with new licenses) then you can create your content as an addon. But you couldnt have his content on yours. That is; you cannot bundle and distribute (a.k.a. release)
I think, as far as I understand, this is where it boils down.
Best,
IH-COL