On Fri, Aug 15, 2025 at 12:12 PM Andrey Semashev via Boost < boost@lists.boost.org> wrote:
Have you discussed this with Christopher? Specifically, if it would be possible to collaborate or co-maintain Asio and/or Boost.Asio.
This is exactly the problem. Chris does not respond to emails, does not respond to GitHub issues, and has told me in the past that he does not like to interact on social media or in chat rooms. I have asked many times. This is a frustration shared by many. No, it is not possible to collaborate or co-maintain Asio with Chris. Kohlhoff works in high frequency trading firms, which implement valuable proprietary algorithms and require NDAs (non-disclosure agreements). Often he cannot talk about his methods, so keeping quiet is second nature. I believe that Asio for Chris is first a portable network library that he uses in his career, and second an open source offering for users. That is, that Chris evolves Asio in accordance to his needs at work and not in response to users, whose GitHub issues, email, and mailing list posts he simply does not see or read. Therefore, even if Chris was open to collaboration there are many design decisions which we may want to make that he might disagree with. For example, we may consider requiring a more recent version of C++. We might want to use `std::error_code` instead of `boost::system::error_code`. We might want design changes which help other Boost libraries interoperate yet conflict with his vision. All of this is solved with our own fork of Asio. Thanks