The FGDATA has succesfully been transferred to the NEXT GENERATION FGDATA
Now also available (NOT IN TEST MODE) with Submodules
The location of FGMEMBERS remains unchanged at: https://github.com/FGMEMBERS
The fork of the Official FGDATA Fork can now be obtained at: https://sourceforge.net/p/fgdata/submod ... next/tree/
Read the Notification here:
viewtopic.php?f=28&t=25314&start=45#p234592
_______________________________________________________________________________
@ALL Flightgear Devs (Core, Aircraft and Other)
Introduction:
Fetching FGdata has been done with a repository hosted in gitorious, for as long as I can remember. (Ive heard it was different before).
This was a very cool way to fetch all the contents of the mainstream FGDATA, including an astonishing amount of FG aircraft in very varied states of development. That are there for us to play with. Literally. Meaning, flying them, tweaking them, forking them, and in the good cases, sharing our updates with the FG world via GIT MERGE REQUEST
The Problem:
The size of this monolithic FGDATA was huge, naturally causing several headaches
1. Git cloning it. Was a time for 2 or 3 coffes. Yes, you get all in one hit. but a loooong hit
2. Git repos size limitation. Happily gitorious allowd that big thing. other repo hosts may be less friendly... but although accepting they seem to be complaining to the dev-core's
3. Git traffic in a huge repo also a problem
4. A project like that large and monolithic, and full of binaries is in summary hard to keep/maintain/develop etc
https://gitorious.org/fg/fgdata/source/ ... 52a366de09:
The proposed Solution
Currently, the solution being executed is, to keep a BASE PACKAGE fgdata, without most of the aircraft, in gitorious. Then move every aircraft away into another monolithic huge repository. And to avod git hosting frictions, they decided to migrate (Back?!) to SVN, CVS done right!, in sourceforge.
http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/
viewtopic.php?f=28&t=24045
IAHMCOL cries loud, request a reversal of decision, suggest a few alternatives
I may seem very childish and negative when it comes to adopting SVN.
Maybe right. Also questioning a few things like, adopting SVN for the Aircrafts, adopting GIT for the rest; Finally when I am interested in submit a few modifications of a plane, (EF-Typhoon), I found out that logically the master repo, the SVN is under siege by the core devs. Logically cause noone wants to let anyone accidentally damage years of work. But under siege anyways. And for those, that doubt that there is some sort of controlling siege in place look at the answer of FF-JJTH to the request of a new inclusion:
http://sourceforge.net/p/flightgear/tickets/3/
Does that foster new collaborations?! What is the problem with allowing a new plane that even other devs can progress? Is every other plane in FG a prime-status of dev such that another plane will be soooo much below the threshold ? (these are retorical questions since I hardly see someone changing my opinion here, too)
So I found now the Aircrafts not only move to SVN, but also are now under siege and protected for good.
In the Git world that type of politics has few place. An user forks, modifies, and pulls a request. The request is evaluated, and hopefully if it does not break something luckily goes in, so every other FG member has access to a new "drone" or "plane" or whatever. If it s not good, maybe the base for a new collaboration. A new project. A new moving forward.
The SVN moves sounds like a taken decision
The point behind, the discussions already took place. Its too late to cry on running milk.
A git approach
Fork.
From where, the gitorious fgdata will loose all its aircraft in a menacing near future.
So I decided to step ahead and make a new Proposal for FGDATA management.