Who controls glibc?

I concur. glibc's gone from being a project that was verging on moribund to a project that's so active that keeping up with the mailing list alone, let alone the patch flow, is quite a lot of work. It's *lively*, and the changes taking place there are extremely nontrivial. (Even some of the changes with no functional effect -- e.g. classifying every entry point according to its multithread-safety.)