20191030 Dev Meeting

Agenda

General:

• Update from relevant previous calls
• Tagged: issues, PR.

Notes

Call 1

• Microservices proposal.
  • Discussed efficiency/flexibly of message set - decided this needed if we want to have new drones work with old GCS.
  • Discussed rules for what microservice support means, and some guidance. Essentially comes down to "Supported is what docs say it means. By default we assume that support means you do everything documented, or the service must create mechanisms to allow you to determine what is supported.
  • Wen through some real examples.

Not discussed:

• #1228 common.xml: add AIS message
  • Action: JamesP still hoping to do due diligence and confirm these are sane.
• #929 No way to transmit airspeed reference
  • JamesP: ArduPilot investigated. ArduPilot DO use NAV_CONTROLLER_OUTPUT. We will discuss options again when he is fully present in 2 weeks.
• #1206 ArduPilot downstream changes
  • This had problematic downstream changes. JamesP agreed to follow up.
• #1234 Add messages for power regulation and temperature status reporting
  • JulianOes to review in coming weeks. James to test if has any constraints in terms of implementation.
• Common Flight Modes Microservices
  • Action on Lorenz to do first evolution of spec/requirements.
• JulianOes discuss "MAVLink connection semantics
• #1216 SET_POSITION_HOME: Add frame for local coordinates

AI:

See above!

Attendees

HamishW, JulianOes, Jonas, Kjar... (sorry, lost record)