20181128 Dev Meeting

Agenda

General:

Lorenz/BeatK:

CHECK Status (no relevant people present)

@JamesP and @MichaelS (or Lorenz/Thomas) to engage with Local and body frames and add comments. Discuss next week.
@WickedShell File format discussion - Attempt to re-engage in next two weeks.
@JulianOes to review and respond to message CRC checksum is wrong when a mavlink_message_t is converted to a sending buffer

MAVLink microservices versioning
- JamesP
  - recognises that it has some merit. But feels ArduPilot unlikely to implement it any time soon.
  - noted that there are cases where vendors are unlikely to agree a standard. Discussion around benefit to them of a standard, even if not perfect.
RFC 0012 - MAVLink Standard Testing Suite
- Lorenz introduced broad scope. Start with test of Autopilots first for some key services. 1 FTE committed from Auterion to do the work.
- Where services diverge, propose work together on new spec to make sure it is something that address all our use cases.
- Note, not necessary for all systems to implement the spec, but if they do, should run against tests and meet requirements captured in docs.
- @JamesP suggested if tests are anything other than Pymavlink unlikely ArduPilot would contribute.
Rest of discussion was around open issues - see AIs below.

@JamesP
- Find what is required to progress ecalculate crc checksum if zeros in payload are trimmed - what we can do?
@HamishW
- Fix CI issues for Add MAV_COMPONENT documentation merges and remove mapper component.
- Fix CI issues for Update minimal.xml to use definitions in common.xml
  - Move in MAV_COMPONENT after
  - Brief review of how hard to support multiple levels of file inclusion. Ask Beat for support if needed.
@Lorenz Next week to create RFC for message services versioning.
- Workshop through at least one service with others

HamishW, BeatK, Lorenz, JamesP, Stone White