yes. I was looking at the git svn software, and it may be a way for me to go around the decision of the devs here.
I may/may not develop. I don't like to just blatantly chop my options of participate in aircraft polishing just out . I am not a proficient developer yet, but I've been learning the ins and outs of how contributions are made to Flightgear. I have been testing my skills in 2 projects: One scenery related (KXTA) and one aircraft related (EF-Typhoon), which I am currently hosting at github (https://github.com/IAHM-COL)
In any case, I was hoping to get some instruction into how to move forward. Essentially
1. Flightgear is still and will still be at gitorious
2. Simgear is still and will still be at gitorious [YES, I do compile from source!]
3. fgdata (the "base" or "required" simplified package) will still be at gitorious
4. fg-addon (which host the plethora of aircraft) is now hosted in SVN (a different animal!)
Now, In my current settings (and I wont surprse this is most everyone-else), the "fg-addon" resides in fgdata/Aircraft/*
(Naturally), now
1. If I clone fgdata (today), will it come still with the planes? (I see them still up in gitorious)
2. So ... If I decide to merge the SVN, will I perform such SVN command inside fgdata git-directory? so all my aircraft now downloads in fgdata/Aircraft/* or is there a change in how this is being managed now?!
3. If I place the add-on SVN inside fgdata, I expect this to mess with my "git status" for fgdata! To the least, now I will have a directory that the repo does (or will ) not
--How on earth to manage / stash that incongruence, or is this non-incongruence at all?!
I do follow the arguments of Johan G above. Thans for putting it clear cut. Our problem is size+traffic, and I can definitely see that being a git-conflict. But on general terms, how is ppl managing the add-on (not in fgdata anymore) nowadays?