A datapoint as Boost.Thread came up: Cross-compilation to Windows using MinGW proved difficult in the not so far past as C++11 threading support was weak and unreliable. I wouldn't mind if Boost.Thread required C++11 (or even C++17 at this point), e.g. due to dependencies, and it would still have value. Similar we may avoid at least API breakage: I guess it isn't too hard to replace Boost.Foreach by just wrapping range-based for loops; similar for Boost.Tuple This would remove the code maintenance (likely) entirely. Moving those to a single repo to consolidate CI- and build maintenance would resolve the other maintenance dimension. So I like that idea! This also serves as a strong signal for newcomers on which libraries are in this state. If we keep the Boost-layout in this "mono-repo" I think it will even work for compiled libraries. The Boost.CI reusable workflow has support for providing the test targets already, so it could build the tests for all of them. It may need extension for creating the "unified" tree though as it copies the library into the correct libs-subfolder which won't work out of the box when there are multiple. But that's very much doable. Best, Alex