@arjo129 won’t be able to make it for the Maritime Interface’s review (meetings are now 2am local time and need some sleep!). Some notes on where this is currently:
- Although we can build packages, we need to sort out CI for bloom deployment. Would be great if someone could assist with setting up bloom packaging in CI for the maritime_interfaces repository.
- Through our own use, we’ve determined a more efficient structure than what we currently have in our fork. I might just post to the discourse with the proposed path.
- Further info re UMAA indicates that significant work would be required to integrate with ROS2. Only available method for the moment is to run direct from FastDDS middleware. Thus would propose we simply build something that works for ROS2 (but may align with UMAA in some areas).
- Proposed structure is a lookup file with message shapes, with additional custom packages for non-existent interfaces (like some control msgs). I’ll include this setup in the proposal in the next month or so (without build)
If anyone has any questions or is interested in helping out in places, flick me a message through element or via email.