@lisuwang @maximest-pierre @TheFlyingZephyr Thank you for offering your support. Please see https://github.com/ros/ros_comm/issues/1496 where I tried to give a high level overview how to help. Please feel free to ask questions on that ticket. @Ingo_Lutkebohle @awesomebytes If you would like to contribute towards an API shim that would be great. We have had discussions about the topic in the past about how viable / complicated it would be, what to cover, what to do when the existing ROS 1 API can't be mapped to ROS 2 etc. I would suggest to start a discussion in the "Next Generation ROS" category. I could also create repositories for this effort (e.g. `ros2/ros1_shim`) if you think that would be helpful to get things rolling? --- [Visit Topic](https://discourse.ros.org/t/ros-comm-request-for-help/5840/8) or reply to this email to respond. If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates. ______________________________________________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users Unsubscribe: