Chris could improve this dramatically here.
Yes, for example:
https://original.boost.org/doc/libs/1_89_0/doc/html/boost_asio/reference/asy...
High quality documentation, that is. ... My proposed solution is a fork and the only other
Maybe the discussion should be not how to fork - the logical answer is obvious - why do you think another maintainer will do the better job. The discussion should be how to help improve code and documentation of ASIO when the author is busy? See the difference? Instead of going negative-counter-productive way - see how can it be "how community can help" Now than it is something that can be discussed with maintainer on higher level and maybe co-developer/development team can be created to manage some of the issues. Fork - not cooperative Co-maintaining - cooperative Just $0.02 Best, Artyom