This is just a guess, I am not actually sure how to handle this.

But hopefully, this will...

Closes: tpo/tpa/team#40354

We had nothing about the star of the weeks, which was informally
specified. This clarifies that it's responsible for routine tasks, but
also takes care of clarifying the ticket workflow in the gitlab policy.

Closes: tpo/tpa/team#40382

The support page is the go-to page for the "how to get help" question,
which previously was hidden inside the TPA-RFC-2 standard.

This basically copies that part of the TPA-RFC-2 policy, but could
eventually diverge without needing to update the policy, for informal
stuff.

I started working on this page while trying to address
team#40382 ("document the triage process"), but I'm not
actually sure triage documentation should go there, as this page feels
more targeted at users, and only users.

howto/incident-response.md would seem like a better space for this.

Also, this is a toplevel page because it's more important than
everything else, so it warrants its own special space.

This is non-normative, so doesn't need discussion.

This was explicitly identified by @hiro, and it seems important to
make it clear that those sites will be cared for.

September seemed a bit early to @hiro and @gaba, push it back three
months. We pick December 1st because:

 1. it's still in 2021 so we don't change the roadmap, and
 2. it's a wednesday, so a good time to shutdown a service (ie. not a
 weekend or friday)

We also clarify that we're not fascists: we won't destroy the world if
people haven't managed to respect the deadline.

We drop the time estimate for the migration, because that's actually a
changing number. We were counting from "right now" which obviously
changes every day. ;)

This will be sent to the list shortly.

Those are mostly tests to see if we can get something that satisfies
markdownlint.