20180711 Weekly Meeting

Agenda

General:

• Update from last call of other group

Ramon:

• Maintainers, responsibilities and overall project governance.
• Meeting health, meeting minutes, attendance, agendas, and where to publish
• Cross-call synergy

Hamish

• Versioning support in MAVLink - see if we can progress the discussion in #795.

Notes

Call 1

• Meetings should be scheduled automatically, meeting id same on all pages
• agenda and meeting notes should be on wiki
• Maintainers:
  • When do we do breaking changes?
  • java: Michael volunteered
  • python: pymavlink is a fork from ardupilot. Need to clear this up.
    • possibility: split out generator from pymalvink
  • discussions about: https://github.com/dronefleet/mavlink
• discussions about smaller chunks of definitions instead of a big set of messages --> goal: have smaller common
• at which stage do external mavlink tools get linked from the mavlink docu? (assuming they adhere the standard)
  • existance of toolchains should be documented, without saying it is validated
  • need validation suite

Points that need further discussion:

• lack of maintenance on mavlink, new ideas do not get in because no one answers
• how to sync repos (ardupilot/mavlink). There might be breaking changes
• Need: release cycle, versioning --> can generate updates for language bindings
• submodule for message definition

AI:

• Hamish: to write documentation section, pointing to external tools
• Thomas: talk with Lorenz about pymavlink (tools and generator) location/forks
• Thomas: discuss submodule for message definition in 2nd meeting

Call 2

• main issue: need maintainers with clear responsibilities
• idea: committee 7 people, self nominated
• what is mavlink: is it language definitions or also a reference implementation
• submodule for message definition: deferred to later when we have maintainers