20200902 Dev Meeting

Agenda

General:

MAVlink Governance Policy (discussion doc)
- Generally, looks good but needs deeper thought. To be updated over coming weeks and discussed next week.
- Initial impressions
  - great to clearly clarify what "standard" means - e.g. 2 implementations.
  - need to work to make sure that we involve "meaningful stakeholders" for design of services/messages (e.g. gimbal manufacturerers).
Param_ext trimming
- Discussion around whether we should have created new messages or left alone. Considerations being:
  - Most uses will be on high bandwidth links - saving a few bytes not necessarily worth it.
  - New design easy to implement and doesn't break if either end does not understand messages. However it has the appearance of complexity for new users.
  - Might be better moving straight to a new param protocol like the one used by ArduPilot or something based on Bson.
- James pointed out more generally that we need to consider the bigger landscape before making changes - e.g. creating a fancy gimbal API is all well and good, but will it be implemented or will manufacturers prefer to invest based on market share.
- ACTION: Julian/Lorenz to decide whether or not to keep.
message_definitions: add an all.xml to try to avoid conflicts in files which don't already conflict #1453
- Love it. Agree to merge
SMART BATTERY - can we kill the status message?
- Yes, action on hamish to push that forward. It is WIP and Don's suggestion is better.

Did not cover

Attendees: HamishW, JamesP, JulianO, LorenzM