Portal:Developer: Difference between revisions
m (fixed a minor typo) |
m (updating) |
||
| Line 22: | Line 22: | ||
|style="color:#000;"| | |style="color:#000;"| | ||
* [[ Project Infrastructure Enhancements ]] | * [[ Project Infrastructure Enhancements ]] | ||
* [http://code.google.com/soc/2008/ Google's Summer of Code deadline for mentor organizations closing | * [http://code.google.com/soc/2008/ Google's Summer of Code deadline for mentor organizations closing on wednesday] | ||
* [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply | * [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply | ||
|- | |- | ||
| Line 63: | Line 63: | ||
|- | |- | ||
|style="color:#000;"| | |style="color:#000;"| | ||
* [[ Contributor Repositories ]] mirrors, branches and forks privately maintained by contributors | |||
* [[ Submitting Patches ]] | * [[ Submitting Patches ]] | ||
* [[ Code Cleanup ]] | * [[ Code Cleanup ]] | ||
Revision as of 16:29, 10 March 2008
|
Developer Documentation
RFC Topics
Clarification:In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).
Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is endorsed by the FlightGear community.
- Next Generation Scenery - revamping the FG scenery engine
- Keyboard function priority list - reorganizing FlightGear keybindings
- FlightGear Sessions - discussing possible steps to finally allow aircraft to be reliably switched at runtime
- Formalizing Aircraft Status - discussing suggestions about how to more properly describe aircraft development status
- Simplifying Aircraft Deployment - identifying potential steps to simplify deployment of FlightGear aircraft
- FDM engine feature standardization - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines
- FlightGear Glass Cockpits - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems
- Recommended Property Tree Enhancements - discussing possible property tree enhancements to help ensure integrity of crucial runtime state