20,741
edits
FlightGear wiki:Instant-Refs: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear wiki:Instant-Refs (view source)
Revision as of 23:22, 19 November 2015
, 19 November 2015→Motivation
m (→Motivation) |
|||
| Line 6: | Line 6: | ||
{{FGCquote | {{FGCquote | ||
|1= As someone new coming to FG, it's pretty tricky to get a handle on what's going on, what's being worked on, what needs fixed and so on. Of course this is an issue for all software projects, and there's different solutions depending on the nature of the team, how many active contributors exist and so on. FG seems to have a few potential tracking 'points' - the Developer Wiki, the SourceForge tracker / bug system, some (mandated) files in CVS (ToDos) and the usual source code 'FIXME' annotations (which something like Doxygen can extract, if formatted suitably). | |1= As someone new coming to FG, it's pretty tricky to get a handle on what's going on, what's being worked on, what needs fixed and so on. Of course this is an issue for all software projects, and there's different solutions depending on the nature of the team, how many active contributors exist and so on. FG seems to have a few potential tracking 'points' - the Developer Wiki, the SourceForge tracker / bug system, some (mandated) files in CVS (ToDos) and the usual source code 'FIXME' annotations (which something like Doxygen can extract, if formatted suitably). | ||
[...] | |||
From reading the code, the list, and watching CVS commits, plus the odd naiive email, it's possible to get p | |||
partial answers to all of the above, but they are incomplete answers at best. | |||
[...] | |||
The main question is about visibility, i.e if there's a place any of the above is recorded by a working consensus (eg, > 60%) of developers. | |||
|2= {{cite web | |2= {{cite web | ||
| url = https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg17198.html | | url = https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg17198.html | ||
| Line 13: | Line 18: | ||
}} | }} | ||
}} | }} | ||
== Background == | == Background == | ||
FlightGear's development is not centrally coordinated in any way – at best, it is "self-coordinated," i.e., contributors discuss ideas and make proposals to contribute in a certain fashion and then team up to implement certain features and building blocks. | FlightGear's development is not centrally coordinated in any way – at best, it is "self-coordinated," i.e., contributors discuss ideas and make proposals to contribute in a certain fashion and then team up to implement certain features and building blocks. | ||