Who controls glibc? And why?

Who controls glibc? And why?

As I read these comments, I kept waiting for someone to state what should be quickly arrived at:

What is the purpose of the documentation? Or, even, what is the purpose of the GNU C project?

I'm not a contributor, so I have no axe to grind other than using tons of GNU-supported software, but I do have a lot of experience in working in a variety of consensus-oriented communities (many non-technical). This is clearly a case where Mr. Stallman has a particular set of values and priorities and some number of contributors differ in these. So, if it is not possible to achieve agreement, the next question is what paths do the various parties find suitable to their respective wishes?

It may be that, overall, the desire to continue as a single project takes priority and whoever has the ultimate decision-making power gets to decide. Deciding who has that power would, in this case, need to involve a high degree of willingness in others to gracefully yield on this decision. If having one project is not the priority, well, GNU software can fork, too.

I do hope that all involved realized that this is both an issue which is about as important as most bikeshedding issues, and another one which is defining the answer to a really important question of the GNU C direction setting and that the two shouldn't be confused.