Andrzej Krzemienski wrote:
I think nowadays a GitHub repo is a good enough place to store a candidate library along with its documentation. The task for the author is to attract sufficient interest for their library.
I have a small library that I consider proposing at some point at: https://github.com/akrzemi1/markable I would occasionally ask for feedback. But it is generally difficult to draw the expert's attention.
One relative obstacle is that a library needs to have a different structure when used standalone and when it's part of the Boost superproject. When I prepare a new library for submission, I make it adhere to the latter structure, so that when accepted, it can go into Boost immediately and as-is. But this makes it inconvenient for others to try it out. We probably need to figure something out on that front because it's 2025. I suppose nowadays one can require C++17 or C++20 and avoid the need for depending on Boost libraries, which makes things much easier.