I think the technical difficulty of an email once per month is nothing like the cultural difficulty here. We don't name and shame at Boost historically. I personally think we should, but it isn't my call to make.
The general process of getting a decision is to generate consensus here on boost-dev somehow, and perhaps institute a voluntary opt in prototype with a few volunteer maintainers (I'll volunteer AFIO right now, and I can't see Vicente having a problem with Thread. Chris just patched ASIO to fix your test failures after I asked him, so I'd assume he'd be in too). After it's proven to work for some months and the community feels comfortable (or not) with it, you then formally ask the Boost Steering Committee for a resolution in favour of instituting it across the board.
That's my best suggestion anyway. Obviously these are matters far wider than Android support, so it's a lot more thorny. For example, if a library repeatedly gets stuck at the top of that name and shame leaderboard, it could generate negative vibes around the library or its maintainers which has unhelpful effects on the community. We already have enough of that with Test.
Yes, it's clearly understandable. I just thought such mechanism was already discussed and community already have kind of consensus on this. If not - well, let's wait for others, what they will say. -- Dmitry Moskalchuk