Architecture & practice·Teams, ownership and Conway's law
you opened a pull request against another team's repository and it sat there for eleven days.
Code ownership
Also calledservice ownership, strong ownership, weak ownership
Who is accountable for a piece of code: reviewing changes, running it, and being paged when it breaks. Strong ownership makes quality and on-call clear and makes cross-team change slow; collective ownership makes change fast and quality diffuse. Neither is right in general, and the failure to state which one is in force is what produces both the eleven-day review and the directory nobody maintains.