4,400
edits
FG Add-on FAQ: Difference between revisions
Jump to navigation
Jump to search
m
Bot: Automated text replacement (-CVS +Git)
(New page: This document attempts to answer some Frequently Asked Questions from aircraft/scenery add-on developers coming from other simulators. It does not cover technical details, but rather desc...) |
m (Bot: Automated text replacement (-CVS +Git)) |
||
| Line 34: | Line 34: | ||
You may be able to release your add-ons under the GPL, and the FlightGear community would encourage you to do so for a variety of reasons: | You may be able to release your add-ons under the GPL, and the FlightGear community would encourage you to do so for a variety of reasons: | ||
* It maximizes the freedoms that the community has to enhance and maintain your add-on. This can be particularly important as the pace of FlightGear development is very high, and you may no-longer want to support the add-on yourself. | * It maximizes the freedoms that the community has to enhance and maintain your add-on. This can be particularly important as the pace of FlightGear development is very high, and you may no-longer want to support the add-on yourself. | ||
* It can be maintained within the FlightGear source-code repository ( | * It can be maintained within the FlightGear source-code repository (Git), and included in subsequent FlightGear releases. | ||
* It can easily be combined with other FlightGear GPL'd components, and made greater than the sum of its parts. | * It can easily be combined with other FlightGear GPL'd components, and made greater than the sum of its parts. | ||
* Most core developers prefer to work on GPL's software, as they see it as being more beneficial to the community. They may work on GPL add-ons in preference to non-GPL add-ons. | * Most core developers prefer to work on GPL's software, as they see it as being more beneficial to the community. They may work on GPL add-ons in preference to non-GPL add-ons. | ||