Open dontcallmedom opened 8 months ago
Hmmm, I'm not sure that I agree but maybe I'm missing something?
Ensuring that things work "as intended" is pretty much review and the fact that it applies across the board is horizontal? I mean, evidently this also has coordinative value, and some reviews (e.g. architecture but not just) are also about making sure all the bits fit together and do the same things in the same way, but I'm not sure that makes it all about coordination?
Or are you saying that because these things have coordinative value it is worth surfacing that and making it more clearly not just about quality but also about making the whole work better?
The description of the role of horizontal reviews ("cornerstone of an integrated approach to web infrastructure, ensuring to the extent possible that the many moving parts of web infrastructure operate coherently and as intended") really seems to be about coordination more than reviews or horizontality.
I suspect talking of horizontal reviews as one of the most important coordination mechanism would avoid confusing the two and may lead to more interesting discussions about the particular role to be played there.
(e.g. coordination happens through other mechanisms that "horizontal reviews" - e.g. the spec infrastructure creates strong convergence forces across groups by enforcing a common set of definitions, shared formal languages, etc)