CitationX by Patten Hangar

[legoboyvdlp]

http://www.mediafire.com/download/hpxes6u7e4xh2sy/CitationX-31-12_2015.zip



Looks --awesome--.
I'm downloading; if it is GPL, it is going into the FGMEMBERS CitationX.

[legoboyvdlp]

cf0d3ea "new patten citationx"

[IAHM-COL]

Looks good
Thanks Lego

I created a branch for the SVN version of this aircraft then'

IH-COL
https://github.com/FGMEMBERS/CitationX/tree/svn

[legoboyvdlp]

They should really put it into svn -- too busy worrying over FGMEMBERS licencing ""issues"" (quotes mine) I suppose.

[IAHM-COL]

[two raising shoulders and a disregarded gaze]

There are no "licensing" issue on FGMEMBERS. That is just a lot of smoke they did believing that a war of flames was necessary to stop the project. And a lot of fake statements thrown into the wild.

But at the end of the day, what they do or not, merge or not in FGADDon, is less of importance to much anyone, right now.

They call themselves, "official" -- whatever that could mean. I say, FGMEMBERS is the "de facto" source for Aircraft downloading in FG. In my opinion, de-facto requires more attention.

IH-COL

[legoboyvdlp]

Uhuh, exactly.
Except for that Omega fiasco....the 787-8 had some stuff.... but.... one out of 800?
Well, I wouldn't say no to my 787-9 going to FGADDON.
But in any case, it is not ready for FGMEMBERS OR FGADDON yet.

[IAHM-COL]

If a non-compliant file (series of files) gets in a repo... well... simply trash it. As we did.
That's that.
Then, the best alternative is to find a compliant replacement. In the case of the Omega Navaids, we could actually get open files from opennav.com, but then it requires someone caring about it enough to fill those files with valid alternatives again.

The whole: OMG, OMG! by certain Finnish people, was just the observation of a Window of Opportunity to create propaganda.

[IAHM-COL]

The CitationX by Patten is looking awesome!

and I am looking forward to see what you get on the 787-9.

Remember FGMEMBERS is not a "finished" product library, but a repository of development, so don't feel afraid of "publishing early, publishing often" approach.

As a matter of fact, most --if not all-- our aircrafts could be conventionally declared WIPs.

[legoboyvdlp]

Hah!
Certain finnish people get told off by stuart too
Yep -- but it is totally not in a publishable state. It still requires a re-3D, addition of GEnx engines, and uv mapping.

[IAHM-COL]

Yep -- but it is totally not in a publishable state. It still requires a re-3D, addition of GEnx engines, and uv mapping.

That's fine by me
What is not fine to me is that you guys (example you with the 787-9) or it0uchpods with his versions, or The same Finnish guy with his shuttle, or artix with the A333, feel entitled to say.... it is GPL, but! (and a but that means: "Not GPL for FGMEMBERS in particular")

That is bribery, or certainly feels like, because by violating verbally the re-distribution allowance clauses on the GPL is actually violating GPL itself: That is, you can't say to anyone: Don't republish/fork/redistribute "my" GPL material. (illegal and a real copyright violation saying so!) [**]

[No excuse makes the above statement valid. That is why you have the "no warranty" statement that protects you for my arguing it was not good enough. If it's good for me; ok. If it is not: that becomes "my", not "your" problem]

So, for now, I am going to assume you did not understand the license, and go ahead and fork.

I wish you good work on the 787-9
Best
IH-COL


----Footnotes
[**] The only way to prevent redistribution of a work is to both, 1) own the copyright, and 2) License it in a manner such as you actually forbid redistribution. Example, the exquisitely delicate Su-15, or another example: Windows (R)