20,741
edits
Howto:Start core development: Difference between revisions
Jump to navigation
Jump to search
→Initial advice
(→Project architecture: Courtesy of Jim Wilson 2003: http://www.mail-archive.com/flightgear-devel@flightgear.org/msg16568.html) |
|||
| Line 62: | Line 62: | ||
= Initial advice = | = Initial advice = | ||
Our advice would be: Start small, start simple, communicate a lot and most importantly '''release early & often''' | Our advice would be: Start small, start simple, communicate a lot and most importantly '''release early & often''' (i.e. use topic branches and commit frequently, and encourage others to provide feedback) | ||
* if you know you want to contribute to the source code, make sure that you are actually able to build FG from source, you can get help using the forum, the mailing list, the issue tracker or live support using IRC chat | * if you know you want to contribute to the source code, make sure that you are actually able to build FG from source, you can get help using the forum, the mailing list, the issue tracker or live support using IRC chat - we have articles on building FG on various platforms, see [[Building FlightGear]] | ||
* read the documentation (wiki, $FG_ROOT/Docs) | * read the documentation (wiki, $FG_ROOT/Docs, $FG_SRC/mini-docs) | ||
* it also helps running DoxyGen our Source Navigator | |||
* start making tiny modifications to existing stuff (aircraft, scenery, source code etc) | * start making tiny modifications to existing stuff (aircraft, scenery, source code etc) | ||
* try to get to grips with how git works (we have some resources to get you started, using GUI frontends like qgit or a good IDE can be helpful) | * try to get to grips with how git works (we have some resources to get you started, using GUI frontends like qgit or a good IDE can be helpful) | ||
* register an account at gitorious | * register an account at gitorious | ||
* clone the FG project (SimGear, FlightGear, fgdata) | * clone the FG project (SimGear, FlightGear, fgdata) | ||
* browse the issue tracker for bug reports/feature requests, help triage problems, maybe provide patches too (i.e. to mute compiler warnings, to fix memory leaks, fix/add comments, clean up source code)? | * browse the issue tracker for bug reports/feature requests, help triage problems, maybe provide patches too (i.e. to mute compiler warnings, to fix memory leaks, fix/add comments, clean up/refactor source code)? | ||
* search the archives (forum and mailing list) for discussions related to your area of interest, these contain often valuable pointers that may save you hours of work | * search the archives (forum and mailing list) for discussions related to your area of interest, these contain often valuable pointers that may save you hours of work | ||
* subscribe to the developers mailing list | * subscribe to the developers mailing list | ||