@JWhitleyAStuff If you're maintaining both versions unless you're planning a ground up rewrite I'd recommend developing keeping it in the same repository and just use a different development branch. This will allow you to keep the code bases close and facilitate code reuse.
Like ROS1 the ROS2 ecosystem is intended to be a large federated ecosystem, we put a lot of things into the ros2 organization during early development but not everything needs or should be there, and some things will be expected to merge back to their original repositories as we get time to cleanup and merge back changes instead of planning to maintain parallel forked projects.
---
[Visit Topic](
https://discourse.ros.org/t/ros-2-wrapper-for-velodyne-drivers/4744/6) 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: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)