20,741
edits
FlightGear hangars: Difference between revisions
Jump to navigation
Jump to search
m
copied relevant text from FlightGear and Content Protection (DRM)
m (→Aircraft hangars: Updated the FGMEMBERS links to point to GitHub, as the blanked out FGMEMBERS wiki article has been deleted.) |
m (copied relevant text from FlightGear and Content Protection (DRM)) |
||
| Line 6: | Line 6: | ||
Be careful with external links! | Be careful with external links! | ||
== 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> | |||
== Official hangars == | == Official hangars == | ||