There’s been a parallel discussion about this on ros-sig-drivers: Velodyne Driver Maintenance
In short, @joq agreed to let Joshua Whitley share maintainership.
I frequently hear people complaining that they don’t have time to do the binary releases. I always find that a bit odd: In my experience, running the catkin_generate_changelog, catkin_prepare_release, bloom-release commands takes up maybe 1% of the time in maintaining a package. The remaining 99% is spent reviewing, testing, merging and iterating on pull requests, tracking down issues, porting to new distros, responding to issues, fixing bugs, making sure that the package correctly builds on the buildfarm and fixing bugs if it doesn’t. Does it really make a maintainer’s job that much easier if somebody else takes over the binary release part? And what happens when nobody feels responsible for the remaining 99% of the work?
Just trying to understand.