Portal:Developer: Difference between revisions

Jump to navigation Jump to search
Remove some outdated info
No edit summary
(Remove some outdated info)
 
Line 72: Line 72:
[[:Category:FlightGear Core developers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] <br/>
[[:Category:FlightGear Core developers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] <br/>
[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Nasal/CppBind|Adding scripting bindings]]<br/>
[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Nasal/CppBind|Adding scripting bindings]]<br/>
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]] <br/>
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]]<br/>
[[Built-in Profiler]] · [[Howto:Extend Nasal]] · [[Howto:Using Ada in FlightGear]] <small>(<font color="red">updated!</font>)</small><br/>
[[Built-in Profiler]] · [[Howto:Extend Nasal]] · [[Howto:Using Ada in FlightGear]]<br/>
[[Howto:Use Property Tree Objects]] · [[Code cleanup]] <br/>
[[Howto:Use Property Tree Objects]] · [[Code cleanup]] <br/>
[[FlightGear-Points of Interest]] · [[Request for comments]] <br/>
[[FlightGear-Points of Interest]] · [[Request for comments]] <br/>
Line 118: Line 118:
{{Main page/Leftbox|title=For core developers
{{Main page/Leftbox|title=For core developers
   |contents=
   |contents=
Visit [[:Category:Core development projects]] to see a list of currently ongoing projects!
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 [[: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). Also see the [http://build.flightgear.org:8080 Jenkins build page] and the {{tickets|Bug tracker}}.
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). Also see the [http://build.flightgear.org:8080 Jenkins build page] and the {{tickets|Bug tracker}}.
'''Help needed:'''
The [[YASim]] FDM is looking for a new maintainer:
{{cquote|There are some pending merge requests[http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/533DBD01.9040802%40sol2500.net/#msg32183541] 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.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}
{{cquote|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.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}
<references/>
}}
}}


{{Main page/Leftbox|title=Coding Help Needed! (Updated 06/2020)
{{Main page/Leftbox|title=Coding Help Needed! (Updated 06/2020)
   |contents=
   |contents=
<!--
out of date
{{Tip|
To keep the spirit alive and repeat the successful execution of the [[Virtual_FSweekend_Hackathon_2020|Virtual FSweekend Hackathon 2020]], we are having another [[Virtual_FSweekend_Hackathon_2021|Virtual FSweekend Hackathon 2021]] on the weekend of 5/6/7 November 2021 (in {{days from now|2021|11|5}}).}}
-->
* {{Progressbar|20}} [[Deboosting FlightGear|Replacing boost]]
* {{Progressbar|20}} [[Deboosting FlightGear|Replacing boost]]
* {{Pending}} [[World Scenery 3.0 roadmap]]  
* {{Pending}} [[World Scenery 3.0 roadmap]]  
* {{Pending}} [[Reset & re-init]]  
* {{Pending}} [[Reset & re-init]]  
* {{Pending}} [[Canvas Development]] - discusses possible future Canvas additions
* {{Pending}} [[Canvas Development]] - discusses possible future Canvas additions
<!--
out of date
* {{Pending}} [[Canvas Properties#Planned Features|Canvas Project (Planned Features)]] (fully scriptable 2D rendering API)
* {{Pending}} [[Canvas Widgets#Missing_.2F_Todo|Canvas Widgets (Missing Features)]] (Canvas GUI layer for scriptable widgets)
* {{Pending}} [[Howto:Use Property Tree Objects|Deprecate tied properties and use PropertyObjects instead]]
-->
}}
}}


{{Main page/Leftbox|title=Wanted: interview candidates
  |contents=Every month we try to include an interview with a contributor in the [[FlightGear Newsletter]]. Anyone contributing to FlightGear, in whatever way, is welcome to answer a few questions and write his/her own interview.
More info at [[FlightGear Newsletter: Interview]].
}}
}}
}}


Navigation menu