I have been talking to the maintainers of the ros2 version of this repository (https://github.com/bdaiinstitute/spot_ros2), and proposed to somehow reunify these repositories, or at the very least least attempt to make a coordinated effort in maintenance of shared components. ROS2 is coming and I suspect people starting with ROS now might prefer to use that version.
As of now, the intent is to extract the wrapper code and have both the ros and ros2 versions call into that for SDK interaction. This means that there would be a unified interface for access between the two versions, which will likely mean faster integration of new features for releases, and shared effort in improvements to that part of the code.
I have been talking to the maintainers of the ros2 version of this repository (https://github.com/bdaiinstitute/spot_ros2), and proposed to somehow reunify these repositories, or at the very least least attempt to make a coordinated effort in maintenance of shared components. ROS2 is coming and I suspect people starting with ROS now might prefer to use that version.
As of now, the intent is to extract the wrapper code and have both the ros and ros2 versions call into that for SDK interaction. This means that there would be a unified interface for access between the two versions, which will likely mean faster integration of new features for releases, and shared effort in improvements to that part of the code.
For more details and to share your input, please comment at https://github.com/bdaiinstitute/spot_ros2/issues/25, or here.