20190501 Dev Meeting
Hamish Willee edited this page May 1, 2019
·
3 revisions
General:
-
Update from relevant previous calls
-
Status updates
- Discussion/progress major proposal: [Events Interface]
- @WickedShell File format discussion - Attempt to re-engage in next two weeks.
- Upload mission - discuss with GCS vendors what they see as best way to handle lost Drone originating messages
- JulianO: Report back on possible System ID allocation approaches and GCS discovery mechanisms/publishing heartbeat when not connected.
- Lorenz/Hamish - What is happening with Rust team (Michal)
- MichaelDb: PR to update
STATUSTEXT_LONGwith fields to allow longer messages. - Minimal or fully specified XML? Direction of defaults? https://github.com/mavlink/mavlink/pull/1100
- Doc Mission partial upload/download - I need to update further.
- COMMAND_INT/MISSION_ITEM_INT definition danger spot - MatthiasG
- SET/GET message interval clarifications - persistence, what stream?
- Ways to resolve conflicts in requests from multiple sources - GCS, Developer APIs, etc. Both different telemetry rates and safety critical systems.
-
Proposal to change Dronecode SDK to MAVLink SDK
- Proposal to rename Dronecode SDK to MAVLink SDK presented by Jonas
- Generally considered a good idea if is hosted under MAVLink project, but otherwise is confusing naming
- Should focus on MAVLink, and be able to support all MAVLink users, both for common and dialects.
- Run like any other project - accept good code with tests. Remove contributed code that isn't be maintained.
- Next step is RFC
- Jonas to create RFC for proposal to allow broader discussion and capture of information. Should cover reasoning, broad steps, high level goals, expectations of project with MAVLink scope.
HamishW, JamesP, Jonas