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 15:26, 8 February 2012
, 8 February 2012no edit summary
m (http://www.flightgear.org/forums/viewtopic.php?f=3&t=11646&start=45#p120961) |
mNo edit summary |
||
| Line 37: | Line 37: | ||
So, we would like to ask you to keep these factor in mind when proposing changes and when voicing recommendations, and when discussing such issues with fellow community members, publicly or privately. | So, we would like to ask you to keep these factor in mind when proposing changes and when voicing recommendations, and when discussing such issues with fellow community members, publicly or privately. | ||
= The dependency structure = | |||
Flightgear, as best as we have managed to understand the somewhat opaque workings in core development, is a meritocracy - your influence is proportional to the amount of work you do for the project. It's not closed, i.e. you can, if you invest a lot of work into the project, work yourself into a position where you have a lot of influence even starting today from zero. | Flightgear, as best as we have managed to understand the somewhat opaque workings in core development, is a meritocracy - your influence is proportional to the amount of work you do for the project. It's not closed, i.e. you can, if you invest a lot of work into the project, work yourself into a position where you have a lot of influence even starting today from zero. | ||