User talk:Bugman: Difference between revisions

: Hey! HerbyW was with me on mumble when I set all this up so I definitely have his consent (albeit vocal only). From what I understand, FGMEMBERS is also just aggregating hundreds of Git repositories anyways which on what I probed looked like all based on GPL or similar licenses so I hardly see any license issue. I don't object if there is some kind of "official" catalog.xml for any of those - I'm not making any money of it, nor am I using it to advertise or otherwise generate any value off of it (or, in fact, flagged my catalog.xml as "official", hence having them under 3rd party). Seeing the fact that however it creates a couple of GB of traffic every month on my server it seems there are at least some people using this feature so removing it might not be in everybody's best interest. If anyone steps up to fill the gap I'm more than glad to stop hosting them on my own but until that happens, removing the (as far as I am aware) only catalog.xmls out there kills a useful feature for little to no merit. [[User:DJGummikuh|DJGummikuh]] ([[User talk:DJGummikuh|talk]]) 05:50, 31 July 2018 (EDT)

: One addition: I'm scraping openly available github repositories and re-distribute them unaltered (except some minor adjustments to prevent name clashes and allow to see which hangar a plane comes from, since Flightgear does not show this on its own). Since I'm not compiling anything (all changes are made in human-readable text files) I'm automatically distributing the license file (if present) and all changed code to anyone. So I'm really pretty damn certain that no matter WHAT licens any of those planes is under, the mere fact that it HAS to be an open-source license (since we're talking about open github repositories) AND the fact that I'm not using their work commercially eliminates issues with any license I could possibly think of. [[User:DJGummikuh|DJGummikuh]] ([[User talk:DJGummikuh|talk]]) 05:58, 31 July 2018 (EDT)