There has been no discernable activity in this repository for the last two years, and it is in dire need of some maintenance. I have taken up maintenance for the RobotWebTools WebRTC package already, and it'd be willing to step in for this package as well, as webrtc_ros depends on async_web_server_cpp, and this is one of the blockers we identified in RobotWebTools/webrtc_ros#53
Assuming that none of the former developers is still invested in this package, I'm hereby pinging the public team members of the organization, @banerjs, @dekent, and @rctoris, to ask for assistance in transitioning the maintenance.
I can continue maintaining the package here if someone were to grant me write access to this repository and https://github.com/gt-rail-release/async_web_server_cpp-release, or I could fork the repository to a namespace under my control and then take over the rosdistro entry. The latter is probably easier to do when I can point to e.g. this issue to show that I have consent of the former maintainers.
There has been no discernable activity in this repository for the last two years, and it is in dire need of some maintenance. I have taken up maintenance for the RobotWebTools WebRTC package already, and it'd be willing to step in for this package as well, as
webrtc_rosdepends onasync_web_server_cpp, and this is one of the blockers we identified in RobotWebTools/webrtc_ros#53Assuming that none of the former developers is still invested in this package, I'm hereby pinging the public team members of the organization, @banerjs, @dekent, and @rctoris, to ask for assistance in transitioning the maintenance.
I can continue maintaining the package here if someone were to grant me write access to this repository and https://github.com/gt-rail-release/async_web_server_cpp-release, or I could fork the repository to a namespace under my control and then take over the rosdistro entry. The latter is probably easier to do when I can point to e.g. this issue to show that I have consent of the former maintainers.