Hello all, Following the recent discussion here about maintenance, I'd like to express some interest in maintaining circular_buffer. It's my recollection that I has some involvement in the origins of circular_buffer, although that was quite some time ago. I've had some fairly in depth discussions with Claude in terms of where circular_buffer is at, what makes sense in terms of priorities, and areas of needed improvement. Like many people here, I have a full time job and other things on the go. I have maintained a fairly well known open source library for over a decade, which is mostly a matter of keeping the lights on, touching up little imperfections and doing a release from time to time. For the most part it seems as good as it needs to be, despite occasional claims on the interwebs that it's abandoned or unmaintained. My main impression of circular_buffer is that it needs some modest work over time, brought forward to better support C++11 and onwards, and the nuts and bolts infrastructure touch ups. Please do chime in if you think I'm missing anything important, or have any opinions about what circular_buffer needs to be of most utility and value in the real world. In particular I'm still a believer in code review, and would rather catch problems before they make it into the mainline or out in the broader world. Claude is definitely helpful with that, but fellow humans much preferred. Thanks, Nigel Stewart https://github.com/nigels-com https://www.linkedin.com/in/nigel-stewart-a42b843/