Hi, Sounds to me like someone who knows Chris just needs to sit down with them and have a chat about how best to maintain the library going forward. I don't think they want it to be taken off their shoulders because they're still adding new features with each release. But it's possible that they would want someone to handle improving the documentation or answering users questions on github, both of which are just as integral to a open source project as good quality code. I'm also not sure what the issue raised with the quality of github issues is, i think this is a common problem across many projects and it means that maintainers do have to spend time answering silly questions. But as winnie the pooh would say doing nothing sometimes leads to the very best of something. If people keep misunderstanding the library then the documentation needs improving. To be clear I think Chris' has done a smashing job in making Boost.ASIO. I think a fork is a bit of nuclear option, the best route i can see is for someone who knows Chris already to sit down with him discuss these issues and how to get around them so we can continue to ensure that C++ has an viable networking library. P.S whatever happened to std::net????? come on C++ you can do better