Skip to content

20201014 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Oct 15, 2020 · 5 revisions

Agenda

General:

Notes

  • add pseudo oblique function to 206 CAM_TRIGG_DIST - 1508

    • Great idea, but very use-case specific.
    • Lorenz concerned that this is on the border of what we should be relying on Flight Stack to do. E.g could be done via Ground station.
    • Igor to investigate whether it can be made more generic - ie update to generic gimbal control at trigger point.

  • MAVlink Governance Policy (discussion doc)

    • Big picture concerns raised:

      • Are generator tools "core part of protocol" / should they be part of this standard?
        • Technically they may not be, but in practice we all rely on them and they do need to be managed collaboratively.
        • Lorenz pointed out that mavlink governance doc over tools when tools are not under management of mavlink org is a bit pointless.
        • JamesP wants this in because it all needs to be managed.
        • Lorenz accepts "as a working position" we can consider the tools as part of the protocol/management and work towards that being true.
      • How can we maintain collaboration
        • The approach encourages development in dialects. This is very agile as it restricts the stakeholders to those who are doing the immediate work. This sometimes results in silos (great ideas that are not well shared) and narrow designs (designs that meet a specific goal, but which cannot easily become part of the standard.
        • We still need a process to encourage collaborative discussion of new features - either experimental, or proposed or whatever.
        • This should not be named "Common.xml".
        • Not entirely resolved, but general agreement that the above are legitimate problems and we do need mechanisms work through these.
      • Lorenz Let's start acting on the process without yet "accepting it" to find out what works in practice.
        • Some discussion that we could accept as "living document" and iterate what does not work.
        • Lorenz: We're not building on "no process" - while this looks good none of use will know until we start hitting roadblocks.

    • Worked through doc. Lots of discussion. General agreement with goals and big picture.

    • HamishW excused himself at 7. My understanding is that discussion continued and result was further iteration of the document.

Not discussed:

Attendees: HamishW, JamesP, JulianO, JonasV, LorenzM, Peter Barker, David Buzz, Michael Oborne, Philip Rowse

Add a custom footer
Add a custom sidebar
Clone this wiki locally