20,741
edits
How the FlightGear project works: Difference between revisions
Jump to navigation
Jump to search
m
How the FlightGear project works (view source)
Revision as of 21:14, 25 December 2013
, 25 December 2013→You need development guidelines: http://forum.flightgear.org/viewtopic.php?f=42&t=21612&p=196718#p196718
m (Update forum links) |
m (→You need development guidelines: http://forum.flightgear.org/viewtopic.php?f=42&t=21612&p=196718#p196718) |
||
| Line 96: | Line 96: | ||
I just have no sympathy for people who take, are not prepared to do any work, but feel entitled to say how others should do their job and issue demands for features, aircraft, documentation, whatever. You may call that elitism, I call that my sense of fairness. | I just have no sympathy for people who take, are not prepared to do any work, but feel entitled to say how others should do their job and issue demands for features, aircraft, documentation, whatever. You may call that elitism, I call that my sense of fairness. | ||
= Lack of Support and Backwards Compatibility = | |||
FlightGear is a volunteer effort and no one is paying several thousand dollars a year for software and related support each year. Since legacy support is expensive (IE. time/effort) one of the ways a project like FlightGear deals with this is to limit legacy support. If this were not the case then time/effort would be expended on legacy support that could be used for new features and bug fixes. Like most things there are trade offs involved. Which do you want - more advanced FlightGear and aircraft or better support for older versions? This is a common issue for open source software and most prefer to look forward rather than looking back. | |||
= You need development guidelines = | = You need development guidelines = | ||