Free Flight, Free Speech

https://forum.flightgear.org/viewtopic. ... 30#p328322

Curtis Olson wrote:Note to Israel: You might be wise to review this situation yourself carefully and decide for yourself if you want to keep the vslash's Bell 412 in your own github repository. If Cerasim should determine there is an issue and if they would make a complaint to github, could having stolen material there put your whole collection at risk? There is no such thing as perfection in this world,. I can't predict what Cerasim's response might be. But if there is deception going on in this matter, I would hate for that to cause trouble for other people's projects and archives.

Hi Curtis, Thanks for your note,
Do you mean, to remove the Bell-412 by V-Slash?
https://github.com/FGMEMBERS-NONGPL
https://github.com/FGMEMBERS-NONGPL/Bell-412

I am going to need a series of clarifications, because right now it seems to me you are speaking a bit of code:

1. Are you referring to the Non-GPL aircraft? and expecting that it follows GPL?
As far as I am aware, V-SLASH has always indicated the troubled license of this material, with Creative Commons, GPL and Copyrighted material all smashed in the content. The COPYRIGHT file and its evolution has been a transparent attempt by V-SLASH to inform you and I of this.

in master: https://github.com/FGMEMBERS-NONGPL/Bel ... /COPYRIGHT
old version: https://github.com/FGMEMBERS-NONGPL/Bel ... /COPYRIGHT

2. what files inside the Bell specifically belong to Cerasim, specifically in the current Bell master state?

3. What is the license Cerasim indicated over its files? is it a share-alike? Is it a share-not allowed type of license? Can the use v-slash has given to these files be considered "fair-use"? Has v-slash established contact Cerasim about this alledged use in non-GPL/free material (the Bell)?

4. Has anyone contacted the alleged copyright owner to verify his posture about the usage of these files in this manner? I think is clear that V-SLASH has put so much work and love in this helicopter, and that saying now that he is not allowed to clarify this issue and distribute as he pleases seem at the moment far fetched to me. Maybe he couldn't distribute it with a GPL license; which he is not doing as far as I am aware, but otherwise, I will admit to you is the most accomplished piece of rotatory craft FG can offer.

5. I get the impression, based on his updated copyright, that V-SLASH seems to prefer FGMEMBERS-NONGPL to drop the distribution as well. I had not been specifically clarified, here. This would be a big sorry, for reasons stated in four, above. A previous Creative Commons version exist which I could legally keep if otherwise. Albeit few, there are some aircrafts that disable sharing under every circumstance (a certain supersonic russian craft comes to mind). In aircrafts with licenses like that FGMEMBERS does drop distribution.

Best Regards,
IH-COL

"4. Has anyone contacted the alleged copyright owner to verify his posture about the usage of these files in this manner? I think is clear that V-SLASH has put so much work and love in this helicopter, and that saying now that he is not allowed to clarify this issue and distribute as he pleases seem at the moment far fetched to me. Maybe he couldn't distribute it with a GPL license; which he is not doing as far as I am aware, but otherwise, I will admit to you is the most accomplished piece of rotatory craft FG can offer."

I find it funny that Curt is looking out for your best interest after lovely book he wrote about FGMEMBERS on the Flightgear home page. Maybe its the fact that this wont be added to FGaddon and so Valery should be under investigation. This is not the first time recently I've seen this kind of treatment of developers who post on the FG forum.

If I were Curt I would have kept my questioning to PM's