Hussain Sitamouwala posted the first draft of a proposal titled "Implement promisor remote fetch ordering". Today, when a partial clone has several promisor remotes, Git picks which one to ask for a missing object by a fixed rule that neither the user nor the server can change.
The plan has three parts: lock today's order in tests, add a local way to set the order, and let a server advertise a preferred order through the existing "promisor-remote" capability. The proposal states a precedence rule and defensive parsing of untrusted input. Sitamouwala asked for feedback on the config shape, the precedence rule, the protocol field and the timeline.
Kaartic Sivaraam thanked him for a careful proposal. He suggested linking to the permalink of the cover letter rather than a thread link, and said that D1-D4 should be explained as the deliverables listed earlier.
Sivaraam also said the choice of Shape A appears to conflict with another part of the proposal. He suggested working out where a stored server value lives, separately from the user's value, and how the two are ranked. In a related thread on a documentation patch about promisor remote ordering, Sivaraam said further discussion should wait until after the Outreachy results are out.