corot
commented
4 years ago :+1: good initiative! sure, I can provide some support, though I don't have a physical Kobuki with me (but still use it Gazebo simulation)
Open stonier opened 4 years ago
corot
commented
4 years ago :+1: good initiative! sure, I can provide some support, though I don't have a physical Kobuki with me (but still use it Gazebo simulation)
For those who've been valiantly striving to get T2 on Melodic working (see #399), it's likely been obvious that the ROS1 Kobuki repositories are in need of a custodian. While @corot and I try to volunteer some time, neither of us work at Yujin Robot any longer and it is fairly apparent that Yujin Robot has not reassigned our roles to anybody there.
If someone has a vested interest and would like to share the keys to the ROS1 codebase so you can get the relevant repositories evolved so that they can be released in Melodic and Noetic, let me know, I'd be more than happy to help them along with some pointers. I'm sure @corot would as well.
As for ROS2 and beyond, I've been spinning what spare cycles I have (with @clalancette 's help) to get Kobuki up and running there. This code has all migrated to the https://github.com/kobuki-base organisation, so no problems with ROS1 and ROS2 codebases interfering with each other. If fundamental fixes come in on either side though, it'd be good to close the loop and make sure they're ported in both directions (#382 was a good example of this).
There's also a parallel documentation effort for Kobuki (non-ros and ros2) at https://kobuki.readthedocs.io/en/devel/ (source code at https://github.com/kobuki-base/kobuki_documentation). ROS1 documentation was horrendously all over the place, this brings it all together and adds some missing pieces - cross compiling instructions, a troubleshooting section, additional use case walkthroughts etc. If you've got corrections or would like to contribute anything (e.g. a tutorial on creating cables), we'd very much welcome them.
Private communciations are fine, you can reach me at the address given in the package meta-information. Do let me know your github handle when you do so I can associate you with your presence back here.