2,561
edits
Portal:Developer: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (more explanation about RFCs) |
mNo edit summary |
||
| Line 176: | Line 176: | ||
'''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). | '''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. | 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 or prioritized by the FlightGear community. | ||
These RFC documents are however intended to hopefully help increase awareness of long-standing issues and challenges affecting FlightGear's evolution and development progress in order to solicit community feedback about possible approaches to address these in an efficient and structured fashion. | These RFC documents are however intended to hopefully help increase awareness of long-standing issues and challenges affecting FlightGear's evolution and overall development progress in order to solicit community feedback about possible approaches to address these in an efficient and structured fashion. | ||
Anybody is welcome to comment on, refine and help develop strategies to tackle the challenges presented in these RFCs. | Anybody is welcome to comment on, refine and help develop new strategies to tackle the challenges presented in these RFCs. | ||