20180725 Weekly Meeting

Agenda

General:

• Update from last call of other group: 20180711
• Also add Meeting start time information and meeting link to this page.

HamishW:

• Removing v0.9 messages (inc removing v0.9 support from pymavlink + single pymavlink repo). How do I get pymavlink change in?
• Update schema for MAV_CMD params - move this along
• Resurrecting minor version number + release process? - MAV_SENSOR_ORIENTATION discussion

AmilcarLucas:

• Decide if the deprecation method introduced in deprecation PR is good enough and can be used.
• Decide if the WIP method introduced in WIP PR is good enough and can be used.

Notes

Call 1

• Discussion about reducing common.xml to be true common.

  • Lorenz concerned about fragmentation/GCS
  • Generally agreed the problem is that we need to manage change better.
  • Leading on to ...

• Discussion about versioning and releases

  • 2 classes of users
    • Autopilot developers do rapid change/prototyping. Need a flexible method for update
    • Everyone else (consumers).
  • We need mechanisms to satisfy both groups. Probably release cycle for everyone else, and per message versioning for autopilots/core.
  • Also discussed options of having GCS handle multiple versions, autopilot just one. General concerns there about maintenance and burden on GCS.

• Lorenz requested we take time to make sure next meeting Agenda includes PRs/Issues we want to discuss.

  • Let's engage to get the participants present so we can unblock problems.

• Next week would like to discuss modernizing/maintaining Generator.

AI:

• AI (Lorenz): Drop mavlink/pymavlink to make management easier for community
• AI (Lorenz): Review 953: Update MAV_SENSOR_ORIENTATION for more entries.
  • In principle will accept this. Will rev the version number in messages from 3 -> 4 (?)
  • Change to rename MAV_SENSOR_ORIENTATION properly held back until we have formal release
• AI (Lorenz): Send meeting members issue number with proposal for message versioning (please update if needed to clarify final proposal)
• AI (Lorenz/Hamish): Make sure agenda up early enough and we chase people to attend on issues that interest us.
• AI (Hamish): Work with others to create contribution guidelines to help people make sensible submissions for new messages.

Call 2

[Discussion] [Points that need further discussion]

AI: