ROS 2 wrapper for velodyne drivers

@JWhitleyWork 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.

1 Like