On 15 Aug 2025 22:34, Vinnie Falco wrote:
On Fri, Aug 15, 2025 at 12:12 PM Andrey Semashev via Boost <boost@lists.boost.org <mailto: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.
Incidentally, I recently received a PR from Christopher for Boost.Log[1], to reduce the dependencies caused by Boost.Asio. Which was an issue I reported in Asio[2] not long before. So clearly he does monitor issues and responds by action, where he sees fit. My concern with the proposed fork is the longevity of the project. I agree with Peter that it would be increasingly difficult to maintain, with little practical effect (other than better documentation, I guess). We may end up with unmaintained fork that is incompatible with the main library, which is no longer accessible to Boost libraries (other than as an external dependency). I don't see switching to std::error_code as a big deal, but maintaining this change will take resources that are better spent elsewhere. As for adding support for other cryptography libraries, is it not possible to that externally? I don't work with Asio very often, but from what I remember, the SSL part of it is quite separate from its core. It should be possible to write similar wrappers for other crypto libraries, if needed. Maybe you should consider a new Boost.AsioEx library that hosts such Asio extensions instead of a fork. [1]: https://github.com/boostorg/log/pull/249 [2]: https://github.com/chriskohlhoff/asio/issues/1637