Tim Bannister

#6289 is a related issue because (I think) if Tide were to set its own status and wait for that to pass before a merge was attempted, then you could...

(that's not to disagree with the need for a clearly reproducible issue report)

I like the idea of documenting this as good practice, even if we never 100% achieve that desired state.

Hi. SIG Docs contributor here As a first step, I recommend creating some documentation under https://github.com/kubernetes-sigs/metrics-server - the way Git works, that automatically gets versioned. Use [CommonMark](https://commonmark.org/) format as that...

Usual path for in-project docs is a directory named `docs`, a child of the root.

I recommend putting the docs inside its own `docs` folder. The README on the primary can link into that folder on a release branch, if that's useful.

> This is actually a planned feature for the site, so no reason to close the issue. /lifecycle frozen

/triage accepted

We should also reference the localized code of conduct pages (that are already translated).

I've assumed that this won't be staffed for some while yet.