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 17:10, 8 February 2012
, 8 February 2012→FlightGear is a meritocracy: http://www.flightgear.org/forums/viewtopic.php?f=3&t=11646&start=45#p121021
m (→FlightGear is a meritocracy: http://www.flightgear.org/forums/viewtopic.php?f=3&t=11646&start=45#p121021) |
|||
| Line 58: | Line 58: | ||
The reason is, simply the dependency structure: Flightgear can run, live and be developed without detailed 3d models, but it can not run without C++ code. If tomorrow all C++ developers quit, that's quite possibly the end of Flightgear, if tomorrow all 3d modellers quit, that's the end of eye candy in Flightgear. | The reason is, simply the dependency structure: Flightgear can run, live and be developed without detailed 3d models, but it can not run without C++ code. If tomorrow all C++ developers quit, that's quite possibly the end of Flightgear, if tomorrow all 3d modellers quit, that's the end of eye candy in Flightgear. | ||
It's not particularly fair that this translates into the existing project structure, and in fact if you go through my posts here and on the devel list, you'll see that I continue to make the same point. As I said, can't all be fixed in a day... I don't have a particularly large influence either, all I can do is talk to people and ask for patience. You can read up what I wrote in the case of the Bo-105... Good work tends to be recognized eventually - be it modelling or coding. But there's no guarantee, sometimes you have to accept being frustrated, get up and try again. Or you walk because things are not perfect as they are, which is a pity. | |||
= To be discussed = | = To be discussed = | ||