20210428 Dev Meeting

Agenda

General:

Broad discussion about broadening industry engagement and standardisation
- How do we stay ahead of the pain points that people will be feeling in a few years/are starting to feel now? (e.g. known stuff like max systems in network, discovery and allocation of ids, routing, and unknown stuff like how to integrate with AI planners)
- Who are the stakeholders we could engage? Enterprises, DoD, Microsoft? Skydio? Betaflight? Cleanflight?
- How would we present standardisation as relevant to them - create an appetite for compliance?
Add simple FSM support to ORBIT_EXECUTION_STATUS message in common.xml #1622 - looks like perhaps the messages are flawed and that this would be just a "patch" on those flaws.
- DONE AO HamishW to capture discussion.
Add fastMavlink C library #341 - New C library 'ala OllieW. Highlighting.
- AO HamishW to merge.

Did not cover:

common.xml: add fields to smart_battery_info - Any objections? Any implementers?
MAVLink signature check in C library does not check signing_streams's link_id when creating new stream #1619 - can I get a technical review please?
Geofence action command per-fence - merged into development.xml. Action to get it into flight stacks?
Add 'invalid' attribute to messages for invalid, unknown, to be not used, etc, fields #1614
- FYI only. Generally seen as a very good thing.
- Careful review done. Final check requested from Julian.
- Only concern for me is slightly ambiguous meaning of invalid "not supported by system" vs "data we are sending now is invalid".
Which dialects are alive? Specifically - matrixpilot, ualberta, paparazzi have no contact details.

Attendees: HamishW, Lorenz, JulianO, Apologies: JamesP