FlightGear hangars: Difference between revisions

Jump to navigation Jump to search

FlightGear hangars (view source)

Revision as of 10:29, 31 July 2018

3,128 bytes removed ,  31 July 2018
Major clean up - including the removal of all quotes.
(→‎Third party sites: Links to the new hangar catalog page.)
(Major clean up - including the removal of all quotes.)
Line 1: Line 1:
{{cleanup}}
Aircraft in FlightGear are often distributed from a hangar.  The official FlightGear hangar is called [[FGAddon]] and it contains hundreds of aircraft at different stages of development (including aircraft from up to 20 years ago).  Many aircraft are also distributed via 3rd-party hangars.


: ''For other content than aircraft and liveries, see [[Links]]''
== Licensing ==


FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version.  
The [[FGAddon]] hangar is distributed using the GPLv2+ licensing terms - see the official [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document].  Third party hangars are free to license their content as they wish.


Be careful with external links!
{{caution|If licensing violations are found in a 3rd party hangar - including copying images, sounds, 3D objects or any other content that cannot be legally copied, or any non-legal licensing combinations - the FlightGear developers reserve the right to remove all mentions of that hangar from the official FlightGear web infrastructure (wiki, forum, mailing lists, etc.).  The advertisement of illegal content via the official infrastructure could lead to legal problems for the FlightGear developers.}}


== Background ==
It is completely up to the original content author to decide how they wish to license their original work. GPL is just one option. Many people seem to prefer one of the variants of the creative commons license these days. If you are modifying someone else's original work, or incorporating portions of their work into your own work, then you must be respectful of the original author's license terms. If you wish to protect your work from being copied or modified (yet somehow still distribute it to users), FlightGear does not have the infrastructure built up to assist with that. Fgaddon is simply a resource offered to aircraft designers. It is a common area to share and collaborate for aircraft development. Historically it has also been the source of FlightGear aircraft that are included in the official distribution. Because fgaddon is closely tied to the main project, we do our best to ensure everything there is licensed with a gpl compatible license so we can safely distribute all those aircraft. We also do our best to ensure that fgaddon aircraft track upstream code changes in the flightgear program so that incompatibilities are not introduced. As others have said, the intention of FlightGear and our evolving infrastructure is to support and encourage 3rd party hangars, and we have no problem if developers want to use other resources to manage and distribute their original aircraft. It is especially important to maintain separation of content with gpl-incompatible licensing.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35077118/
  |title  =  <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
  |author =  <nowiki> Curtis Olson </nowiki>
  |date  =  May 10th, 2016
  |added  =  May 10th, 2016
  |script_version = 0.39
  }}</ref>
We have support for catalogs and external hangars for precisely this reason. We obviously want to encourage GPL aircraft, but not every aircraft developer wishes, or is able to, release their work under the GPL. FlightGear both respects and supports that option. <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35076199/
  |title  =  <nowiki> Re: [Flightgear-devel] botom line: if i don't my aircraft to be
subject to GPL FGAddon clauses </nowiki>
  |author =  <nowiki> Stuart Buchanan </nowiki>
  |date  =  May 10th, 2016
  |added  =  May 10th, 2016
  |script_version = 0.39
  }}</ref>
please do ask about setting up your own hangar with whatever license you like. One of the major goals is to give a better end-user experience for different sources of aircraft.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35077834/
  |title  =  <nowiki> Re: [Flightgear-devel] botom line: if i don't my aircraft to be
subject to GPL FGAddon clauses </nowiki>
  |author =  <nowiki> James Turner </nowiki>
  |date  =  May 10th, 2016
  |added  =  May 10th, 2016
  |script_version = 0.39
  }}</ref>
== Screenshots ==
{{See also|Canvas_Development#Canvas-based_Splash_Screens}}
Note in this system it would be important the screenshots are *just* screenshots - no border, badges or other info as some splash screens currently do. The idea being to add this using OSG dynamically from the metadata and then it can be restyled as needed.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35494679/
  |title  =  <nowiki> [Flightgear-devel] Hangar thumbnails, screenshots, splash-screens </nowiki>
  |author =  <nowiki> James Turner </nowiki>
  |date  =  Nov 16th, 2016
  |added  =  Nov 16th, 2016
  |script_version = 0.40
  }}</ref>


== Official FGAddon hangar ==
== Official FGAddon hangar ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/115699"

Navigation menu