980
edits
User:Callahanp: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
I hope to make regular code contributions to FlightGear. I want to gain the skills to address some FlightGear issues as they come up and participate in the discussions and programming for the various [FlightGear Epics |https://gitlab.com/groups/flightgear/-/epics?sort=created_date&state=opened&first_page_size=100] | I hope to make regular code contributions to FlightGear. I want to gain the skills to address some FlightGear issues as they come up and participate in the discussions and programming for the various [FlightGear Epics |https://gitlab.com/groups/flightgear/-/epics?sort=created_date&state=opened&first_page_size=100] | ||
Teamwork: | === Teamwork: === | ||
I'm a believer in teamwork and would love working closely in real-time with others on specific programming problems. I hope we can create opportunities for that. | I'm a believer in teamwork and would love working closely in real-time with others on specific programming problems. I hope we can create opportunities for that. | ||
| Line 28: | Line 27: | ||
We're taught in academic settings to program by ourselves and hand in ou submissions for review as "homework", but we continue that pattern in our work mainly out of inertia and lack of proper training. There's no reason to continue that pattern outside of a classroom as our only or even as main way of working together. | We're taught in academic settings to program by ourselves and hand in ou submissions for review as "homework", but we continue that pattern in our work mainly out of inertia and lack of proper training. There's no reason to continue that pattern outside of a classroom as our only or even as main way of working together. | ||
== Understanding FlightGear's | == Understanding FlightGear's Large & Complex Codebase == | ||
The problem with FlightGear is its size, complexity, and the lack of a detailed guide to exploring that complexity. Several factors contribute to that complexity. Understanding FlightGear requires knowledge of many application domains, C++, an internal scripting language, a global data store, application features driven by XML or scripts, network protocols and data formats, some custom, some obscure, and from the era of mainframe computers. | The problem with FlightGear is its size, complexity, and the lack of a detailed guide to exploring that complexity. Several factors contribute to that complexity. Understanding FlightGear requires knowledge of many application domains, C++, an internal scripting language, a global data store, application features driven by XML or scripts, network protocols and data formats, some custom, some obscure, and from the era of mainframe computers. | ||