20200318 Dev Meeting

Agenda

General:

Add documentation for Open Drone ID messages #220 -component/type ids
- Soren says others have implemented, but not clear how.
- At this point assume will not need component ID or MAV_TYPE for this.
- AO: SorenF to chase up Tom to get a real implementation (and discuss hardware). Aim to get both Network and BT version.
- DONE AO: HW to merge the current docs with WIP tag.
Discussion around larger address space
- James: Needs to be done "properly" but will be very disruptive. Might be an intermediate solution. E.g. Dynamic allocation of system IDs in network so they are more efficiently allocated.
- Joe, convenience of big system ID is that we can use them for identity. Other things we're doing are a hack.
- JulianO: We tried using uuids rather than sysids but that only works well for Autopilots (not everything has a UUID). So would be good to have problem solved.
- AO: Lorenz will design for a non-hacky solution that meets BazookaJoe reuirements in coming 2 weeks. Not a full solution to the long term problem but not hack either. Joe will have to do implementation.
AO: James to keep chasing PeterB re nested inclusion.
Discussions around Microservices versioning and common flight modes taken offline.

Attendees: JulianO, JamesP, HamishW, JonasVautherin, RomanLigocki, Lorenz, SorenFriis, BazookaJoe, Garfield, Superware.