It is generally known within the community that some of the libraries in Boost are not being properly maintained: issues pile up without a prompt (or any) response from the nominal maintainers, eroding the libraries' usefulness and, ultimately, their viability. There are a number of stalwart contributors (Peter Dimov, Andrey Semashev, and others) who work to make sure CI tests stay green throughout the project, but beyond that they can't possibly address outstanding issues and evolution requests for all libraries. Any initiative to try to remedy this situation begins with identifying its true extent. My colleagues at the FSC and I have gone through all Boost libraries and identified those that we regard as unmaintained, as evidenced by the presence of many important issues that go unresolved without anyone addressing them. This is the list: accumulators, align, callable_traits, circular_buffer, compute, concept_check, contract, convert, date_time, foreach, format, function_types, functional, fusion, hana, hof, integer, lambda, local_function, logic, multi_array, numeric_conversion, odeint, parameter, phoenix, polygon, pool, preprocessor, property_tree, proto, ptr_container, range, rational, scope_exit, statechart, stl_interfaces, tokenizer, tti, tuple, type_erasure, ublas, units, variant, vmd, xpressive, yap Any such assessment is a little fuzzy by definition, so the cutoff point for what's considered maintained or not is subject to discussion. I'd like to request your feedback: * If you think some entry in this list should be removed (because you're the maintainer or you know the library is actually maintained and we got it wrong), please say so. * Conversely, tell us if you feel some Boost library not in the list should be included. * Please share any ideas on how to improve the situation so that we get more people actively maintaining more libraries. For starters, unmaintained libraries could be labeled as such on the website to attract people potentially interested in taking over (and to warn potential users about long-term adoption risks). Thank you! Best, Joaquín M López Muñoz Fiscal Sponsorship Committee