You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team and I have just started on a MOOS/ROS2 project and we'll be bridging between these two worlds. I understand we can use moos-ros-bridge and ros1_bridge but was thinking we'd be much better off writing a moos-ros2-bridge.
Is this something you have looked at before? I was thinking we'd either fork this project or I could submit a PR and the ros2 version could live on a branch.
Thanks,
David
The text was updated successfully, but these errors were encountered:
I have been using ROS2, but I haven't been using it with MOOS or the moos-ros-bridge yet. Porting from ROS1 to ROS2 isn't too cumbersome, so many ROS packages just use a "ros2" branch in the existing repo to designate which branch should be used with ros2. If you port the code to ROS2, I would be more than happy to merge it back into this repository under a ros2 branch.
Hello hello,
My team and I have just started on a MOOS/ROS2 project and we'll be bridging between these two worlds. I understand we can use moos-ros-bridge and ros1_bridge but was thinking we'd be much better off writing a moos-ros2-bridge.
Is this something you have looked at before? I was thinking we'd either fork this project or I could submit a PR and the ros2 version could live on a branch.
Thanks,
David
The text was updated successfully, but these errors were encountered: