I'm a little late but I just wanted to make some clarifications about what happened with FGMEMBERS and this aircraft. There is a lot of FUD going around.- FGMEMBERS forks the CRJ700 from my Github repository, which had a CC license on my models and textures.
- FGMEMBERS sees that the slightly older copy in FGAddon has a GPL license. This is because I would relicense my models and textures under GPL before pushing to fgdata.
- FGMEMBERS changes the license on their copy to GPL, which is completely illegal because it was derived from my CC version.
- Some months later, FGMEMBERS realizes their "mistake" and reverts the commit that changed the license file. They move their repository to their "NONGPL" section.
Where they went wrong is step three. That change and any changes made after it are illegal. Just because the commit was later un-done doesn't mean it's been fixed.
It's an unfortunate misunderstanding, but it's not permissible, plain and simple, and they could have handled it better. As the author, this isn't cool.
jsb wrote in Sun Sep 13, 2015 11:39 am:Ok, I guess I managed to create and apply a pull to my repo so I have Skyops latest license file now. I deleted all branches but master from my repo (but not from my local PC) so I hope everything is "clean" now.
Unfortunately, no, it's not. Legally, any contributions after the commit that changed the license from CC to GPL need to be audited to ensure they conform to the CC-BY-3.0 license. Actually, it would be best if they complied with the new CC-BY-4.0 license, which will be applied to the copy that will be pushed into FGAddon by Hamza.
If you are the sole contributor then this will be no problem, we just have to rebase your commits.
jsb wrote in Sun Sep 13, 2015 11:39 am:Could somebody explain how exactly that could happen? I still do not fully understand.
See above.
legoboyvdlp wrote in Sun Sep 13, 2015 12:37 pm:IAHM-COL thought yours was the same liscencing as FGADDON CRJ so he changed it from CC-BY-3.0 TO GPL. but on september 11 he changed it back, seeing the error.
So now its compatiable with GPL, and it can be put in ADDON and MEMBERS.
Wrong. "Changing it back" is not sufficient, see above.