Clearly with five years of discussions already undertaken it was not a viable path forwards to restart discussing the splitting of the assets and which revision control systems were most suited for the FlightGear project. Unfortunately this necessary change resulted in a fundamental disagreement with a couple of FlightGear users who demanded that the decision making process be restarted.
This required the removal of the aircraft models from the old fgdata repository, leaving the core assets and the default aircraft. Why not switch the core infrastructure to FGMEMBERS?ĭuring five years of in-depth discussions on the development mailing list (where decisions are made ) a consensus of opinion was reached which defined the future direction for the core assets of the FlightGear project.Why not consider the FGMEMBERS proposal?.Why use the “hostile fork” terminology?.Why is FGMEMBERS considered as a legal liability?.This includes the divergence of models as well as scenery enhancements that are not contributed to the scene models database. From experience, the core team knows that the lack of appropriate controls on contributions may, after a long period of time, lead to a divergence that may result in contributions being lost. The FGMEMBERS infrastructure offers little benefit to contributors. The core FlightGear team feel that it is important to make a clear statement of their position concerning the FGMEMBERS organization, explaining why it is important to continue working in a way that will ensure that FlightGear continues to prosper for the next 20 years as well as to clear up any confusion and FUD that has been disseminated by members of the FGMEMBERS organization.
FLIGHTGEAR TIPS AND TRICKS SIMULATOR
What you see today as FlightGear is the result of 20 years of collaborative development effort by hundreds of talented people all working together to provide a freely available GPL flight simulator that anyone can contribute to. FlightGear FGMEMBERS Statement (v2.2): Preface
0 kommentar(er)
