Hamish Willee

@auturgy @julianoes I have listed all the WIP entities in common.xml above. Are there any cases above where we can agree that WIP tag should be removed. I think the...

@auturgy OK, I'll do PRs for some of my "no brainers" then. How about I PR moving opendroneid into development.xml and we discuss that with the owner through that PR?...

Thanks @dlwalter and @olliw42 . The first set of changes merged (see checked items above). I am keeping gimbal stuff WIP until @julianoes comes back. I "think" that the ship...

@aerialhedgehog @dlwalter Just FYI, the reason that I haven't progressed dealing with the gimbal/camera messages is that I am waiting on @julianoes to return from holiday (the gimbal stuff was...

I commented on https://github.com/mavlink/mavlink/issues/1669#issuecomment-903393762. In summary I somewhat agree. The camera info message was designed to enable basic camera info via normal mavlink messages, with access to more advanced features...

@python36 Thanks- removed in https://github.com/mavlink/mavlink/pull/1736

@AndKe Yes it would be great to have a simple example of this. It isn't one of my priorities. Part of the problem is that an example is a bit...

Re James comment ^^^ sure - we absolutely need to be careful. However I don't think we can avoid dealing with this in "some way" because the messages are not...

FWIW this was discussed briefly. - Clearly observers are looking at the position output and expecting it to be NED (incorrectly, but still detrimental) - Needs a whole lot more...

@olliw42 It's more "we don't really know, so we need to do more testing". I'm kind of feel that "if you're broken because you're not checking that frame field then...