Hi dear community, It seems there’s some shared dissatisfaction with how Asio’s process currently works. From what I understand the key challenge is finding a way forward without “taking over” Chris’s role — and of course, if Chris is hard to reach, that makes collaboration trickier. One possible path could be to draft and review PRs collaboratively as a community. From Chris’s perspective, this could raise the quality bar enough to make merging easier/faster. For Boost developers, it provides a way to contribute and maintain some quality control without requiring a full takeover. And for users, it would mean faster improvements and iterations without the complexity of two Boost.Asio versions :) Naturally, this would still depend on a minimum of goodwill, time and communication from everyone involved. Best, Arno