Josh, you know I would never argue with you without reason.
Nonsense, you don't need FGAddon to collaborate. I do all my projects in my GitHub and collaboration is easy.
I've been following this thread and I didn't get this out of any of the comments.
As you know the only default aircraft that is packaged with FG is "currently" a collaboration of folks preferring GitHub. It is then ported manually to the FG repository fgdata when a new release is on the horizon. The J3Cub as well as others I work on are done the same way with the exception that I also use a svn link to SourceForge fgaddon to transfer updates when ready. Because of my lack of knowledge I have to manually transfer updated files from my local git repo to my local svn repo first.
I don't exactly know how the Shuttle is set up but I do know I am using a local git repo to push to a svn-git repo on SourceForge when I do work on it.
Thorsten is the one who takes care of the magic of getting the releases to fgaddon.
So your statement is correct, but the implied tone behind it is something I don't understand. I have noticed as of late that fgmembers is not being updated as it once was. I know this for fact because I noticed changes I have made to numerous aircraft are not being forwarded into fgmembers in a timely fashion if at all. There may be good cause that I am not aware of but it is what I have noticed none the less.
Something else that I am extremely frustrated with is when I see aircraft changes to fgmemeber forks that never make it into fgaddon duplicate aircraft, as there was never any agreement on how to make that happen.
Simple fact of the matter is the way in which fgmembers was originated and managed, without comprise on both sides. It left a fractured society and is now responsible for many aircraft updates not getting into fgaddon. Fgaddon is the defacto repository managed by the FG organization and I think it should have the most up to date aircraft available, period.
Other, non-hostile, hangers don't try to duplicate aircraft repositories controlled by the FG organization. I say "controlled" loosely as the organization is only interested in a central repository overseen by the organization to allow for all aircraft to continue at least the basic updates to be able to run with new versions of the simulator.
Other non-hostile hangers don't work on aircraft that are also provided in fgmembers without periodically making their contributions back into fgaddon.
Other, non-hostile, hangers don't have a separate website with a section solely for the purpose of denigrating members in good standing of the FG organization. They try to work with the rest of the organization VS fighting with it.
I like the idea of a central location where you could go to get every GPL aircraft ever made, but that is a huge task to keep it organized and not competing with what the FG organization is trying to achieve. In the case of fgmembers its concept, while admiral, turned into a political "hostile" fork which in my opinion left a fractured, worse off infrastructure to everyones cause.
It is nothing but confusion for me and I know how it originated and how it works. I can only imagine the confusion of a new user of FG that comes along.
It's a fact, a couple people with less standing in the organization disagreed with several people, with maybe a little better standing in the organization, and refused to cooperate with a consensus and decided to do their own thing without regard to the negative side effects it could have on the organization as a whole.
Sad thing really! I wish it had turned out differently.