Document how team leads rotate

[jdno]

We, the infra-team, committed to team lead rotations a few years ago, but never formalized the process to do so. Inspired by the compiler team's RFC on their rolling team leads, we have put together a document that describes the role of the team lead, how we use two co-leads with offset terms to ensure continuity, and the special role that the Rust Foundation plays for the infrastructure team.

Disclaimer: AI was used to iterate on the policy.

[Kobzol]

I think that the t-infra/announcements post is unnecessary, as this is mostly an internal detail of the infra team.

Other than that, it looks great. Thank you very much for putting this together!

[marcoieni]

"re-establish the staggering" is hard to read as a non-native english speaker.

[marcoieni]

Suggested change

	With staggered two-year terms, the rotations alternate: one year, the
	In the two-year rotation: one year, the

simplify

[marcoieni]

Suggested change

	- When a rotation would otherwise leave the team without a
	Foundation-employed co-lead, only Foundation employees can be candidates
	for the seat.

isn't this obvious? 🤔

[jdno]

It is, but since this is a policy I don't think it hurts to call it out explicitly.

[marcoieni]

Suggested change

	selection process applies, and the departing co-lead stays in the role
	until their successor takes over.
	selection process applies.

Isn't this obvious? If not, what does this phrase add?
From my understanding the departing co-lead should give the leadership role asap, right?

[marcoieni]

Suggested change

	The rotation is completed by updating the [team database], the README of
	this repository, and announcing the new co-lead in the
	[t-infra/announcements] channel.
	The rotation is completed by updating the [team database] and the README of
	this repository.

As noted by Jakub, an announcement shouldn't be necessary.

[marcoieni]

looks great, thanks JD ❤️

[jdno]

Thanks for the feedback. 🙂 I dropped the announcement and rewrote some sections to be clearer.

[marcoieni]

Mark in Zulip said agrees with the document. But he suggests to schedule the rotation in March, so that it doesn't overlap with Council and PD elections.
#t-infra > meeting 2026-08-31 @ 💬

Should we add this to the doc?

[marcoieni]

Merging the policy according to what we agreed in #t-infra > meeting 2026-08-31 @ 💬 because no concerns were raised.

I will suggest to schedule the rotation in March in a separate PR.

EDIT: done in #299