Please visit our forum if you cannot find what you're looking for.
|
|
|
Put a piece of yourself into FlightGear!
|
|
|
|
|
For core developers
|
Visit Category:Core development projects to see a list of currently ongoing projects!
See Category:Developer Plans to see a list of developer plans for the upcoming release.
See request for comments for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress (admittedly a little outdated meanwhile).
Help needed:
The YASim FDM is looking for a new maintainer:
|
There are some pending merge requests[1] to add some YASim features, but we have an issue that since none of the current C++ developers own, or are experts in YASim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too,
if people are new to C++), and providing we have some assurance that a representative sample of YASim aircraft are unchanged or improved by the patch.
Suggestions for that means in practice, are most welcome!
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.[1]
— James Turner
|
|
|
I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my latencies here are measured in weeks.Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.[2]
— Andy Ross
|
|
|
|
|
|
Coding Help Needed! (Updated 06/2020)
|
|
|
|
|
Wanted: interview candidates
|
|
|
Development repository status
|