Pl/FGAddon: Difference between revisions

FlightGear został zapoczątkowany 8 kwietnia 1996 roku przez Davida Murra, który zaproponował stworzenie nowego symulatora lotu przez wolontariuszy<ref>David Murr (9 kwi, 1996).  Propozycja FlightGear 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J "A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@"].  opublikowana na grupie dyskusyjnej rec.aviation.simulators.</ref><ref>David Murr (1996).  Propozycja FlightGear 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR "This truly is as real as it gets!" - propozycja nowego symulatora lotu - WERSJA 2.0].</ref><ref>David Murr (29 paź, 1996).  Propozycja FlightGear 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, "The future of flight simulation is here"].  Opublikowana na [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com liście mailingowej].</ref><ref>David Murr (11 wrz, 1998).  Propozycja FlightGear 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, "The future of flight simulation is here"].</ref>.  Częścią początkowych celów było opracowanie procedur graficznych 2D i 3D dla symulatora. Było to jednak ogromne zadanie, które zostało przerwane na początku 1997 roku, gdy główny programista, Eric Korpela, kończył swoją pracę magisterską. Jednak, począwszy od 16 maja 1997 roku, Curtis Olson wznowił prace nad nowym projektem opartym na bibliotece OpenGL, umożliwiając stworzenie funkcjonalnego symulatora lotu w krótkim czasie<ref>Curtis Olson (28 wrz, 2015).  [http://forum.flightgear.org/viewtopic.php?f=42&t=27558&p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@].  Opublikowanym na forum FlightGear.</ref>.  Pierwsze zatwierdzenia dotyczyły oryginalnych repozytoriów kontroli wersji [[FlightGear CVS|CVS]] flightgear i simgear.

As the project grew, so did the size, quantity, and quality of the FlightGear assets. These assets were not organised and were scattered across different parts of the internet. Therefore it was decided that much of this FlightGear content would be assembled and stored together in a new centralised CVS repository called fgdata, which was created on October 22, 2000. To allow for the legal redistribution of these assets as part of the FlightGear distribution, a GPLv2 only policy was adopted.

In May 2010, development was interrupted by the infamous ''"coffee incident"'' which resulted in the loss of Curtis' home server hosting all of the FlightGear repositories<ref>James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 <nowiki>[Flightgear-devel]</nowiki> Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.</ref>.  These events resulted in a [[FlightGear CVS|mass migration of all the CVS repositories to Git repositories]].  Due to bandwidth issues, it was decided that the new repositories would be hosted on the Gitorious open source infrastructure.

With time as the project grew, the size and scope of the fgdata repository mushroomed, mainly due to the growing number of aircraft stored in [[$FG_ROOT]]/Aircraft, so that a split was inevitable.  A first splitting attempt was organised by Gijs de Rooy and announced on October 18, 2011<ref>Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 <nowiki>[Flightgear-devel]</nowiki> FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.</ref>.  Each aircraft was placed in its own Git repository and all aircraft linked back to fgdata using a Git submodule approach.  However this attempt failed and was abandoned.  From this date until the end of 2014, the design of the fgdata split was discussed on the development mailing list and summarised in the [[FlightGear Git: splitting fgdata]] wiki article.  In the planning stages, the repositories were known as fgdata-old splitting into [[FGData]] (a.k.a. fgdata-new) and FGAddon (a.k.a. flightgear-aircraft and fgaircraft). After half a decade of planning, it was decided that the best solution for FlightGear aircraft development would be a single centralized Subversion repository. This would facilitate community management and maintenance of the aircraft while at the same time providing modularity and smaller downloads and smaller local repository sizes.

In late 2014, Gitorious, the provider of the open source infrastructure for the FlightGear source code and data repositories announced that it would shut its services down by May 2015 due to its acquisition by GitLab. This catalysed the split of fgdata-old and a switch to the SourceForge open source infrastructure for the hosting of the VC repositories. Other parts of the FlightGear infrastructure were already hosted by SourceForge, making the move a natural one. Sealing the deal, SourceForge agreed in writing to host the huge FlightGear aircraft collection, the size of which is unrivaled in open source circles. Today, the FGAddon SVN repository, together with most of the FlightGear project infrastructure, is hosted on SourceForge.

In August 2015, a new FlightGear policy document was written to codify the unwritten standards of the project<ref>[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.</ref>.  With this document, the licensing policy for the FlightGear aircraft hosted on FGAddon has been updated from being GPLv2-only to now being GPLv2+. To combat licence proliferation, avoid complications using work from one aircraft in another, and for the integrity and good of the FlightGear project, it is strongly recommended that all original content (whether hosted in FGAddon or elsewhere) be GPLv2+ licensed.