-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rough outline of ROS 1 to ROS 2 porting documentation #3299
base: rolling
Are you sure you want to change the base?
Conversation
Signed-off-by: Shane Loretz <sloretz@google.com>
This is great, thanks for starting this!
Yes please! That is, I think it is important for us to have a one-stop, consistent set of guides for porting ROS 1 to ROS 2. |
Signed-off-by: Shane Loretz <sloretz@google.com>
Signed-off-by: Shane Loretz <sloretz@google.com>
Signed-off-by: Shane Loretz <sloretz@google.com>
Signed-off-by: Shane Loretz <sloretz@google.com>
Signed-off-by: Shane Loretz <sloretz@google.com>
Signed-off-by: Shane Loretz <sloretz@google.com>
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-2023-02-16/29927/1 |
what's the status of this PR ? are you going to put some time on it @sloretz ? |
Opening for early feedback from curious readers. This is a rough outline of a guide for porting a package from ROS 1 to ROS 2.
There are existing guides for parameters and launch files that I'll try to include in the flow of this one.