Ok, I will create ‘ros-orphaned’ ‘ros-orphaned-gbp’ organization, fork, and release them, as a ROS Orphaned Package Maintainers initiative. (OrphanedPackage - ROS Wiki, https://github.com/ros-infrastructure/rep/pull/150)
But this means if someone willing to maintain the repository, we will move the package to them and I understand there is a concern of confusion.
Regarding the location of “orphaned” repositories: I don’t think moving them around when the maintainer status changes (which could happen multiple times over time) is beneficial.
So another option is to fork to ‘ros’ and ‘ros-gbp’ and I’ll take care of them. How do you think ?? @tfoote @dirk-thomas