Closed andrestoga closed 4 years ago
Hello, Yes, it is a good idea. However, I don't know what are the effort to do it and if all modules presently used by Gribot are already ported on ROS2. If you need modification of your access right, don't hesitate to tell me. egards, Guy.
Yeah, that's a problem. What we can do is to work in both versions(ROS and ROS2) in parallel in separate branches.
I see two possibilities:
My only issue is only concerning modules. I have no issue to do a "big bang" in migrating to ROS2.
Agree. Not all modules will be in ROS2. Plus there will be another version for ROS1 in May 23rd. Probably is just better to focus right now on ROS1 Melodic. Then, check if the new version of ROS1, ROS Noetic, is compatible with ROS Melodic and move to that version. ROS2 will be a future feature.
Hi,
What if we focus in developing Gribot in ROS2 which eventually is going to be the ROS stantard. I can start porting the existing Melodic workspace to ROS2 workspace by creating a branch.
Best,