S&J wrote in Sat Feb 06, 2021 1:44 pm:I'd advice you to use CC, as it gives you access to use FGUK's 3d, 2d and animation plus Bombers JSBsim helicopter code.
If what you produce is good enough people will find it through word of mouth.
Plus it can't be use to con people out of money by paying for Flightgear rip off.
wlbragg wrote in Sat Feb 06, 2021 10:12 pm:If you want it in the main FG repository then you need to use GPL. But then your work is truly free for anyone to do most anything with, within the GPL restraints of course. I would personally never recommend that someone use anything other than GPL if it is to be associated with FilghtGear, after all that is our entire philosophy.
@S&J
I don't understand your truly free comment.
Only that they are indeed free to "rip you off" as you mentioned. But also free to do other "legit" commercial projects as well.
I understand your reasoning and it is reasonable. But that is precisely why I am less enthusiastic about using a license other than GPL. It is now and forever under that license and I can't use any parts of it for my purposes on another GPL aircraft which would be part of my reason for wanting to help contribute in anyway I can.
@bell_pilot
As far as figuring out the license later on, I wouldn't be interested in working on a project unless It was GPL. That is the only way I can reuse any creation in other projects I am interested in that are GPL.
For what it's worth, I'm currently working on the YASim version of the AirCrane (GPL). I have always wanted a JSBSim version of the FDM to really do it justice but I don't have the background nor willingness to learn something so complex, at least at this stage. So when I hear of someone considering creating another JSBSim helicopter FDM version to possibly study from, I am encouraged. If it potentially is not going to be available for my purposes because of license, or lack of, then that isn't something I place at the top of my limited attention nor am I willing to invest time in.
Licensing matters!
I don't mean to hijack this development thread and turn it into anything other than developing the AH-1W. It's that if this new interest in revitalizing this project goes somewhere, I wish to try to steer it into the right direction, or at least a direction I might be able to leverage later on. My understanding is that CC would shut me out for my purposes.