Lydiot wrote in Tue Sep 15, 2015 3:29 pm: Or could it "spread" to other parts of the FG 'universe'....?
Yes, unfortunately this is a legitimate concern. The latest example occurred when the Boeing 787-8 from Omega Hangar was added to the FGADDon to become the official Boeing 787
http://sourceforge.net/p/flightgear/fgaddon/888
Then, the group realized that cleaning of non-GPL files coming from Navigraph (which are not possible to be distributed under GPL content) were added; Therefore, the following actions are of expurging the source from these files
http://sourceforge.net/p/flightgear/fgaddon/889
http://sourceforge.net/p/flightgear/fgaddon/890
This actions are benefitial, and off course transmit to FGMEMBERS as well
https://github.com/FGMEMBERS/787-8/comm ... b38ab7dcc6
https://github.com/FGMEMBERS/787-8/comm ... 4d5879745f
https://github.com/FGMEMBERS/787/commit ... ad91b0e252
https://github.com/FGMEMBERS/787/commit ... a5cd9ad3d7
Another case referred to the Fokker 100 sound package which contained a dubious file and was subsequently removed by E. Hofmann
https://github.com/FGMEMBERS/fokker100/ ... 4a1bb5e488
http://sourceforge.net/p/flightgear/fgaddon/853/
So yes, these issues happen, and the community all together works to maintain compliance.
It is not a problem that exists because FGMEMBERS, as Stefan indicates, and although you can probably find examples of dubious files added throughout the project history, the proper thing is curation, cleaning, and removal.