Sorry, I didn’t saw that there had been further developments here.
Well, I have to be honest. I don’t understand this argument. If you argue that this is a more widespread problem, I would say that none of these institutions are problematic on themselves. It is the organizational and institutional architecture (and the contained flows and interactions) in which these institutions are embedded that makes them a complement or a problem. But in here, I just focused on Fedora Docs within Fedora 
Well, it is not really a pain. I just see that underlying problems remain hidden, due to reciprocal false assumptions that make symptoms look like origins. I am not questioning the centralization in general, but our current implementation in the given organizational and institutional framework.
My goal with this topic was to encourage people to question what used to be taken for granted, to replace maybe some false assumptions, and especially, to practice some self-reflection. A “hard counter perspective” might facilitate this - or just create a slight cognitive dissonance that might result in a little broadened horizon, and maybe encourage people to compare here and there what type of Docs (or other things) work and what not, and maybe question why 
The current release notes issue could be seen as another example of symptoms but one that does not come from within but from outside, so vice versa to most of my examples. So I don’t argue the Docs team is the problem or so (just to avoid a misunderstanding).